Flight profile · JetBlue
B6620
San Diego (SAN) to Boston (BOS) · scheduled 10:20 AM – 7:12 PM
How B6620 performs
848 operations, July 2023 – July 2026.
B6620 arrived on time 69.7% of the time, against 75.5% for all SAN → BOS flights, so this departure is 5.8 percentage points worse than the route as a whole. Against JetBlue’s own flights on this route it is 3.4 points worse.
Source: US DOT Bureau of Transportation Statistics · 848 operations, July 2023 – July 2026 · If B6620 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where B6620 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 B6620 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 |
|---|---|---|---|---|---|
| B6620 | 69.7% | 0.94% | -4 min | 12.0% | 848 |
| 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 B6620 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
screening or terminal security incidents
Share of the delay minutes US DOT attributed to each cause for B6620 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 B6620 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, B6620 pushed back an average of 59 minutes late; when it came in on time or early, an average of 8 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, 829 of 840 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 |
|---|---|---|---|
| B6620 | 16% | 78% | 18% |
| 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 B6620’s aircraft landed 15 or more minutes late is about the same as the network’s and, once the aircraft was late, how often B6620 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?
B6620 pushes back an average of 18.1 minutes late and reaches the gate at BOS an average of 12.1 minutes late. The 6.0 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 22.7 minutes on the taxiways at SAN is about what any departure from the airport in that hour spends.
On arrival at BOS, B6620 spends 9.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 about what any arrival at BOS 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 BOS. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 21,520 departures from SAN scheduled in the clock hour B6620 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 B6620’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. B6620 has one departure time, so this is what that time is worth.
On-time arrival rate. 21,520 departures from SAN are scheduled in the 10 AM–11 AM hour over the period, against 297,668 across the whole day.
B6620 is scheduled out of SAN at 10:20 AM, in the 10 AM–11 AM bank. Departures from SAN in that hour arrive on time 80.4% of the time against 77.9% across the airport’s whole day, so the hour B6620 leaves in is an ordinary one for SAN and explains nothing about its record either way.
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 B6620 run worse on particular days?
Wednesday is historically the most reliable day and Monday the least, a gap of 6.0 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 B6620 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 |
|---|---|---|---|
| JFK→SJU New York to San Juan | December 15, 2023 | 1 | — |
Because the same number has served different journeys, the statistics above describe only the route B6620 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.
68 min late
against a median of 4 min early
B6620 has an average that understates its risk: a typical arrival is 4 min early, but the worst tenth are 72 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 848 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 | JetBlue | 78.8% | 10 min early | 1,052 |
| AS390 | Alaska Airlines | 74.9% | 3 min early | 1,074 |
| B6620 this flight | JetBlue | 69.7% | 4 min early | 848 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. B6620 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 848 records of B6620 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