Flight profile · Delta Air Lines
DL2263
Tampa (TPA) to Minneapolis (MSP) · scheduled 7:00 AM – 9:30 AM
How DL2263 performs
780 operations, June 2024 – July 2026.
DL2263 arrived on time 89.7% of the time, against 83.1% for all TPA → MSP flights, so this departure is 6.6 percentage points better than the route as a whole. Against Delta Air Lines’ own flights on this route it is 6.5 points better.
Source: US DOT Bureau of Transportation Statistics · 780 operations, June 2024 – July 2026 · If DL2263 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where DL2263 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 DL2263 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 |
|---|---|---|---|---|---|
| DL2263 | 89.7% | 1.28% | -8 min | 3.0% | 780 |
| Delta Air Lines on TPA → MSP | 83.2% | 1.28% | -7 min | 5.9% | 3,670 |
| All TPA → MSP flights | 83.1% | 1.30% | -7 min | 5.9% | 3,697 |
Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026
Why DL2263 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 DL2263 on TPA → MSP. 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 DL2263 comes in late, and what that does to the departure.
DL2263 is usually the aircraft’s first flight of the day: the schedule gives it a median of 8.4 hours on the ground at TPA, so its “inbound” is mostly the aircraft’s arrival the evening before.
When the aircraft came in 15 or more minutes late, DL2263 pushed back an average of 3 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 TPA just before it, using the tail number in the DOT file, 726 of 770 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 |
|---|---|---|---|
| DL2263 | 27% | 10% | 7% |
| 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 DL2263’s aircraft landed 15 or more minutes late is about the same as the network’s and, once the aircraft was late, how often DL2263 left 15 or more minutes late is about the same as 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 TPA late, does that still matter by the time it reaches MSP?
DL2263 pushes back an average of 2.5 minutes late and reaches the gate at MSP an average of 2.1 minutes early. The 4.6 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 15.2 minutes on the taxiways at TPA, 1.0 minutes shorter than a typical TPA departure in the same hour.
On arrival at MSP, DL2263 spends 7.1 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 MSP 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 MSP. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 26,402 departures from TPA scheduled in the clock hour DL2263 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at MSP (369,815 flights), not just DL2263’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · June 2024 – July 2026
The hour it leaves TPA
Part of any flight’s record belongs to the clock rather than to the flight. DL2263 has one departure time, so this is what that time is worth.
On-time arrival rate. 26,402 departures from TPA are scheduled in the 7 AM–8 AM hour over the period, against 242,628 across the whole day.
DL2263 is scheduled out of TPA at 7:00 AM, in the 7 AM–8 AM bank. Departures from TPA in that hour arrive on time 89.6% of the time against 78.2% across the airport’s whole day — the slot alone is worth 11.4 points better before anything about this particular flight is considered.
The two airport figures cover every departure from TPA 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 DL2263 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 |
|---|---|---|---|
| ONT→ATL Ontario to Atlanta | May 7, 2024 – June 6, 2024 | 31 | — |
| ATL→BTR Atlanta to Baton Rouge | March 10, 2024 – May 6, 2024 | 58 | — |
| BTR→ATL Baton Rouge to Atlanta | March 10, 2024 – May 6, 2024 | 58 | — |
| SEA→PSP Seattle to Palm Springs | January 8, 2024 – March 9, 2024 | 62 | — |
| PSP→SEA Palm Springs to Seattle | January 8, 2024 – March 8, 2024 | 31 | — |
| BOI→SLC Boise to Salt Lake City | July 1, 2023 – December 30, 2023 | 124 | 89.4% |
| SLC→BOI Salt Lake City to Boise | July 1, 2023 – December 30, 2023 | 124 | 90.2% |
Because the same number has served different journeys, the statistics above describe only the route DL2263 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.
15 min late
against a median of 8 min early
Percentiles over 780 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 780 records of DL2263 operating TPA → MSP, 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