Flight profile · JetBlue

B6391

Boston (BOS) to Tampa (TPA) · scheduled 6:20 PM – 9:40 PM

This page describes how B6391 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 JetBlue.

How B6391 performs

611 operations, February 2024 – July 2026.

On-time arrivals
59.7%
354 of 593 completed
Cancellation rate
2.29%
14 cancelled
Median arrival delay
4 min
Average 22.7 min
Severe delays
17.2%
Arrived 60+ minutes late
Delay when late
75 min
Average, when 15+ min late
Departure punctuality
56.8%
Left the gate on time

B6391 arrived on time 59.7% of the time, against 73.8% for all BOS → TPA flights, so this departure is 14.1 percentage points worse than the route as a whole. Against JetBlue’s own flights on this route it is 12.7 points worse.

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

What stands out

How B6391 compares to other flight numbers, not just to itself.

This flight runs unusually far behind the carrier's own average on this route, worse than 93% of 11,589 comparable flight numbers.

59.7% on time for this specific departure, against 72.4% for the same carrier's other flights on this route.

Source: FlyerIntel analysis of US DOT BTS data · February 2024 – July 2026 · The one thing about this specific departure that ranks most extreme against every other published flight number, out of everything FlyerIntel checks — shown only when something clears a real statistical bar, not for every flight.

Where B6391 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 B6391 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
B639159.7%2.29%4 min17.2%611
JetBlue on BOS → TPA72.4%2.67%-5 min11.6%4,684
All BOS → TPA flights73.8%2.31%-6 min11.0%8,553

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

Why B6391 runs late

Where US DOT attributed the delay minutes on this flight.

Share of the delay minutes US DOT attributed to each cause for B6391 on BOS → TPA. Only delays of 15 minutes or more are attributed.

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

Does a late aircraft delay this flight?

How often the plane that flies B6391 comes in late, and what that does to the departure.

Inbound aircraft late
30%
145 of 491 departures came in 15+ minutes late
Scheduled time on the ground
66 minutes
Median at BOS between the inbound and this departure
Left 15+ late after a late inbound
87%
145 departures
Left 15+ late after an on-time inbound
21%
346 departures

When the aircraft came in 15 or more minutes late, B6391 pushed back an average of 71 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 BOS just before it, using the tail number in the DOT file, 491 of 597 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

B6391 against all flights with a scheduled turn of 60 to 89 minutes
Share of departuresInbound landed 15+ lateLeft 15+ late after a late inboundLeft 15+ late after an on-time inbound
B639130%87%21%
Network, same turn17%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 B6391’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often B6391 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 February 2024 – July 2026

From pushback to gate

When it leaves BOS late, does that still matter by the time it reaches TPA?

Leaves the gate
31.8 minutes late
Average over 597 pushbacks
Taxi out at BOS
21.2 min
23.4 min for the airport in this hour
Taxi in at TPA
6.8 min
5.9 min for a typical TPA arrival
Reaches the gate at TPA
22.7 minutes late
Average over 593 arrivals

B6391 pushes back an average of 31.8 minutes late and reaches the gate at TPA an average of 22.7 minutes late. The 9.1 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.2 minutes on the taxiways at BOS, 2.3 minutes shorter than a typical BOS departure in the same hour.

On arrival at TPA, B6391 spends 6.8 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 TPA 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 TPA. 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 B6391 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at TPA (242,635 flights), not just B6391’s own. More on taxi time.

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

The hour it leaves BOS

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

B639159.7%
All BOS departures, 6 PM–7 PM66.3%
All BOS departures, whole day77.2%

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.

B6391 is scheduled out of BOS at 6:20 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 · February 2024 – July 2026 · Hours below 120 departures are not scored.

Other routes B6391 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 B6391 has flown
RouteOperatedFlightsOn time
BUF→JFK Buffalo to New YorkOctober 27, 2024 – February 12, 202510667.0%

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

96 min late

against a median of 4 min late

Arrived an hour or more late17.2%
Typical delay when late75 min
Cancelled2.29%
Landed somewhere else0.65%

B6391 has an average that understates its risk: a typical arrival is 4 min late, but the worst tenth are 92 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 611 operations; cancelled and diverted flights are counted separately.

Source: US DOT Bureau of Transportation Statistics · Data covering February 2024 – 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
DL2706Delta Air Lines89.1%12 min early762
B6891JetBlue85.0%10 min early983
DL1439Delta Air Lines68.2%1 min early916
B6591JetBlue65.2%0 min early962
DL2234Delta Air Lines63.6%2 min early617
B6391 this flightJetBlue59.7%4 min late611

Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. B6391 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 611 records of B6391 operating BOS → TPA, 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