Flight profile · JetBlue

B6698

Orlando (MCO) to New York (LGA) · scheduled 10:25 AM – 3:05 PM

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

672 operations, 2023-07-01 to 2026-06-30.

On-time arrivals
71.5%
474 of 663 completed
Cancellation rate
0.74%
5 cancelled
Median arrival delay
-3 min
Average 12.5 min
Severe delays
10.9%
Arrived 60+ minutes late
Delay when late
65 min
Average, when 15+ min late
Departure punctuality
74.5%
Left the gate on time

B6698 arrived on time 71.5% of the time, against 73.0% for all MCOLGA flights — this specific departure is 1.5 percentage points worse than the route as a whole. Against JetBlue’s own flights on this route it is 4.5 points better.

Source: US DOT Bureau of Transportation Statistics · 672 operations between 2023-07-01 to 2026-06-30

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B669871.5%0.74%-3 min10.9%672
JetBlue on MCOLGA67.0%2.09%-2 min15.4%4,353
All MCOLGA flights73.0%2.54%-6 min11.6%15,619

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

Other routes B6698 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
PITJFK Pittsburgh to New York2025-11-202025-12-0111

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

Data and methodology

Calculated by FlyerIntel from 672 records of B6698 operating MCOLGA, 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