Flight profile · Frontier Airlines
F92633
Baltimore (BWI) to Atlanta (ATL) · scheduled 6:00 AM – 9:00 AM
How F92633 performs
717 operations, November 2023 – July 2026.
F92633 arrived on time 69.5% of the time, against 78.7% for all BWI → ATL flights, so this departure is 9.2 percentage points worse than the route as a whole. Against Frontier Airlines’ own flights on this route it is 3.3 points better.
Source: US DOT Bureau of Transportation Statistics · 717 operations, November 2023 – July 2026 · If F92633 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where F92633 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 F92633 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 |
|---|---|---|---|---|---|
| F92633 | 69.5% | 2.65% | 0 min | 10.5% | 717 |
| Frontier Airlines on BWI → ATL | 66.2% | 3.24% | 0 min | 13.0% | 2,314 |
| All BWI → ATL flights | 78.7% | 1.53% | -5 min | 7.5% | 18,065 |
F92633 has cancelled 2.65% of its scheduled departures (19 of 717), against 1.53% for all BWI → ATL flights — this specific departure cancels 1.1 percentage points more often than the route as a whole. Different flight numbers on the same route can carry different aircraft, crews and schedules, so this is a fact about F92633 specifically, not about the route it flies.
Source: FlyerIntel analysis of US DOT BTS data · November 2023 – July 2026
Why F92633 runs late
Where US DOT attributed the delay minutes on this flight.
airspace and airport capacity, including weather-driven flow control
crew, maintenance, boarding and fueling, all within the carrier’s control
the inbound aircraft was late, so this flight started late
weather severe enough to stop this flight specifically
Share of the delay minutes US DOT attributed to each cause for F92633 on BWI → ATL. 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 F92633 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, F92633 pushed back an average of 19 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 BWI just before it, using the tail number in the DOT file, 662 of 699 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 |
|---|---|---|---|
| F92633 | 41% | 31% | 11% |
| 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 F92633’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often F92633 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 BWI late, does that still matter by the time it reaches ATL?
F92633 pushes back an average of 9.7 minutes late and arrives a further 2.5 minutes behind that. This departure loses ground between the two gates rather than recovering it, so a late pushback here tends to get worse on the way, not better. It spends 18.4 minutes on the taxiways at BWI, 2.5 minutes longer than a typical BWI departure in the same hour.
On arrival at ATL, F92633 spends 29.2 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 19.6 minutes longer than a typical ATL arrival (9.6 min).
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 ATL. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 28,419 departures from BWI scheduled in the clock hour F92633 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at ATL (1,012,161 flights), not just F92633’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · November 2023 – July 2026
The hour it leaves BWI
Part of any flight’s record belongs to the clock rather than to the flight. F92633 has one departure time, so this is what that time is worth.
On-time arrival rate. 28,419 departures from BWI are scheduled in the 6 AM–7 AM hour over the period, against 299,178 across the whole day.
F92633 is scheduled out of BWI at 6:00 AM, in the 6 AM–7 AM bank. Departures from BWI in that hour arrive on time 90.2% of the time against 76.0% across the airport’s whole day — the slot alone is worth 14.3 points better before anything about this particular flight is considered.
The two airport figures cover every departure from BWI 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.
61 min late
against a median of 0 min early
F92633 has an average that understates its risk: a typical arrival is 0 min early, but the worst tenth are 61 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 717 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 |
|---|---|---|---|---|
| DL2950 | Delta Air Lines | 90.1% | 9 min early | 1,095 |
| DL1592 | Delta Air Lines | 89.7% | 9 min early | 868 |
| DL2579 | Delta Air Lines | 89.4% | 7 min early | 810 |
| DL2562 | Delta Air Lines | 88.4% | 10 min early | 845 |
| DL801 | Delta Air Lines | 86.5% | 8 min early | 734 |
| DL2711 | Delta Air Lines | 80.7% | 8 min early | 973 |
| DL2799 | Delta Air Lines | 80.4% | 9 min early | 1,048 |
| F91079 | Frontier Airlines | 73.8% | 6 min early | 660 |
| F92633 this flight | Frontier Airlines | 69.5% | 0 min early | 717 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. F92633 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 717 records of F92633 operating BWI → ATL, 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