United Airlines CEO Scott Kirby told a Chicago audience this summer that American Airlines is losing roughly $1.1 billion a year at O'Hare, and that an American exit would let United consolidate the airport into a single 1,000-daily-departure hub on par with Delta in Atlanta and American itself at Dallas/Fort Worth.

Speaking at a Crain's Power Breakfast on August 27, 2026, Kirby framed American's Chicago operation as a structural drain. United, he argued, would absorb the traffic, drop redundant shuttles to nearby cities, and use the released slots to open longer-haul routes that Chicago travelers actually want.

What is the regulator's role?

The argument does not stand in isolation. The FAA capped operations at O'Hare this summer under a gate-allocation plan that favored American and froze United's post-pandemic build-up. That ruling broke United's playbook for gradual dominance at the airport and handed American a reprieve.

United had banked on incremental gains. The cap pushed back.

How much duplication sits on the schedule?

Cirium schedule data for July 2026 shows the two carriers run more combined daily departures from Chicago than Delta runs from Atlanta or American runs from DFW on their own. The gap in per-airline scale is the point.

Milwaukee illustrates the redundancy. On Monday, July 12, 2026, the two carriers ran six flights on 50-seaters, five on 65-seaters, and three on 76-seaters between MKE and ORD. Almost none of those seats carry true Chicago origin-and-destination demand; they exist to feed each hub.

What would United actually gain?

Kirby's logic runs as follows: drop the duplicate feed, upgauge where needed, and shift roughly 250 daily departures toward new destinations.

"There's twice as many flights to Milwaukee as there would be the equivalent number of flights from, you know, at Atlanta to Charlotte, or Atlanta to Raleigh-Durham," Kirby said. "So that constrained resource of the number of flights [that can flow through the airspace around O'Hare] is being used to fly twice as many flights to those local markets that don't really drive the local Chicago economy."

Available slots around ORD are fixed. Freeing them creates room for longer-haul routes, denser mainline service, or both. United already runs more ORD departures than any other carrier and would presumably widen that lead.

Where does the trade-off break down?

The Milwaukee case is straightforward. Chicago-area passengers rarely fly there for its own sake. A swap of short-hop shuttles for a nonstop to a leisure or business market they actually choose is generally a win.

For Pittsburgh, it is harder. The Chicago-Pittsburgh market runs more than 300 daily passengers each way as true origin-and-destination demand. Routing all of that through a single carrier would almost certainly lift fares and reduce schedule choice. Some competing airline would have to backfill, and that is unlikely at competitive scale without American's existing infrastructure.

Why doesn't American just leave?

Three forces hold the carrier in place:

• The hub underwrites a large credit-card and loyalty earnings base no rival network can replicate.
• A sole-carrier ORD would give United pricing power no other U.S. airline holds.
• Abandoning ORD concedes Chicago to United permanently, after American already lost New York and is ceding share in Los Angeles.

American cannot realistically reclaim the top spot in any of those three coastal markets. Chicago is the one place it can still be a credible number two. Walking away forfeits that floor.

What comes next?

The Crain's appearance is pre-damage control. Kirby is shaping the narrative before American has to answer for a Chicago retreat that has not been announced. The likeliest near-term outcome is continued litigation over the FAA gate plan and a slow grind for corporate accounts.

Kirby's longer-term play is harder to read. Some observers now speculate a future American board could revisit merger discussions rather than accept a managed retreat from ORD. That scenario remains improbable, but the FAA ruling has reset the table on which it would be debated.