Flight profile · JetBlue
B6733
Boston (BOS) to San Francisco (SFO) · scheduled 6:30 PM – 10:15 PM
How B6733 performs
794 operations, September 2023 – July 2026.
B6733 arrived on time 68.2% of the time, against 74.6% for all BOS → SFO flights, so this departure is 6.4 percentage points worse than the route as a whole. Against JetBlue’s own flights on this route it is 3.6 points worse.
Source: US DOT Bureau of Transportation Statistics · 794 operations, September 2023 – July 2026 · If B6733 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where B6733 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 B6733 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 |
|---|---|---|---|---|---|
| B6733 | 68.2% | 0.76% | -3 min | 12.6% | 794 |
| JetBlue on BOS → SFO | 71.8% | 0.89% | -5 min | 10.3% | 5,059 |
| All BOS → SFO flights | 74.6% | 1.03% | -6 min | 8.8% | 14,232 |
Source: FlyerIntel analysis of US DOT BTS data · September 2023 – July 2026
Why B6733 runs late
Where US DOT attributed the delay minutes on this flight.
airspace and airport capacity, including weather-driven flow control
crew, maintenance, boarding and fueling, all within the carrier’s control
the inbound aircraft was late, so this flight started late
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for B6733 on BOS → SFO. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering September 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies B6733 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, B6733 pushed back an average of 39 minutes late; when it came in on time or early, an average of 11 minutes late.
Each departure is matched to the flight the same aircraft flew into BOS just before it, using the tail number in the DOT file, 573 of 788 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 |
|---|---|---|---|
| B6733 | 21% | 54% | 22% |
| 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 B6733’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often B6733 left 15 or more minutes late is lower 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 September 2023 – July 2026
From pushback to gate
When it leaves BOS late, does that still matter by the time it reaches SFO?
B6733 pushes back an average of 20.6 minutes late and reaches the gate at SFO an average of 12.5 minutes late. The 8.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. It spends 21.8 minutes on the taxiways at BOS, 1.6 minutes shorter than a typical BOS departure in the same hour.
On arrival at SFO, B6733 spends 10.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 2.1 minutes longer than a typical SFO arrival (7.9 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 SFO. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 27,363 departures from BOS scheduled in the clock hour B6733 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 B6733’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · September 2023 – July 2026
The hour it leaves BOS
Part of any flight’s record belongs to the clock rather than to the flight. B6733 has one departure time, so this is what that time is worth.
On-time arrival rate. 27,363 departures from BOS are scheduled in the 6 PM–7 PM hour over the period, against 440,893 across the whole day.
B6733 is scheduled out of BOS at 6:30 PM, in the 6 PM–7 PM bank. Departures from BOS in that hour arrive on time 66.3% of the time against 77.2% across the airport’s whole day — the slot alone is worth 10.9 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from BOS 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 · September 2023 – July 2026 · Hours below 120 departures are not scored.
Other routes B6733 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 |
|---|---|---|---|
| BDL→TPA Hartford to Tampa | February 15, 2024 – April 30, 2024 | 76 | — |
Because the same number has served different journeys, the statistics above describe only the route B6733 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.
69 min late
against a median of 3 min early
B6733 has an average that understates its risk: a typical arrival is 3 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 794 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering September 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 |
|---|---|---|---|---|
| UA1008 | United Airlines | 88.0% | 12 min early | 954 |
| B61333 | JetBlue | 84.3% | 12 min early | 601 |
| UA1187 | United Airlines | 81.0% | 12 min early | 604 |
| DL977 | Delta Air Lines | 80.8% | 8 min early | 893 |
| B6133 | JetBlue | 80.2% | 10 min early | 660 |
| B61833 | JetBlue | 79.3% | 12 min early | 712 |
| AS357 | Alaska Airlines | 68.6% | 2 min early | 636 |
| DL475 | Delta Air Lines | 68.4% | 3 min early | 744 |
| B6733 this flight | JetBlue | 68.2% | 3 min early | 794 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. B6733 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 794 records of B6733 operating BOS → 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