Flight profile · JetBlue

B61652

Orlando (MCO) to Boston (BOS) · scheduled 6:00 AM – 9:04 AM

FlyerIntel does not track flights in the air. This page describes how B61652 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 B61652 performs

576 operations, 2023-09-06 to 2026-04-27.

On-time arrivals
79.5%
447 of 562 completed
Cancellation rate
2.08%
12 cancelled
Median arrival delay
-7 min
Average 9.1 min
Severe delays
9.4%
Arrived 60+ minutes late
Delay when late
85 min
Average, when 15+ min late
Departure punctuality
79.6%
Left the gate on time

B61652 arrived on time 79.5% of the time, against 72.7% for all MCOBOS flights — this specific departure is 6.9 percentage points better than the route as a whole. Against JetBlue’s own flights on this route it is 10.1 points better.

Source: US DOT Bureau of Transportation Statistics · 576 operations between 2023-09-06 to 2026-04-27

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B6165279.5%2.08%-7 min9.4%576
JetBlue on MCOBOS69.4%2.26%-3 min14.0%7,242
All MCOBOS flights72.7%2.05%-5 min11.9%14,564

Source: FlyerIntel analysis of US DOT BTS data · 2023-09-06 to 2026-04-27

Other routes B61652 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
SJUTPA San Juan to Tampa2023-07-082023-08-0610

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

Data and methodology

Calculated by FlyerIntel from 576 records of B61652 operating MCOBOS, 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