Flight profile · JetBlue

B62523

Washington (DCA) to Orlando (MCO) · scheduled 8:00 PM – 10:24 PM

This page describes how B62523 has historically performed, which is a different and more useful question when you are deciding what to book. The live position below is a reading from receivers on the ground, not flight status. For today’s status, check with JetBlue.

How B62523 performs

930 operations, July 2023 – July 2026.

On-time arrivals
63.5%
573 of 903 completed
Cancellation rate
2.47%
23 cancelled
Median arrival delay
2 min
Average 30.1 min
Severe delays
20.4%
Arrived 60+ minutes late
Delay when late
103 min
Average, when 15+ min late
Departure punctuality
62.0%
Left the gate on time

B62523 arrived on time 63.5% of the time, against 77.1% for all DCA → MCO flights, so this departure is 13.6 percentage points worse than the route as a whole. Against JetBlue’s own flights on this route it is 11.6 points worse.

B62523’s scheduled departure has moved during the period FlyerIntel has on file: it typically left around 8:00 PM earlier on, and around 7:00 PM more recently — a 60-minute shift, not the few minutes of day-to-day rounding every published schedule carries. Confirm the current departure time before booking around an older listing.

Source: US DOT Bureau of Transportation Statistics · 930 operations, July 2023 – July 2026 · If B62523 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.

What stands out

How B62523 compares to other flight numbers, not just to itself.

This flight's worst arrivals run unusually far past its typical one, a bigger gap than 97% of 11,788 comparable flight numbers.

A typical arrival is 2 min late, but the worst tenth run 112 minutes worse than that.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · The one thing about this specific departure that ranks most extreme against every other published flight number, out of everything FlyerIntel checks — shown only when something clears a real statistical bar, not for every flight.

Where B62523 is right now

A live reading, only if you ask for it. It is not part of the reliability record above.

Ask for the position of B62523 right now, if receivers on the ground are hearing it. Nothing is requested until you press the button.

Against the rest of the route

Against the rest of the route
Flight or routeOn timeCancelledMedian delaySevereFlights
B6252363.5%2.47%2 min20.4%930
JetBlue on DCA → MCO75.1%2.03%-7 min12.4%3,593
All DCA → MCO flights77.1%1.97%-7 min10.0%14,633

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026

Why B62523 runs late

Where US DOT attributed the delay minutes on this flight.

Share of the delay minutes US DOT attributed to each cause for B62523 on DCA → MCO. Only delays of 15 minutes or more are attributed.

Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026

Does a late aircraft delay this flight?

How often the plane that flies B62523 comes in late, and what that does to the departure.

Inbound aircraft late
39%
334 of 864 departures came in 15+ minutes late
Scheduled time on the ground
61 minutes
Median at DCA between the inbound and this departure
Left 15+ late after a late inbound
75%
334 departures
Left 15+ late after an on-time inbound
11%
530 departures

When the aircraft came in 15 or more minutes late, B62523 pushed back an average of 64 minutes late; when it came in on time or early, an average of 1 minute late.

Each departure is matched to the flight the same aircraft flew into DCA just before it, using the tail number in the DOT file, 864 of 909 departures in all. A departure is left out when that flight is unknown, was cancelled or diverted, or the aircraft had sat for more than 12 hours. A flight the airline cancelled never left and is not in the count, and one flown by a substitute aircraft is matched to the aircraft that flew it, not to the one first planned.

Against the network at the same turn length

B62523 against all flights with a scheduled turn of 60 to 89 minutes
Share of departuresInbound landed 15+ lateLeft 15+ late after a late inboundLeft 15+ late after an on-time inbound
B6252339%75%11%
Network, same turn17%68%9%

The schedule leaves a normal turn: enough time to clean and board if the aircraft is on time, little to spare if it is not.

The network row is every flight with a scheduled turn of 60 to 89 minutes. How often B62523’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often B62523 left 15 or more minutes late is higher than the network’s.

More: Which Flight Numbers Pay for a Late Aircraft lists the flight numbers that pass a late aircraft on.

Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026

From pushback to gate

