Flight profile · United Airlines
UA373
Honolulu (HNL) to San Francisco (SFO) · scheduled 7:00 AM – 3:16 PM
How UA373 performs
601 operations, October 2024 – July 2026.
UA373 arrived on time 90.4% of the time, against 81.5% for all HNL → SFO flights, so this departure is 8.9 percentage points better than the route as a whole. Against United Airlines’ own flights on this route it is 3.0 points better.
UA373’s scheduled departure has moved during the period FlyerIntel has on file: it typically left around 7:00 AM earlier on, and around 8:00 AM more recently — a 60-minute shift, not the few minutes of day-to-day rounding every published schedule carries. Confirm the current departure time before booking around an older listing.
Source: US DOT Bureau of Transportation Statistics · 601 operations, October 2024 – July 2026 · If UA373 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where UA373 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 UA373 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 |
|---|---|---|---|---|---|
| UA373 | 90.4% | 1.00% | -12 min | 4.2% | 601 |
| United Airlines on HNL → SFO | 87.4% | 0.69% | -10 min | 3.8% | 5,363 |
| All HNL → SFO flights | 81.5% | 1.26% | -7 min | 4.9% | 7,806 |
Source: FlyerIntel analysis of US DOT BTS data · October 2024 – July 2026
Why UA373 runs late
Where US DOT attributed the delay minutes on this flight.
crew, maintenance, boarding and fueling, all within the carrier’s control
the inbound aircraft was late, so this flight started late
airspace and airport capacity, including weather-driven flow control
Share of the delay minutes US DOT attributed to each cause for UA373 on HNL → SFO. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering October 2024 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies UA373 comes in late, and what that does to the departure.
UA373 is usually the aircraft’s first flight of the day: the schedule gives it a median of 11.2 hours on the ground at HNL, so its “inbound” is mostly the aircraft’s arrival the evening before.
The aircraft flying UA373 came in 15 or more minutes late on 22% 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 HNL just before it, using the tail number in the DOT file, 294 of 596 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 |
|---|---|
| UA373 | 22% |
| Network, same turn | 29% |
A night on the ground absorbs most of a late arrival, so a late inbound matters far less on a turn this long than on a same-day one.
The network row is every flight with a scheduled turn of 6 hours or more, usually overnight. How often UA373’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 October 2024 – July 2026
From pushback to gate
When it leaves HNL late, does that still matter by the time it reaches SFO?
UA373 pushes back an average of 9.4 minutes late and reaches the gate at SFO an average of 0.9 minutes late. The 8.4 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.8 minutes on the taxiways at HNL, 3.5 minutes longer than a typical HNL departure in the same hour.
On arrival at SFO, UA373 spends 7.0 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 10,197 departures from HNL scheduled in the clock hour UA373 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 UA373’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · October 2024 – July 2026
The hour it leaves HNL
Part of any flight’s record belongs to the clock rather than to the flight. UA373 has one departure time, so this is what that time is worth.
On-time arrival rate. 10,197 departures from HNL are scheduled in the 7 AM–8 AM hour over the period, against 186,300 across the whole day.
UA373 is scheduled out of HNL at 7:00 AM, in the 7 AM–8 AM bank. Departures from HNL in that hour arrive on time 91.6% of the time against 85.3% across the airport’s whole day — the slot alone is worth 6.3 points better before anything about this particular flight is considered.
The two airport figures cover every departure from HNL 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 · October 2024 – July 2026 · Hours below 120 departures are not scored.
Other routes UA373 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→BNA San Francisco to Nashville | June 25, 2026 – July 31, 2026 | 21 | — |
| SFO→AUS San Francisco to Austin | May 23, 2025 – June 24, 2026 | 43 | — |
| SFO→MSP San Francisco to Minneapolis | April 1, 2026 – May 20, 2026 | 43 | — |
| SFO→PHX San Francisco to Phoenix | February 12, 2026 – March 4, 2026 | 21 | — |
| SFO→ONT San Francisco to Ontario | January 7, 2026 – February 11, 2026 | 29 | — |
| SFO→DEN San Francisco to Denver | October 27, 2024 – January 5, 2026 | 55 | — |
| SFO→MSY San Francisco to New Orleans | September 25–28, 2025 | 4 | — |
| SFO→BUR San Francisco to Burbank | August 19, 2025 – September 24, 2025 | 37 | — |
| SFO→SNA San Francisco to Santa Ana | August 1–18, 2025 | 18 | — |
| SNA→EWR Santa Ana to Newark | August 1–18, 2025 | 18 | — |
| ATL→IAD Atlanta to Washington | October 29, 2023 – May 22, 2025 | 2 | — |
| IAH→ORD Houston to Chicago | May 2–21, 2025 | 20 | — |
| CHS→IAD Charleston to Washington | March 30, 2025 | 1 | — |
| SFO→LAS San Francisco to Las Vegas | December 19, 2024 – February 12, 2025 | 56 | — |
| SFO→ORD San Francisco to Chicago | May 4, 2024 – December 16, 2024 | 12 | — |
| DEN→ATL Denver to Atlanta | September 26, 2024 – October 26, 2024 | 31 | — |
| ORD→DEN Chicago to Denver | September 26, 2024 – October 26, 2024 | 31 | — |
| EWR→LAS Newark to Las Vegas | May 23, 2024 – September 25, 2024 | 126 | 97.5% |
| LAS→DEN Las Vegas to Denver | June 27–30, 2024 | 4 | — |
| BUR→SFO Burbank to San Francisco | May 3–22, 2024 | 20 | — |
| CLE→ORD Cleveland to Chicago | May 2, 2024 | 1 | — |
| DEN→IAH Denver to Houston | March 31, 2024 – May 1, 2024 | 32 | — |
| IAH→MSY Houston to New Orleans | April 1, 2024 – May 1, 2024 | 23 | — |
| DEN→EWR Denver to Newark | March 7–30, 2024 | 24 | — |
| BTV→ORD Burlington to Chicago | July 1, 2023 – March 6, 2024 | 220 | 85.8% |
| ORD→LAS Chicago to Las Vegas | February 15, 2024 – March 6, 2024 | 21 | — |
| ORD→SRQ Chicago to Sarasota/Bradenton | December 21, 2023 – January 8, 2024 | 18 | — |
| BNA→EWR Nashville to Newark | October 30, 2023 – November 27, 2023 | 19 | — |
| OMA→DEN Omaha to Denver | November 26, 2023 | 1 | — |
Because the same number has served different journeys, the statistics above describe only the route UA373 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.
14 min late
against a median of 12 min early
Percentiles over 601 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering October 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 |
|---|---|---|---|---|
| UA373 this flight | United Airlines | 90.4% | 12 min early | 601 |
| UA1947 | United Airlines | 85.4% | 8 min early | 808 |
| UA1141 | United Airlines | 79.7% | 5 min early | 809 |
| AS876 | Alaska Airlines | 73.0% | 2 min early | 620 |
| HA12 | Hawaiian Airlines | 61.7% | 9 min late | 847 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA373 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 601 records of UA373 operating HNL → 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