Flight profile · United Airlines
UA1757
Washington (IAD) to San Francisco (SFO) · scheduled 5:55 PM – 8:50 PM
How UA1757 performs
616 operations, September 2024 – July 2026.
UA1757 arrived on time 56.1% of the time, against 78.5% for all IAD → SFO flights, so this departure is 22.4 percentage points worse than the route as a whole. Against United Airlines’ own flights on this route it is 23.2 points worse.
Source: US DOT Bureau of Transportation Statistics · 616 operations, September 2024 – July 2026 · If UA1757 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
What stands out
How UA1757 compares to other flight numbers, not just to itself.
This flight runs unusually far behind the carrier's own average on this route, worse than 99% of 11,589 comparable flight numbers.
56.1% on time for this specific departure, against 79.3% for the same carrier's other flights on this route.
Source: FlyerIntel analysis of US DOT BTS data · September 2024 – 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.
Where UA1757 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 UA1757 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 |
|---|---|---|---|---|---|
| UA1757 | 56.1% | 1.79% | 10 min | 17.7% | 616 |
| United Airlines on IAD → SFO | 79.3% | 0.97% | -7 min | 7.2% | 7,512 |
| All IAD → SFO flights | 78.5% | 0.98% | -7 min | 7.5% | 8,482 |
Source: FlyerIntel analysis of US DOT BTS data · September 2024 – July 2026
Why UA1757 runs late
Where US DOT attributed the delay minutes on this flight.
crew, maintenance, boarding and fueling, all within the carrier’s control
airspace and airport capacity, including weather-driven flow 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 UA1757 on IAD → SFO. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering September 2024 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies UA1757 comes in late, and what that does to the departure.
The aircraft flying UA1757 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, 429 of 605 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 |
|---|---|
| UA1757 | 19% |
| Network, same turn | 23% |
The schedule leaves a long gap on the ground, which gives a late aircraft room to catch up before this flight pushes back.
The network row is every flight with a scheduled turn of 90 minutes to 3 hours. How often UA1757’s aircraft landed 15 or more minutes late is lower than 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 September 2024 – July 2026
From pushback to gate
When it leaves IAD late, does that still matter by the time it reaches SFO?
On arrival at SFO, UA1757 spends 10.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 2.9 minutes longer than a typical SFO arrival (7.9 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 SFO. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 37,767 departures from IAD scheduled in the clock hour UA1757 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at SFO (436,060 flights), not just UA1757’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · September 2024 – July 2026
The hour it leaves IAD
Part of any flight’s record belongs to the clock rather than to the flight. UA1757 has one departure time, so this is what that time is worth.
On-time arrival rate. 37,767 departures from IAD are scheduled in the 5 PM–6 PM hour over the period, against 170,208 across the whole day.
UA1757 is scheduled out of IAD at 5:55 PM, in the 5 PM–6 PM bank. Departures from IAD in that hour arrive on time 72.1% of the time against 81.0% across the airport’s whole day — the slot alone is worth 8.9 points worse before anything about this particular flight is considered.
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 · September 2024 – July 2026 · Hours below 120 departures are not scored.
Other routes UA1757 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→RNO San Francisco to Reno | December 19, 2024 – July 31, 2026 | 418 | 69.5% |
| MCO→IAD Orlando to Washington | May 22, 2025 – January 5, 2026 | 101 | 86.1% |
| ORD→IAD Chicago to Washington | September 2–24, 2025 | 23 | — |
| MSY→IAD New Orleans to Washington | January 7, 2025 – February 12, 2025 | 32 | — |
| JAX→IAD Jacksonville to Washington | March 7, 2024 – December 2, 2024 | 234 | 78.6% |
| ORD→JAX Chicago to Jacksonville | June 27, 2024 – December 2, 2024 | 65 | — |
| SFO→SBA San Francisco to Santa Barbara | February 15, 2024 – March 6, 2024 | 21 | — |
| SLC→SFO Salt Lake City to San Francisco | February 15, 2024 – March 6, 2024 | 21 | — |
| ORD→CLT Chicago to Charlotte | January 9, 2024 – February 14, 2024 | 36 | — |
| LAS→EWR Las Vegas to Newark | February 12, 2024 | 1 | — |
| ORD→DEN Chicago to Denver | December 21, 2023 – January 8, 2024 | 19 | — |
| EWR→DFW Newark to Dallas–Fort Worth | November 1, 2023 – December 20, 2023 | 42 | — |
| EWR→DTW Newark to Detroit | November 5, 2023 | 1 | — |
| EWR→SEA Newark to Seattle | August 1, 2023 – October 28, 2023 | 89 | — |
| SEA→ORD Seattle to Chicago | October 1–28, 2023 | 28 | — |
| SYR→EWR Syracuse to Newark | August 1, 2023 – September 4, 2023 | 35 | — |
| JAC→EWR Jackson to Newark | July 1–31, 2023 | 31 | — |
| EWR→CHS Newark to Charleston | July 3–31, 2023 | 22 | — |
Because the same number has served different journeys, the statistics above describe only the route UA1757 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.
115 min late
against a median of 10 min late
UA1757 has an average that understates its risk: a typical arrival is 10 min late, but the worst tenth are 105 minutes worse than that. If the trip has something unmissable at the end of it, the median is the wrong number to plan against.
Percentiles over 616 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering September 2024 – July 2026
Data and methodology
Calculated by FlyerIntel from 616 records of UA1757 operating IAD → SFO, 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