Flight profile · JetBlue

B6360

Philadelphia (PHL) to Boston (BOS) · scheduled 9:25 AM – 10:42 AM

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

365 operations, 2023-10-29 to 2026-05-20.

On-time arrivals
84.7%
299 of 353 completed
Cancellation rate
3.29%
12 cancelled
Median arrival delay
-13 min
Average -3.7 min
Severe delays
3.7%
Arrived 60+ minutes late
Delay when late
56 min
Average, when 15+ min late
Departure punctuality
87.3%
Left the gate on time

B6360 arrived on time 84.7% of the time, against 76.4% for all PHLBOS flights — this specific departure is 8.3 percentage points better than the route as a whole. Against JetBlue’s own flights on this route it is 7.5 points better.

Source: US DOT Bureau of Transportation Statistics · 365 operations between 2023-10-29 to 2026-05-20

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B636084.7%3.29%-13 min3.7%365
JetBlue on PHLBOS77.2%2.04%-10 min9.7%2,839
All PHLBOS flights76.4%2.12%-8 min10.4%15,050

Source: FlyerIntel analysis of US DOT BTS data · 2023-10-29 to 2026-05-20

Other routes B6360 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
CLEBOS Cleveland to Boston2025-01-082025-02-1236

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

Data and methodology

Calculated by FlyerIntel from 365 records of B6360 operating PHLBOS, 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