Flight profile · Delta Air Lines
DL2268
Minneapolis (MSP) to Fort Myers (RSW) · scheduled 6:55 PM – 11:22 PM
How DL2268 performs
749 operations, June 2024 – July 2026.
DL2268 arrived on time 74.9% of the time, against 80.3% for all MSP → RSW flights, so this departure is 5.4 percentage points worse than the route as a whole. Against Delta Air Lines’ own flights on this route it is 6.1 points worse.
Source: US DOT Bureau of Transportation Statistics · 749 operations, June 2024 – July 2026 · If DL2268 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where DL2268 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 DL2268 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 |
|---|---|---|---|---|---|
| DL2268 | 74.9% | 1.74% | -5 min | 7.6% | 749 |
| Delta Air Lines on MSP → RSW | 81.0% | 1.05% | -8 min | 6.5% | 3,635 |
| All MSP → RSW flights | 80.3% | 1.17% | -8 min | 6.5% | 3,838 |
Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026
Why DL2268 runs late
Where US DOT attributed the delay minutes on this flight.
crew, maintenance, boarding and fueling, all within the carrier’s control
the inbound aircraft was late, so this flight started late
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 DL2268 on MSP → RSW. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies DL2268 comes in late, and what that does to the departure.
When the aircraft came in 15 or more minutes late, DL2268 pushed back an average of 34 minutes late; when it came in on time or early, an average of 5 minutes late.
Each departure is matched to the flight the same aircraft flew into MSP just before it, using the tail number in the DOT file, 675 of 736 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 |
|---|---|---|---|
| DL2268 | 23% | 65% | 15% |
| Network, same turn | 17% | 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 DL2268’s aircraft landed 15 or more minutes late is higher than the network’s and, once the aircraft was late, how often DL2268 left 15 or more minutes late is lower 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 June 2024 – July 2026
From pushback to gate
When it leaves MSP late, does that still matter by the time it reaches RSW?
DL2268 pushes back an average of 17.4 minutes late and reaches the gate at RSW an average of 9.3 minutes late. The 8.1 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 18.2 minutes on the taxiways at MSP is about what any departure from the airport in that hour spends.
On arrival at RSW, DL2268 spends 5.3 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 RSW 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 RSW. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 33,761 departures from MSP scheduled in the clock hour DL2268 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at RSW (107,489 flights), not just DL2268’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026
The hour it leaves MSP
Part of any flight’s record belongs to the clock rather than to the flight. DL2268 has one departure time, so this is what that time is worth.
On-time arrival rate. 33,761 departures from MSP are scheduled in the 6 PM–7 PM hour over the period, against 369,781 across the whole day.
DL2268 is scheduled out of MSP at 6:55 PM, in the 6 PM–7 PM bank. Departures from MSP in that hour arrive on time 75.1% of the time against 81.1% across the airport’s whole day — the slot alone is worth 6.0 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from MSP 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 · June 2024 – July 2026 · Hours below 120 departures are not scored.
Other routes DL2268 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 |
|---|---|---|---|
| DTW→PIT Detroit to Pittsburgh | May 7, 2024 – June 6, 2024 | 31 | — |
| SLC→DEN Salt Lake City to Denver | March 10, 2024 – May 6, 2024 | 50 | — |
| DEN→SLC Denver to Salt Lake City | April 9, 2024 – May 6, 2024 | 24 | — |
| SAN→SEA San Diego to Seattle | January 8, 2024 – March 9, 2024 | 62 | — |
| SEA→SAN Seattle to San Diego | January 8, 2024 – March 9, 2024 | 62 | — |
| SAT→SLC San Antonio to Salt Lake City | December 7, 2023 – January 7, 2024 | 31 | — |
| ATL→DAY Atlanta to Dayton | July 1, 2023 – December 6, 2023 | 156 | 89.1% |
| DAY→ATL Dayton to Atlanta | July 1, 2023 – December 6, 2023 | 156 | 94.9% |
Because the same number has served different journeys, the statistics above describe only the route DL2268 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.
50 min late
against a median of 5 min early
Percentiles over 749 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering June 2024 – July 2026
Data and methodology
Calculated by FlyerIntel from 749 records of DL2268 operating MSP → RSW, 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