Flight profile · JetBlue

B6984

Raleigh–Durham (RDU) to Boston (BOS) · scheduled 6:00 AM – 7:59 AM

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

391 operations, 2023-07-02 to 2026-05-18.

On-time arrivals
85.6%
327 of 382 completed
Cancellation rate
2.30%
9 cancelled
Median arrival delay
-14 min
Average -6.5 min
Severe delays
2.6%
Arrived 60+ minutes late
Delay when late
45 min
Average, when 15+ min late
Departure punctuality
87.2%
Left the gate on time

B6984 arrived on time 85.6% of the time, against 79.0% for all RDUBOS flights — this specific departure is 6.6 percentage points better than the route as a whole. Against JetBlue’s own flights on this route it is 9.8 points better.

Source: US DOT Bureau of Transportation Statistics · 391 operations between 2023-07-02 to 2026-05-18

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B698485.6%2.30%-14 min2.6%391
JetBlue on RDUBOS75.8%2.10%-10 min10.7%3,767
All RDUBOS flights79.0%1.78%-12 min9.7%8,787

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

Other routes B6984 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
PHXBOS Phoenix to Boston2024-06-132024-09-0383

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

Data and methodology

Calculated by FlyerIntel from 391 records of B6984 operating RDUBOS, 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