The aircraft before your flight / July 2025
Your plane
has had a day.
One aircraft left San Francisco two and a half hours late. Its next departure was only eleven minutes late. What happened between those flights?
SFO → HNL+150min
HNL → PPG+11min
PPG → HNL+12min
Tail N393HA · flights scheduled July 10, 2025 · minutes relative to each departure’s own schedule
Follow its day ↓01 / BEFORE YOUR FLIGHT
There is another timetable behind your boarding pass.
The plane at your gate may already have made several trips. Every stop gives it a chance to lose time or catch up: a late arrival might use up a long layover, or leave the next flight waiting. Following the aircraft shows how its delay changes through the day.
These three journeys come from Hawaiian’s July 2025 flight records, reported to the Bureau of Transportation Statistics. Each illustrates a pattern: staying near schedule, recovering from a delay, or remaining late. We chose short journeys so you can follow every leg; the full comparison appears below.
01Near schedule
Los Angeles to Maui, then Seattle and Anchorage: departures 4 minutes early, 5 early, and 9 late. At the last arrival, the aircraft was 13 minutes early.
02Delay, then recovery
San Francisco to Honolulu, then Pago Pago and back: 150 minutes late became 11, then 12. The last arrival was on July 11, two minutes early.
03Delay that persists
Honolulu to San Diego and back, then another San Diego flight: 2 minutes early, 62 late, then 35 late. Some delay was absorbed; a late departure remained.
The third aircraft recovered 27 minutes between departures and still left 35 minutes late. Catching up can take more than one stop.
02 / FOLLOW THE SAME AIRCRAFT
The day, leg by leg.
N393HA, 2025-07-10: 3 reported flights. Departure deviations: +150, +11, +12 minutes. Delay, then recovery.
Read left to right through airport lanes. Sloping bands are flights; horizontal stretches are ground intervals. Their separation shows where the schedule and reported day diverge or converge. Airport spacing does not encode distance or speed. Both paths use UTC; clock labels below can change independently.
Scheduled · hatched Actual · solid
Loading the chart enhancement. All times are in the itinerary below.
Before this window:HA 12 · HNL → SFO, scheduled date 2025-07-09. Tail, airport and chronology are consistent with the first leg shown.
Scheduled departureJul 10, 09:35 PDT
Actual departureJul 10, 12:05 PDT
Arrivals and original reporting fields
Scheduled arrival: Jul 10, 12:00 HST
Actual arrival: Jul 10, 14:34 HST
Signed arrival deviation: +154 min. Scheduled / actual gate-to-gate durations:325 /329 min.
Reported categories on this row: CarrierDelay 154 min; WeatherDelay 0 min; NASDelay 0 min; SecurityDelay 0 min; LateAircraftDelay 0 min. These are reporting categories, not a reconstruction of the aircraft's whole day.
Cancellation flag: 0.00; diversion flag: 0.00. BTS archive CSV record line 584013.
2025-07-10~HA~11~14771~12173~0935127 min on the ground at HNL between the reported flights
Scheduled departureJul 10, 16:30 HST
Actual departureJul 10, 16:41 HST
Arrivals and original reporting fields
Scheduled arrival: Jul 10, 21:10 GMT-11
Actual arrival: Jul 10, 21:09 GMT-11
Signed arrival deviation: -1 min. Scheduled / actual gate-to-gate durations:340 /328 min.
No delay-cause values were supplied on this row. Blank is not evidence of no cause.
Cancellation flag: 0.00; diversion flag: 0.00. BTS archive CSV record line 589260.
2025-07-10~HA~465~12173~14222~1630133 min on the ground at PPG between the reported flights
Scheduled departureJul 10, 23:10 GMT-11
Actual departureJul 10, 23:22 GMT-11
Arrivals and original reporting fields
Scheduled arrival: Jul 11, 05:40 HST
Actual arrival: Jul 11, 05:38 HST
Signed arrival deviation: -2 min. Scheduled / actual gate-to-gate durations:330 /316 min.
No delay-cause values were supplied on this row. Blank is not evidence of no cause.
Cancellation flag: 0.00; diversion flag: 0.00. BTS archive CSV record line 589274.
2025-07-10~HA~466~14222~12173~2310
After this window:HA 628 · HNL → SAN, scheduled date 2025-07-11. Tail, airport and chronology are consistent with the last leg shown.This window does not describe every use of the aircraft.
03 / THE REST OF THE MONTH
How often did these patterns appear?
Of 660 aircraft-days with at least three connected flights, 334 stayed near schedule, 11 met our recovery rule, and 24 met our persistence rule. The other 291 followed different patterns. Use the controls to explore the journeys behind those counts.
334 / 660Near schedule ·50.6%
11 / 660Delay, then recovery ·1.7%
24 / 660Delay that persists ·3.6%
291 / 660Other eligible patterns ·44.1%
The July 2–30 records contain 1,627 aircraft-days with a tail number. Of these, 941 have fewer than three flights and 48 have a reporting or continuity break; 22 fall into both groups. Excluding them leaves 660 days. This favors longer itineraries, so the counts describe that group rather than Hawaiian’s overall on-time performance.
All checked, internally continuous sequences of at least three reported flights.660 aircraft-days selected.
Departure distribution is loading.
Read the distribution counts
- Early (<0):2439checked flight rows
- 0–14 min:1694checked flight rows
- 15–59 min:616checked flight rows
- 60–119 min:70checked flight rows
- 120+ min:28checked flight rows
Each flight contributes once. Missing actual times are excluded; other flights on an ineligible day can still have valid reported times.
04 / TIME TO CATCH UP
A long layover can absorb a late arrival.
The recovery flight arrived 154 minutes late. But its schedule allowed 270 minutes on the ground before the next departure. The plane actually spent 127 minutes there and left just 11 minutes late. Most of the delay had used up time between flights.
That timetable explains where the aircraft caught up. For reported causes of delay, look at the BTS categories under each flight. Those entries cover individual flights; the sequence alone cannot tell us why the first flight was late or what happened during a stop.
We connect records when the tail number, airports and times agree, stopping at an unresolved record or a gap longer than twelve hours. Flights outside this reporting extract may be missing from the sequence.
A delay belongs to a flight’s schedule, and the next flight has a schedule of its own. The time between them can determine whether a late arrival becomes another late departure. That is why the aircraft’s earlier journey is worth a look when you are waiting at the gate.
05 / TAKE THE FLIGHT WITH YOU
Save a flight and your notes.
Pin a flight and add a note. Its link or downloaded packet will reopen the same flight and notes in another session. Notes are stored in the link or file, so anyone you share it with can read them.