Flight profile · JetBlue

B61238

Austin (AUS) to Boston (BOS) · scheduled 10:35 AM – 3:35 PM

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

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

On-time arrivals
67.0%
284 of 424 completed
Cancellation rate
1.39%
6 cancelled
Median arrival delay
1 min
Average 24.4 min
Severe delays
13.2%
Arrived 60+ minutes late
Delay when late
90 min
Average, when 15+ min late
Departure punctuality
66.4%
Left the gate on time

B61238 arrived on time 67.0% of the time, against 71.4% for all AUSBOS flights — this specific departure is 4.4 percentage points worse than the route as a whole. Against JetBlue’s own flights on this route it is 3.7 points better.

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

Against the rest of the route

On timeCancelledMedian delaySevereFlights
B6123867.0%1.39%1 min13.2%433
JetBlue on AUSBOS63.3%1.42%3 min16.5%1,126
All AUSBOS flights71.4%1.53%-4 min12.6%4,776

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

Other routes B61238 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
BQNJFK Aguadilla to New York2024-05-012024-06-1231

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

Data and methodology

Calculated by FlyerIntel from 433 records of B61238 operating AUSBOS, 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