UA1732

UA1732 arrived on time 88.6% of the time, against 76.9% for all BOS → ORD flights, so this departure is 11.7 percentage points better than the route as a whole. Against United Airlines’ own flights on this route it is 9.6 points better.

Source: US DOT Bureau of Transportation Statistics · 967 operations, July 2023 – July 2026 · If UA1732 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.

This flight runs unusually far ahead of the BOS → ORD route as a whole, better than 93% of 11,788 comparable flight numbers.

88.6% on time for this specific departure, against 76.9% for every BOS → ORD flight.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · The one thing about this specific departure that ranks most extreme against every other published flight number, out of everything FlyerIntel checks — shown only when something clears a real statistical bar, not for every flight.

UA1732 has cancelled 0.93% of its scheduled departures (9 of 967), against 2.02% for all BOS → ORD flights — this specific departure cancels 1.1 percentage points less often than the route as a whole. Different flight numbers on the same route can carry different aircraft, crews and schedules, so this is a fact about UA1732 specifically, not about the route it flies.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026

Share of the delay minutes US DOT attributed to each cause for UA1732 on BOS → ORD. Only delays of 15 minutes or more are attributed.

Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026

The aircraft flying UA1732 came in 15 or more minutes late on 8% of the departures where its previous flight is known. There are not enough departures in both groups to say how the flight left after a late one and after an on-time one.

Each departure is matched to the flight the same aircraft flew into BOS just before it, using the tail number in the DOT file, 896 of 959 departures in all. A departure is left out when that flight is unknown, was cancelled or diverted, or the aircraft had sat for more than 12 hours. A flight the airline cancelled never left and is not in the count, and one flown by a substitute aircraft is matched to the aircraft that flew it, not to the one first planned.

Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026

UA1732 pushes back an average of 7.4 minutes late and reaches the gate at ORD an average of 0.9 minutes early. The 8.2 minutes between those two figures are slack the published schedule already carries, which is why a late pushback on this flight does not reliably become a late arrival. It spends 15.4 minutes on the taxiways at BOS, 3.1 minutes shorter than a typical BOS departure in the same hour.

On arrival at ORD, UA1732 spends 18.1 min taxiing from touchdown to the gate — ground time a connecting passenger sits through before they can even leave the aircraft, on top of however late the flight itself ran. That is about what any arrival at ORD spends on the ground before reaching the gate.

Departure delay is averaged over every pushback and arrival delay over every completed arrival, so the two counts differ by the flights that never reached ORD. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 23,189 departures from BOS scheduled in the clock hour UA1732 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at ORD (952,666 flights), not just UA1732’s own. More on taxi time.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026

UA1732 is scheduled out of BOS at 12:30 PM, in the 12 PM–1 PM bank. Departures from BOS in that hour arrive on time 79.2% of the time against 77.2% across the airport’s whole day, so the hour UA1732 leaves in is an ordinary one for BOS and explains nothing about its record either way.

The two airport figures cover every departure from BOS to every destination, so they describe the slot rather than this journey — the like-for-like comparison against the route is above. Hours are scheduled local, and a number whose schedule moved between banks inside the period has no single hour and is not described here at all. Why the hour matters.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · Hours below 120 departures are not scored.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · Days with fewer than 120 operations are not scored.

Because the same number has served different journeys, the statistics above describe only the route UA1732 currently operates. Blending them would produce an average of two different flights.

Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026

Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA1732 is placed in the same ordering rather than left out of it; the rows around it are the most punctual departures on the route, not all of them, so this is a comparison and not a rank. Schedules change; confirm the departure still operates before booking around this.

• UA2040 BOS→ORD United Airlines on the same route, departs 4:27 PM, on time 58.0%
• B6311 BOS→ORD JetBlue on the same route, departs 6:00 AM, on time 85.2%
• UA1414 BOS→ORD United Airlines on the same route, departs 6:00 AM, on time 93.4%
• UA1421 ORD→FLL United Airlines flight out of ORD, ORD to FLL, departs 7:00 AM, on time 91.5%