Flight profile · JetBlue
B61923
Washington (DCA) to Orlando (MCO) · scheduled 12:00 PM – 2:04 PM
How B61923 performs
804 operations, September 2023 – July 2026.
Source: US DOT Bureau of Transportation Statistics · 804 operations, September 2023 – July 2026 · If B61923 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where B61923 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 B61923 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 |
|---|---|---|---|---|---|
| B61923 | 77.6% | 1.49% | -6 min | 9.5% | 804 |
| 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 · September 2023 – July 2026
Why B61923 runs late
Where US DOT attributed the delay minutes on this flight.
the inbound aircraft was late, so this flight started late
crew, maintenance, boarding and fueling, all within the carrier’s control
airspace and airport capacity, including weather-driven flow control
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for B61923 on DCA → MCO. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering September 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies B61923 comes in late, and what that does to the departure.
The aircraft flying B61923 came in 15 or more minutes late on 13% of the departures where its previous flight is known. There are not enough departures in both groups to say how the flight left after a late one and after an on-time one.
Each departure is matched to the flight the same aircraft flew into DCA just before it, using the tail number in the DOT file, 751 of 792 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 |
|---|---|
| B61923 | 13% |
| Network, same turn | 18% |
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 45 to 59 minutes. How often B61923’s aircraft landed 15 or more minutes late is lower than the network’s. There are not enough departures in both groups to compare how it left.
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 September 2023 – July 2026
From pushback to gate
When it leaves DCA late, does that still matter by the time it reaches MCO?
B61923 pushes back an average of 16.1 minutes late and reaches the gate at MCO an average of 10.7 minutes late. The 5.3 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 18.2 minutes on the taxiways at DCA, 1.0 minutes shorter than a typical DCA departure in the same hour.
On arrival at MCO, B61923 spends 10.9 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 23,457 departures from DCA scheduled in the clock hour B61923 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 B61923’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · September 2023 – July 2026
The hour it leaves DCA
Part of any flight’s record belongs to the clock rather than to the flight. B61923 has one departure time, so this is what that time is worth.
On-time arrival rate. 23,457 departures from DCA are scheduled in the 12 PM–1 PM hour over the period, against 435,076 across the whole day.
B61923 is scheduled out of DCA at 12:00 PM, in the 12 PM–1 PM bank. Departures from DCA in that hour arrive on time 79.3% of the time against 76.5% across the airport’s whole day, so the hour B61923 leaves in is an ordinary one for DCA and explains nothing about its record either way.
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 · September 2023 – July 2026 · Hours below 120 departures are not scored.
Other routes B61923 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.
| Route | Operated | Flights | On time |
|---|---|---|---|
| DCA→FLL Washington to Fort Lauderdale | July 1, 2023 – August 28, 2023 | 55 | — |
Because the same number has served different journeys, the statistics above describe only the route B61923 currently operates. Blending them would produce an average of two different flights.
When it goes wrong
The average describes a usual day. This is the day that ruins a connection.
56 min late
against a median of 6 min early
B61923 has an average that understates its risk: a typical arrival is 6 min early, but the worst tenth are 62 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 804 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering September 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 | JetBlue | 82.0% | 8 min early | 1,070 |
| DL1003 | Delta Air Lines | 81.7% | 8 min early | 755 |
| B61923 this flight | 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. B61923 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 804 records of B61923 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