Flight profile · United Airlines
UA1738
Washington (IAD) to Chicago (ORD) · scheduled 10:10 PM – 11:15 PM
How UA1738 performs
759 operations, June 2024 – July 2026.
Source: US DOT Bureau of Transportation Statistics · 759 operations, June 2024 – July 2026 · If UA1738 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where UA1738 is right now
A live reading, only if you ask for it. It is not part of the reliability record above.
Ask for the position of UA1738 right now, if receivers on the ground are hearing it. Nothing is requested until you press the button.
Against the rest of the route
| Flight or route | On time | Cancelled | Median delay | Severe | Flights |
|---|---|---|---|---|---|
| UA1738 | 79.1% | 1.05% | -6 min | 8.3% | 759 |
| United Airlines on IAD → ORD | 78.2% | 0.87% | -5 min | 7.1% | 5,764 |
| All IAD → ORD flights | 78.2% | 0.87% | -5 min | 7.1% | 5,764 |
Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026
Why UA1738 runs late
Where US DOT attributed the delay minutes on this flight.
airspace and airport capacity, including weather-driven flow control
crew, maintenance, boarding and fueling, all within the carrier’s control
the inbound aircraft was late, so this flight started late
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for UA1738 on IAD → ORD. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies UA1738 comes in late, and what that does to the departure.
The aircraft flying UA1738 came in 15 or more minutes late on 19% 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 IAD just before it, using the tail number in the DOT file, 603 of 753 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.
Against the network at the same turn length
| Share of departures | Inbound landed 15+ late |
|---|---|
| UA1738 | 19% |
| Network, same turn | 17% |
The schedule leaves a normal turn: enough time to clean and board if the aircraft is on time, little to spare if it is not.
The network row is every flight with a scheduled turn of 60 to 89 minutes. How often UA1738’s aircraft landed 15 or more minutes late is about the same as the network’s. There are not enough departures in both groups to compare how it left.
More: Which Flight Numbers Pay for a Late Aircraft lists the flight numbers that pass a late aircraft on.
Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026
From pushback to gate
When it leaves IAD late, does that still matter by the time it reaches ORD?
UA1738 pushes back an average of 14.1 minutes late and reaches the gate at ORD an average of 8.9 minutes late. The 5.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. Its 21.1 minutes on the taxiways at IAD is about what any departure from the airport in that hour spends.
On arrival at ORD, UA1738 spends 9.8 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 8.0 minutes shorter than a typical ORD arrival (17.8 min).
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 17,830 departures from IAD scheduled in the clock hour UA1738 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 UA1738’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026
The hour it leaves IAD
Part of any flight’s record belongs to the clock rather than to the flight. UA1738 has one departure time, so this is what that time is worth.
On-time arrival rate. 17,830 departures from IAD are scheduled in the 10 PM–11 PM hour over the period, against 170,208 across the whole day.
UA1738 is scheduled out of IAD at 10:10 PM, in the 10 PM–11 PM bank. Departures from IAD in that hour arrive on time 78.7% of the time against 81.0% across the airport’s whole day, so the hour UA1738 leaves in is an ordinary one for IAD and explains nothing about its record either way.
The two airport figures cover every departure from IAD 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 · June 2024 – July 2026 · Hours below 120 departures are not scored.
Other routes UA1738 has flown
A flight number is a slot in a schedule, and carriers reassign it. These are the other city pairs this number served in the analysis period.
| Route | Operated | Flights | On time |
|---|---|---|---|
| SFO→IAD San Francisco to Washington | February 15, 2024 – January 5, 2026 | 253 | 78.7% |
| SAN→IAD San Diego to Washington | November 1, 2024 – December 2, 2024 | 31 | — |
| IAD→LAX Washington to Los Angeles | July 2, 2023 – June 26, 2024 | 244 | 83.4% |
| ORF→IAH Norfolk to Houston | February 1–14, 2024 | 14 | — |
| TUS→IAH Tucson to Houston | January 9–31, 2024 | 23 | — |
Because the same number has served different journeys, the statistics above describe only the route UA1738 currently operates. Blending them would produce an average of two different flights.
When it goes wrong
The average describes a usual day. This is the day that ruins a connection.
47 min late
against a median of 6 min early
Percentiles over 759 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026
Other flights on this route
Same airports, same journey, different odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| UA1738 this flight | United Airlines | 79.1% | 6 min early | 759 |
| UA2497 | United Airlines | 57.0% | 9 min late | 946 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA1738 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.
Data and methodology
Calculated by FlyerIntel from 759 records of UA1738 operating IAD → ORD, published by the US DOT Bureau of Transportation Statistics. A flight counts as delayed when it arrives 15 or more minutes after schedule. Cancelled and diverted flights are excluded from the on-time rate and reported separately. Flight numbers are resolved as carrier plus number plus route, because the same number serves different routes over time.
Full methodology · Data sources · Report a problem
Related research: Most and Least Reliable Flight Numbers · The Delay You Inherit · Making Up Time in the Air
Analysis last recomputed