The Smart Marty Sky Dispatch
American Airlines Cancels & Launches 6 Routes: See All Changes Now
They're all from one hub, which is fast-growing but not among the carrier's main hubs. Find out more here!
American Airlines announced a broad set of changes to its route network centered on Los Angeles International Airport, with the goal of recalibrating its overall Los Angeles operations. The communications describe a mix of route cancellations and new launches tied to the carrier’s Los Angeles hub, but the material does not provide specific destinations or exact flight details for either the cancellations or the additions. The emphasis is on Los Angeles as the focal point of the week-long network update and on the strategic importance of the hub within American’s broader network planning.
In addition to the Los Angeles-focused adjustments, Simple Flying reports a plan to expand American’s international footprint with nine new routes planned for 2027. The first new service cited is a Miami to Venezuela link, described as the initial addition in the nine-route plan. A second notable proposed long-haul service is Chicago to Tokyo, which is expected to launch in March as the first long-haul addition within the plan. The material provided does not list the other destinations, exact launch dates beyond March for Chicago–Tokyo, or aircraft assignments for these proposed routes.
The reporting also recounts that these international expansion efforts form part of American’s broader growth strategy to broaden connectivity beyond current operations, with the carrier not supplying further specifics such as the complete destination list, the full launch timetable, or the aircraft types planned for the new routes. The coverage consistently frames these nine anticipated routes as part of a larger international-growth push rather than as isolated changes.
Separately, the Bradenton Herald notes a nationwide action by the Federal Aviation Administration grounding all flights on a given Friday, which disrupted operations across the sports world. The Bradenton Herald places this FAA grounding within the context of broader aviation-safety reporting that included engine-related emergencies involving American Airlines, but it centers on the grounding action itself and its immediate operational impact rather than on the details of the American network revisions.
The Tanzania Times provides a distinct incident tied to an in-flight emergency observation near the incident zone: a SkyWest-operated aircraft was seen with flames in an engine and a possible fluid leak, prompting an urgent transmission to air traffic control signaling a potential in-flight emergency needing ATC attention. The Tanzania Times notes that the report does not identify the airline operating the aircraft, the flight route, or the passenger count on board. Simple Flying later specifies that the American Airlines case involved an Airbus A319 departing Phoenix Sky Harbor for an undisclosed destination, which declared a Mayday shortly after takeoff after another aircraft observed flames in one engine; a trailing SkyWest flight relayed the warning to ATC, and the aircraft returned to Phoenix and landed. No information on injuries or the final status of the flight is provided in the supplied material.
The Straits Times frames this engine-fire event as part of a broader set of engine-related emergencies, distinguishing the Phoenix A319 incident from a separate 737 incident that diverted back to its departure airport after an inbound engine fire attributed to a bird strike. The Straits Times notes that all 181 people aboard the 737 were reported safe upon landing, and it does not tie that event to the Phoenix A319 incident or to Israir’s codeshare discussions. The Straits Times’ account thus situates the A319 event within a wider narrative of engine-related emergencies rather than linking it to a specific procedural cause or outcome beyond the landing.
Haaretz reports on a separate development in American Airlines’ operations: Israir announced a codeshare agreement with American Airlines, described as part of American’s return to Israel and broader connectivity ambitions. Haaretz characterizes the codeshare as potentially widening Israir’s customer base by an estimated 20 to 25 percent and possibly generating $20 million to $40 million in annual revenue for Israir. The Haaretz piece does not provide specific routes, dates, or other operational details tied to the codeshare. In the broader context, Haaretz frames Israir’s codeshare with American as part of American’s broader connectivity strategy, including its return to Israel, but does not connect the codeshare to any particular American route adjustments or the Phoenix A319 incident.