Flight profile · JetBlue

B6334

San Juan (SJU) to Orlando (MCO) · scheduled 9:45 PM – 12:47 AM

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

136 operations, 2025-06-12 to 2026-06-30.

On-time arrivals
69.6%
94 of 135 completed
Cancellation rate
0.00%
0 cancelled
Median arrival delay
-4 min
Average 15.0 min
Severe delays
18.5%
Arrived 60+ minutes late
Delay when late
74 min
Average, when 15+ min late
Departure punctuality
67.6%
Left the gate on time

B6334 arrived on time 69.6% of the time, against 77.3% for all SJUMCO flights — this specific departure is 7.7 percentage points worse than the route as a whole. Against JetBlue’s own flights on this route it is 5.4 points worse.

Source: US DOT Bureau of Transportation Statistics · 136 operations between 2025-06-12 to 2026-06-30

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B633469.6%0.00%-4 min18.5%136
JetBlue on SJUMCO75.0%1.06%-6 min10.9%6,115
All SJUMCO flights77.3%1.08%-5 min8.7%18,752

Source: FlyerIntel analysis of US DOT BTS data · 2025-06-12 to 2026-06-30

Other routes B6334 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
SFOBOS San Francisco to Boston2023-07-022026-04-2855076.2%

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

Data and methodology

Calculated by FlyerIntel from 136 records of B6334 operating SJUMCO, 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