Flight profile · JetBlue
B62080
Fort Lauderdale (FLL) to Washington (DCA) · scheduled 8:00 PM – 10:59 PM
How B62080 performs
777 operations, November 2023 – July 2026.
B62080 arrived on time 58.3% of the time, against 71.4% for all FLL → DCA flights, so this departure is 13.1 percentage points worse than the route as a whole. Against JetBlue’s own flights on this route it is 13.6 points worse.
Source: US DOT Bureau of Transportation Statistics · 777 operations, November 2023 – July 2026 · If B62080 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 B62080 compares to other flight numbers, not just to itself.
This flight runs unusually far behind the carrier's own average on this route, worse than 94% of 11,589 comparable flight numbers.
58.3% on time for this specific departure, against 71.9% for the same carrier's other flights on this route.
Source: FlyerIntel analysis of US DOT BTS data · November 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 B62080 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 B62080 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 |
|---|---|---|---|---|---|
| B62080 | 58.3% | 2.06% | 5 min | 16.2% | 777 |
| JetBlue on FLL → DCA | 71.9% | 1.90% | -5 min | 11.2% | 4,589 |
| All FLL → DCA flights | 71.4% | 1.68% | -4 min | 11.3% | 7,312 |
Source: FlyerIntel analysis of US DOT BTS data · November 2023 – July 2026
Why B62080 runs late
Where US DOT attributed the delay minutes on this flight.
the inbound aircraft was late, so this flight started late
airspace and airport capacity, including weather-driven flow control
crew, maintenance, boarding and fueling, all within the carrier’s control
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 B62080 on FLL → DCA. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering November 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies B62080 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, B62080 pushed back an average of 56 minutes late; when it came in on time or early, an average of 14 minutes late.
Each departure is matched to the flight the same aircraft flew into FLL just before it, using the tail number in the DOT file, 575 of 763 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 |
|---|---|---|---|
| B62080 | 27% | 71% | 29% |
| Network, same turn | 33% | 24% | 11% |
The schedule leaves a long gap on the ground, which gives a late aircraft room to catch up before this flight pushes back.
The network row is every flight with a scheduled turn of 3 to 6 hours. How often B62080’s aircraft landed 15 or more minutes late is lower than the network’s and, once the aircraft was late, how often B62080 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 November 2023 – July 2026
From pushback to gate
When it leaves FLL late, does that still matter by the time it reaches DCA?
B62080 pushes back an average of 27.5 minutes late and reaches the gate at DCA an average of 24.8 minutes late. The 2.7 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.2 minutes on the taxiways at FLL, 1.9 minutes longer than a typical FLL departure in the same hour.
On arrival at DCA, B62080 spends 8.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 DCA 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 DCA. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 23,630 departures from FLL scheduled in the clock hour B62080 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at DCA (435,126 flights), not just B62080’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · November 2023 – July 2026
The hour it leaves FLL
Part of any flight’s record belongs to the clock rather than to the flight. B62080 has one departure time, so this is what that time is worth.
On-time arrival rate. 23,630 departures from FLL are scheduled in the 8 PM–9 PM hour over the period, against 278,691 across the whole day.
B62080 is scheduled out of FLL at 8:00 PM, in the 8 PM–9 PM bank. Departures from FLL in that hour arrive on time 62.6% of the time against 72.6% across the airport’s whole day — the slot alone is worth 10.0 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from FLL 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 · November 2023 – July 2026 · Hours below 120 departures are not scored.
When it goes wrong
The average describes a usual day. This is the day that ruins a connection.
92 min late
against a median of 5 min late
B62080 has an average that understates its risk: a typical arrival is 5 min late, but the worst tenth are 87 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 777 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering November 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 |
|---|---|---|---|---|
| B61480 | JetBlue | 90.5% | 12 min early | 1,011 |
| B61680 | JetBlue | 69.4% | 2 min early | 883 |
| B61880 | JetBlue | 60.4% | 4 min late | 1,059 |
| B62080 this flight | JetBlue | 58.3% | 5 min late | 777 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. B62080 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 777 records of B62080 operating FLL → DCA, 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