Flight profile · JetBlue

B61302

Phoenix (PHX) to Boston (BOS) · scheduled 10:05 PM – 5:00 AM

FlyerIntel does not track flights in the air. This page describes how B61302 has historically performed, which is a different and more useful question when you are deciding what to book. For today’s status, check with JetBlue.

How B61302 performs

657 operations, 2023-07-01 to 2026-05-26.

On-time arrivals
67.7%
439 of 648 completed
Cancellation rate
1.37%
9 cancelled
Median arrival delay
-3 min
Average 24.3 min
Severe delays
14.8%
Arrived 60+ minutes late
Delay when late
100 min
Average, when 15+ min late
Departure punctuality
66.7%
Left the gate on time

B61302 arrived on time 67.7% of the time, against 78.3% for all PHXBOS flights — this specific departure is 10.5 percentage points worse than the route as a whole. Against JetBlue’s own flights on this route it is 1.0 points worse.

Source: US DOT Bureau of Transportation Statistics · 657 operations between 2023-07-01 to 2026-05-26

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B6130267.7%1.37%-3 min14.8%657
JetBlue on PHXBOS68.8%1.20%-3 min13.3%1,162
All PHXBOS flights78.3%0.90%-6 min7.6%6,322

Source: FlyerIntel analysis of US DOT BTS data · 2023-07-01 to 2026-05-26

Other routes B61302 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.

RouteOperatedFlightsOn time
FLLJFK Fort Lauderdale to New York2025-09-032025-10-2553

Because the same number has served different journeys, the statistics above describe only the route B61302 currently operates. Blending them would produce an average of two different flights.

Data and methodology

Calculated by FlyerIntel from 657 records of B61302 operating PHXBOS, 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 · Report a problem