Flight profile · JetBlue
B62120
San Diego (SAN) to Boston (BOS) · scheduled 8:10 PM – 5:00 AM
How B62120 performs
1,052 operations, July 2023 – July 2026.
B62120 arrived on time 78.8% of the time, against 75.5% for all SAN → BOS flights, so this departure is 3.3 percentage points better than the route as a whole. Against JetBlue’s own flights on this route it is 5.7 points better.
Source: US DOT Bureau of Transportation Statistics · 1,052 operations, July 2023 – July 2026 · If B62120 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where B62120 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 B62120 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 |
|---|---|---|---|---|---|
| B62120 | 78.8% | 0.48% | -10 min | 9.3% | 1,052 |
| JetBlue on SAN → BOS | 73.1% | 0.91% | -7 min | 11.1% | 2,514 |
| All SAN → BOS flights | 75.5% | 0.86% | -6 min | 8.8% | 5,087 |
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026
Why B62120 runs late
Where US DOT attributed the delay minutes on this flight.
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
airspace and airport capacity, including weather-driven flow control
screening or terminal security incidents
Share of the delay minutes US DOT attributed to each cause for B62120 on SAN → BOS. 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 B62120 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, B62120 pushed back an average of 63 minutes late; when it came in on time or early, an average of 2 minutes late.
Each departure is matched to the flight the same aircraft flew into SAN just before it, using the tail number in the DOT file, 1,032 of 1,047 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 | Left 15+ late after a late inbound | Left 15+ late after an on-time inbound |
|---|---|---|---|
| B62120 | 22% | 73% | 8% |
| Network, same turn | 17% | 68% | 9% |
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 B62120’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often B62120 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 SAN late, does that still matter by the time it reaches BOS?
B62120 pushes back an average of 19.7 minutes late and reaches the gate at BOS an average of 10.1 minutes late. The 9.6 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. Its 20.4 minutes on the taxiways at SAN is about what any departure from the airport in that hour spends.
On arrival at BOS, B62120 spends 7.4 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 1.5 minutes shorter than a typical BOS arrival (9.0 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 BOS. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 14,722 departures from SAN scheduled in the clock hour B62120 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at BOS (440,886 flights), not just B62120’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026
The hour it leaves SAN
Part of any flight’s record belongs to the clock rather than to the flight. B62120 has one departure time, so this is what that time is worth.
On-time arrival rate. 14,722 departures from SAN are scheduled in the 8 PM–9 PM hour over the period, against 297,668 across the whole day.
B62120 is scheduled out of SAN at 8:10 PM, in the 8 PM–9 PM bank. Departures from SAN in that hour arrive on time 69.1% of the time against 77.9% across the airport’s whole day — the slot alone is worth 8.8 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from SAN 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 B62120 run worse on particular days?
Wednesday is historically the most reliable day and Sunday the least, a gap of 15.7 percentage points.
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · Days with fewer than 120 operations are not scored.
When it goes wrong
The average describes a usual day. This is the day that ruins a connection.
54 min late
against a median of 10 min early
B62120 has an average that understates its risk: a typical arrival is 10 min early, but the worst tenth are 64 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 1,052 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.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| B62120 this flight | JetBlue | 78.8% | 10 min early | 1,052 |
| AS390 | Alaska Airlines | 74.9% | 3 min early | 1,074 |
| B6620 | JetBlue | 69.7% | 4 min early | 848 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. B62120 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,052 records of B62120 operating SAN → BOS, 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