Flight profile · JetBlue
B62423
Washington (DCA) to Orlando (MCO) · scheduled 7:00 AM – 9:22 AM
How B62423 performs
1,070 operations, July 2023 – July 2026.
B62423 arrived on time 82.0% of the time, against 77.1% for all DCA → MCO flights, so this departure is 4.9 percentage points better than the route as a whole. Against JetBlue’s own flights on this route it is 6.9 points better.
Source: US DOT Bureau of Transportation Statistics · 1,070 operations, July 2023 – July 2026 · If B62423 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where B62423 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 B62423 right now, if receivers on the ground are hearing it. Nothing is requested until you press the button.
Against the rest of the route
| Flight or route | On time | Cancelled | Median delay | Severe | Flights |
|---|---|---|---|---|---|
| B62423 | 82.0% | 2.24% | -8 min | 7.7% | 1,070 |
| JetBlue on DCA → MCO | 75.1% | 2.03% | -7 min | 12.4% | 3,593 |
| All DCA → MCO flights | 77.1% | 1.97% | -7 min | 10.0% | 14,633 |
Source: FlyerIntel analysis of US DOT BTS data · July 2023 – July 2026
Why B62423 runs late
Where US DOT attributed the delay minutes on this flight.
crew, maintenance, boarding and fueling, all within the carrier’s control
airspace and airport capacity, including weather-driven flow control
the inbound aircraft was late, so this flight started late
weather severe enough to stop this flight specifically
screening or terminal security incidents
Share of the delay minutes US DOT attributed to each cause for B62423 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 B62423 comes in late, and what that does to the departure.
B62423 is usually the aircraft’s first flight of the day: the schedule gives it a median of 9.5 hours on the ground at DCA, so its “inbound” is mostly the aircraft’s arrival the evening before.
When the aircraft came in 15 or more minutes late, B62423 pushed back an average of 16 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, 933 of 1,048 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
| Share of departures | Inbound landed 15+ late | Left 15+ late after a late inbound | Left 15+ late after an on-time inbound |
|---|---|---|---|
| B62423 | 30% | 22% | 8% |
| Network, same turn | 29% | 12% | 9% |
A night on the ground absorbs most of a late arrival, so a late inbound matters far less on a turn this long than on a same-day one.
The network row is every flight with a scheduled turn of 6 hours or more, usually overnight. How often B62423’s aircraft landed 15 or more minutes late is about the same as the network’s and, once the aircraft was late, how often B62423 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?
B62423 pushes back an average of 10.8 minutes late and reaches the gate at MCO an average of 5.3 minutes late. The 5.5 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. Its 20.0 minutes on the taxiways at DCA is about what any departure from the airport in that hour spends.
On arrival at MCO, B62423 spends 11.0 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,395 departures from DCA scheduled in the clock hour B62423 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 B62423’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. B62423 has one departure time, so this is what that time is worth.
On-time arrival rate. 22,395 departures from DCA are scheduled in the 7 AM–8 AM hour over the period, against 435,076 across the whole day.
B62423 is scheduled out of DCA at 7:00 AM, in the 7 AM–8 AM bank. Departures from DCA in that hour arrive on time 88.4% of the time against 76.5% across the airport’s whole day — the slot alone is worth 11.9 points better 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 B62423 run worse on particular days?
Wednesday is historically the most reliable day and Sunday the least, a gap of 7.1 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.
39 min late
against a median of 8 min early
Percentiles over 1,070 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.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| AA592 | American Airlines | 91.3% | 14 min early | 624 |
| B62423 this flight | JetBlue | 82.0% | 8 min early | 1,070 |
| DL1003 | Delta Air Lines | 81.7% | 8 min early | 755 |
| B61923 | JetBlue | 77.6% | 6 min early | 804 |
| B62523 | JetBlue | 63.5% | 2 min late | 930 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. B62423 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 1,070 records of B62423 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