The Smart Marty Sky Dispatch
Chicago O'Hare news: United Airlines CEO Scott Kirby urges FAA to boost staffing as airport taxi times rank among nation's longest
United Airlines CEO Scott Kirby is urging the FAA to increase air traffic controller staffing, citing lengthy aircraft taxi times at O'Hare International Airport.
United Airlines chief executive Scott Kirby has urged the Federal Aviation Administration to restore full air traffic controller staffing at the agency, arguing that understaffing at the ORD-area facilities contributes to prolonged taxi times at Chicago O’Hare International Airport. The remarks focus on ground movement efficiency and ATC capacity as the primary lever for reducing taxi durations, rather than changes to takeoff or landing procedures.
In the same wave of reporting, ABC7 Chicago notes that the issue at ORD is tied to ground operations and employee staffing levels and does not present specific taxi-time figures. The coverage centers on Kirby’s position regarding regulatory staffing and its potential impact on airport ground movement, with ORD singled out as the location of concern.
Simultaneously, Simple Flying's summary of Kirby’s statements emphasizes the claim that returning ORD’s air traffic control towers to full staffing could shorten taxi times by several minutes per movement, framing the problem as structural within the ATC system serving ORD and not a single flight anomaly. The outlet highlights ORD as a hub where taxi durations have grown lengthy.
CBS News corroborates the broader theme by incorporating Kirby’s assertion about staffing and efficiency at ORD into their report, while also including separate coverage of a Frontier Airlines diversion to O’Hare (see below). The CBS piece notes that ORD’s ATC staffing is part of the conversation about ground movement and congestion, without detailing specific flight operational numbers.
Within the same narrative cluster, Florida Politics and PYOK report on a separate Frontier Airlines incident diverted to O’Hare due to an in-flight issue described as highly unusual, with the diversion to ORD noted but no injuries reported at that moment. ABC7 Chicago’s consolidated coverage reiterates that Frontier was contacted for additional information, though the material available does not include precise aircraft type, flight number, or passenger counts.
The Frontier diversion is further detailed by CBS News, which identifies the flight as Frontier 3655 traveling from Denver to Detroit when the lavatory leak flooded the cabin and prompted an emergency landing at O’Hare. CBS specifies that the diversion occurred en route to Detroit Metro Airport and that there were no reported injuries upon arrival, and notes an emergency procedure was declared by air traffic control as the situation developed.
NBC 5 Chicago’s coverage similarly describes Frontier Airlines’ diversion to O’Hare following a reported bathroom leak and the resulting emergency landing, but the report does not provide additional granularity such as aircraft type or crew and passenger details. The combined reporting from ABC7 Chicago emphasizes the administrative and operational response rather than technical aircraft specifics, while noting Frontier was contacted for more information.
Across the gathered material, the core sequence is consistent: a Frontier Airlines flight diverted to Chicago O’Hare because a lavatory-related issue caused cabin flooding, the diversion culminated with an emergency landing at ORD, and there were no injuries reported at the time of landing. Local outlets such as ClickOnDetroit and other affiliates corroborate the general sequence but do not add new technical flight details beyond describing the emergency diversion and response.
In related, non-ORD items within the same feed, the Florida Politics material mentions a United Airlines Boeing 737 MAX 8 observed at Ponta Delgada, Portugal, while TheTravel covers an American Airlines passenger lounge moment involving a former U.S. president, and other outlets describe unrelated airport policy developments and security events. None of these ancillary items provide additional operational specifics about the Frontier diversion or ORD taxi-time data beyond what the Frontier incident itself establishes.