Flight profile · United Airlines

UA300

San Francisco (SFO) to Honolulu (HNL) · scheduled 1:40 PM – 4:18 PM

This page describes how UA300 has historically performed, which is a different and more useful question when you are deciding what to book. The live position below is a reading from receivers on the ground, not flight status. For today’s status, check with United Airlines.

How UA300 performs

1,092 operations, July 2023 – July 2026.

On-time arrivals
81.4%
886 of 1,088 completed
Cancellation rate
0.27%
3 cancelled
Median arrival delay
-7 min
Average 3.2 min
Severe delays
7.8%
Arrived 60+ minutes late
Delay when late
72 min
Average, when 15+ min late
Departure punctuality
75.2%
Left the gate on time

UA300 arrived on time 81.4% of the time, against 80.0% for all SFO → HNL flights, so this departure is 1.4 percentage points better than the route as a whole. Against United Airlines’ own flights on this route it is 1.3 points worse.

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

Where UA300 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 UA300 right now, if receivers on the ground are hearing it. Nothing is requested until you press the button.

Against the rest of the route

Against the rest of the route
Flight or routeOn timeCancelledMedian delaySevereFlights
UA30081.4%0.27%-7 min7.8%1,092
United Airlines on SFO → HNL82.7%0.30%-7 min5.9%5,364
All SFO → HNL flights80.0%1.04%-5 min5.8%7,809

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

Why UA300 runs late

Where US DOT attributed the delay minutes on this flight.

Share of the delay minutes US DOT attributed to each cause for UA300 on SFO → HNL. 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 UA300 comes in late, and what that does to the departure.

Inbound aircraft late
20%
179 of 891 departures came in 15+ minutes late
Scheduled time on the ground
99 minutes
Median at SFO between the inbound and this departure
Left 15+ late after a late inbound
49%
179 departures
Left 15+ late after an on-time inbound
15%
712 departures

When the aircraft came in 15 or more minutes late, UA300 pushed back an average of 28 minutes late; when it came in on time or early, an average of 7 minutes late.

Each departure is matched to the flight the same aircraft flew into SFO just before it, using the tail number in the DOT file, 891 of 1,090 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

UA300 against all flights with a scheduled turn of 90 minutes to 3 hours
Share of departuresInbound landed 15+ lateLeft 15+ late after a late inboundLeft 15+ late after an on-time inbound
UA30020%49%15%
Network, same turn23%40%9%

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 UA300’s aircraft landed 15 or more minutes late is about the same as the network’s and, once the aircraft was late, how often UA300 left 15 or more minutes late is higher than the network’s.

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 SFO late, does that still matter by the time it reaches HNL?

Leaves the gate
16.8 minutes late
Average over 1,090 pushbacks
Taxi out at SFO
22.7 min
21.6 min for the airport in this hour
Taxi in at HNL
5.3 min
8.3 min for a typical HNL arrival
Reaches the gate at HNL
3.2 minutes late
Average over 1,088 arrivals

UA300 pushes back an average of 16.8 minutes late and reaches the gate at HNL an average of 3.2 minutes late. The 13.5 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 22.7 minutes on the taxiways at SFO, 1.1 minutes longer than a typical SFO departure in the same hour.

On arrival at HNL, UA300 spends 5.3 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 shorter than a typical HNL arrival (8.3 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 HNL. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 33,066 departures from SFO scheduled in the clock hour UA300 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at HNL (186,355 flights), not just UA300’s own. More on taxi time.

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

The hour it leaves SFO

Part of any flight’s record belongs to the clock rather than to the flight. UA300 has one departure time, so this is what that time is worth.

UA30081.4%
All SFO departures, 1 PM–2 PM73.7%
All SFO departures, whole day78.7%

On-time arrival rate. 33,066 departures from SFO are scheduled in the 1 PM–2 PM hour over the period, against 435,779 across the whole day.

UA300 is scheduled out of SFO at 1:40 PM, in the 1 PM–2 PM bank. Departures from SFO in that hour arrive on time 73.7% of the time against 78.7% across the airport’s whole day — the slot alone is worth 5.0 points worse before anything about this particular flight is considered.

The two airport figures cover every departure from SFO 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 UA300 run worse on particular days?

Monday82.7%
Tuesday83.9%
Wednesday78.8%
Thursday86.4%
Friday82.7%
Saturday80.6%
Sunday75.0%

Thursday is historically the most reliable day and Sunday the least, a gap of 11.4 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 UA300 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.

Other routes UA300 has flown
RouteOperatedFlightsOn time
ATL→SFO Atlanta to San FranciscoJanuary 27, 2026 – February 10, 20263—
FLL→SFO Fort Lauderdale to San FranciscoMarch 7–28, 202519—
MSY→SFO New Orleans to San FranciscoFebruary 13, 2025 – March 5, 202518—
TPA→SFO Tampa to San FranciscoDecember 21, 2023 – December 18, 202470—
ORD→SFO Chicago to San FranciscoMarch 31, 2024 – May 1, 202432—

Because the same number has served different journeys, the statistics above describe only the route UA300 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.

One arrival in ten is worse than

41 min late

against a median of 7 min early

Arrived an hour or more late7.8%
Typical delay when late72 min
Cancelled0.27%
Landed somewhere else0.09%

Percentiles over 1,092 operations; cancelled and diverted flights are counted separately.

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

Other flights on this route

Same airports, same journey, different odds of arriving on time.

Other flights on this route
FlightAirlineOn timeMedian arrivalOperations
UA638United Airlines89.4%11 min early708
UA1175United Airlines85.7%7 min early1,127
UA300 this flightUnited Airlines81.4%7 min early1,092
UA1509United Airlines80.8%7 min early1,106
UA2380United Airlines75.9%4 min early826
HA11Hawaiian Airlines73.5%2 min late848

Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. UA300 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 1,092 records of UA300 operating SFO → HNL, 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