Flight profile · United Airlines
UA1769
Raleigh–Durham (RDU) to San Francisco (SFO) · scheduled 6:15 PM – 9:50 PM
How UA1769 performs
961 operations, July 2023 – July 2026.
UA1769 arrived on time 72.4% of the time, against 80.5% for all RDU → SFO flights, so this departure is 8.1 percentage points worse than the route as a whole. Against United Airlines’ own flights on this route it is 8.1 points worse.
Source: US DOT Bureau of Transportation Statistics · 961 operations, July 2023 – July 2026 · If UA1769 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where UA1769 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 UA1769 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 |
|---|---|---|---|---|---|
| UA1769 | 72.4% | 0.52% | -4 min | 9.9% | 961 |
| United Airlines on RDU → SFO | 80.5% | 0.38% | -8 min | 6.2% | 2,363 |
| All RDU → SFO flights | 80.5% | 0.38% | -8 min | 6.2% | 2,363 |
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026
Why UA1769 runs late
Where US DOT attributed the delay minutes on this flight.
airspace and airport capacity, including weather-driven flow control
the inbound aircraft was late, so this flight started late
crew, maintenance, boarding and fueling, all within the carrier’s control
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for UA1769 on RDU → SFO. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies UA1769 comes in late, and what that does to the departure.
The aircraft flying UA1769 came in 15 or more minutes late on 12% 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 RDU just before it, using the tail number in the DOT file, 944 of 956 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 |
|---|---|
| UA1769 | 12% |
| 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 UA1769’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 July 2023 – July 2026
From pushback to gate
When it leaves RDU late, does that still matter by the time it reaches SFO?
UA1769 pushes back an average of 20.4 minutes late and reaches the gate at SFO an average of 11.1 minutes late. The 9.3 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 18.9 minutes on the taxiways at RDU, 1.3 minutes longer than a typical RDU departure in the same hour.
On arrival at SFO, UA1769 spends 8.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 about what any arrival at SFO 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 SFO. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 14,289 departures from RDU scheduled in the clock hour UA1769 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 UA1769’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026
The hour it leaves RDU
Part of any flight’s record belongs to the clock rather than to the flight. UA1769 has one departure time, so this is what that time is worth.
On-time arrival rate. 14,289 departures from RDU are scheduled in the 6 PM–7 PM hour over the period, against 179,935 across the whole day.
UA1769 is scheduled out of RDU at 6:15 PM, in the 6 PM–7 PM bank. Departures from RDU in that hour arrive on time 69.3% of the time against 79.4% across the airport’s whole day — the slot alone is worth 10.0 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from RDU 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.
By day of week
Does UA1769 run worse on particular days?
Wednesday is historically the most reliable day and Sunday the least, a gap of 8.6 percentage points.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · Days with fewer than 120 operations are not scored.
Other routes UA1769 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.
Because the same number has served different journeys, the statistics above describe only the route UA1769 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.
59 min late
against a median of 4 min early
UA1769 has an average that understates its risk: a typical arrival is 4 min early, but the worst tenth are 63 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 961 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026
Data and methodology
Calculated by FlyerIntel from 961 records of UA1769 operating RDU → 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