When it leaves DCA late, does that still matter by the time it reaches MCO?

Leaves the gate
36.3 minutes late
Average over 909 pushbacks
Taxi out at DCA
19.6 min
22.8 min for the airport in this hour
Taxi in at MCO
11.4 min
10.9 min for a typical MCO arrival
Reaches the gate at MCO
30.1 minutes late
Average over 903 arrivals

B62523 pushes back an average of 36.3 minutes late and reaches the gate at MCO an average of 30.1 minutes late. The 6.2 minutes between those two figures are slack the published schedule already carries, which is why a late pushback on this flight does not reliably become a late arrival. It spends 19.6 minutes on the taxiways at DCA, 3.2 minutes shorter than a typical DCA departure in the same hour.

On arrival at MCO, B62523 spends 11.4 min taxiing from touchdown to the gate — ground time a connecting passenger sits through before they can even leave the aircraft, on top of however late the flight itself ran. That is about what any arrival at MCO spends on the ground before reaching the gate.

Departure delay is averaged over every pushback and arrival delay over every completed arrival, so the two counts differ by the flights that never reached MCO. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 22,666 departures from DCA scheduled in the clock hour B62523 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at MCO (498,229 flights), not just B62523’s own. More on taxi time.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026

The hour it leaves DCA

Part of any flight’s record belongs to the clock rather than to the flight. B62523 has one departure time, so this is what that time is worth.

B6252363.5%
All DCA departures, 8 PM–9 PM69.3%
All DCA departures, whole day76.5%

On-time arrival rate. 22,666 departures from DCA are scheduled in the 8 PM–9 PM hour over the period, against 435,076 across the whole day.

B62523 is scheduled out of DCA at 8:00 PM, in the 8 PM–9 PM bank. Departures from DCA in that hour arrive on time 69.3% of the time against 76.5% across the airport’s whole day — the slot alone is worth 7.3 points worse before anything about this particular flight is considered.

The two airport figures cover every departure from DCA to every destination, so they describe the slot rather than this journey — the like-for-like comparison against the route is above. Hours are scheduled local, and a number whose schedule moved between banks inside the period has no single hour and is not described here at all. Why the hour matters.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · Hours below 120 departures are not scored.

By day of week

Does B62523 run worse on particular days?

Monday65.7%
Tuesday—
Wednesday66.9%
Thursday59.3%
Friday53.3%
Saturday70.3%
Sunday56.8%

Saturday is historically the most reliable day and Friday the least, a gap of 17.0 percentage points.

Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026 · Days with fewer than 120 operations are not scored.

When it goes wrong

The average describes a usual day. This is the day that ruins a connection.

One arrival in ten is worse than

114 min late

against a median of 2 min late

Arrived an hour or more late20.4%
Typical delay when late103 min
Cancelled2.47%
Landed somewhere else0.43%

B62523 has an average that understates its risk: a typical arrival is 2 min late, but the worst tenth are 112 minutes worse than that. If the trip has something unmissable at the end of it, the median is the wrong number to plan against.

Percentiles over 930 operations; cancelled and diverted flights are counted separately.

Source: US DOT Bureau of Transportation Statistics · Data covering July 2023 – July 2026

Other flights on this route

Same airports, same journey, different odds of arriving on time.

Other flights on this route
FlightAirlineOn timeMedian arrivalOperations
AA592American Airlines91.3%14 min early624
B62423JetBlue82.0%8 min early1,070
DL1003Delta Air Lines81.7%8 min early755
B61923JetBlue77.6%6 min early804
B62523 this flightJetBlue63.5%2 min late930

Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. B62523 is placed in the same ordering rather than left out of it; the rows around it are the most punctual departures on the route, not all of them, so this is a comparison and not a rank. Schedules change; confirm the departure still operates before booking around this.

Data and methodology

Calculated by FlyerIntel from 930 records of B62523 operating DCA → MCO, 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 · Data sources · Report a problem

Related research: Most and Least Reliable Flight Numbers · The Delay You Inherit · Making Up Time in the Air

Analysis last recomputed