Flight profile · JetBlue

B6133

Orlando (MCO) to San Juan (SJU) · scheduled 5:55 PM – 8:53 PM

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

261 operations, 2024-08-06 to 2026-06-30.

On-time arrivals
85.4%
222 of 260 completed
Cancellation rate
0.38%
1 cancelled
Median arrival delay
-3 min
Average 6.5 min
Severe delays
3.8%
Arrived 60+ minutes late
Delay when late
72 min
Average, when 15+ min late
Departure punctuality
84.6%
Left the gate on time

B6133 arrived on time 85.4% of the time, against 73.9% for all MCOSJU flights — this specific departure is 11.5 percentage points better than the route as a whole. Against JetBlue’s own flights on this route it is 10.2 points better.

Source: US DOT Bureau of Transportation Statistics · 261 operations between 2024-08-06 to 2026-06-30

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B613385.4%0.38%-3 min3.8%261
JetBlue on MCOSJU75.2%1.00%-4 min9.9%6,122
All MCOSJU flights73.9%0.90%-2 min9.3%18,761

Source: FlyerIntel analysis of US DOT BTS data · 2024-08-06 to 2026-06-30

Other routes B6133 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
BOSSFO Boston to San Francisco2023-07-022026-04-2866080.2%

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

Data and methodology

Calculated by FlyerIntel from 261 records of B6133 operating MCOSJU, 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