Flight profile · JetBlue

B6247

Boston (BOS) to Salt Lake City (SLC) · scheduled 6:05 PM – 9:44 PM

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

398 operations, 2023-09-06 to 2026-06-30.

On-time arrivals
63.1%
248 of 393 completed
Cancellation rate
1.26%
5 cancelled
Median arrival delay
5 min
Average 19.9 min
Severe delays
14.8%
Arrived 60+ minutes late
Delay when late
70 min
Average, when 15+ min late
Departure punctuality
60.9%
Left the gate on time

B6247 arrived on time 63.1% of the time, against 78.7% for all BOSSLC flights — this specific departure is 15.6 percentage points worse than the route as a whole.

Source: US DOT Bureau of Transportation Statistics · 398 operations between 2023-09-06 to 2026-06-30

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B624763.1%1.26%5 min14.8%398
JetBlue on BOSSLC63.2%1.05%3 min14.3%765
All BOSSLC flights78.7%0.78%-7 min7.2%3,867

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

Other routes B6247 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
LGATPA New York to Tampa2023-10-292023-12-2252

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

Data and methodology

Calculated by FlyerIntel from 398 records of B6247 operating BOSSLC, 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