Flight profile · Delta Air Lines
DL2089
Minneapolis (MSP) to San Francisco (SFO) · scheduled 9:30 PM – 11:36 PM
How DL2089 performs
414 operations, 2024-06-07 to 2026-06-26.
DL2089 arrived on time 71.1% of the time, against 76.0% for all MSP → SFO flights — this specific departure is 4.8 percentage points worse than the route as a whole. Against Delta Air Lines’s own flights on this route it is 4.9 points worse.
Source: US DOT Bureau of Transportation Statistics · 414 operations between 2024-06-07 to 2026-06-26
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| DL2089 | 71.1% | 0.97% | -2 min | 8.1% | 414 |
| Delta Air Lines on MSP → SFO | 76.0% | 0.61% | -6 min | 6.4% | 4,424 |
| All MSP → SFO flights | 76.0% | 0.67% | -6 min | 7.0% | 5,785 |
Source: FlyerIntel analysis of US DOT BTS data · 2024-06-07 to 2026-06-26
Other routes DL2089 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 |
|---|---|---|---|
| ATL→DAY Atlanta to Dayton | 2026-02-12 – 2026-03-06 | 19 | — |
| DAY→ATL Dayton to Atlanta | 2026-02-12 – 2026-03-06 | 19 | — |
| LAX→MCI Los Angeles to Kansas City | 2024-05-07 – 2024-06-06 | 31 | — |
| SEA→DTW Seattle to Detroit | 2024-04-09 – 2024-05-06 | 28 | — |
| BNA→BOS Nashville to Boston | 2024-01-08 – 2024-04-08 | 75 | — |
| BOS→BNA Boston to Nashville | 2024-01-08 – 2024-04-08 | 75 | — |
| ATL→CAE Atlanta to Columbia | 2023-12-16 – 2024-01-07 | 23 | — |
| CAE→ATL Columbia to Atlanta | 2023-12-16 – 2024-01-07 | 23 | — |
| CLT→MSP Charlotte to Minneapolis | 2023-11-05 – 2023-12-06 | 30 | — |
| ATL→PIT Atlanta to Pittsburgh | 2023-10-09 – 2023-11-04 | 23 | — |
| PIT→ATL Pittsburgh to Atlanta | 2023-10-09 – 2023-11-04 | 23 | — |
| ATL→LEX Atlanta to Lexington | 2023-10-28 – 2023-10-31 | 4 | — |
| BOS→LGA Boston to New York | 2023-09-17 – 2023-10-08 | 18 | — |
| CHS→LGA Charleston to New York | 2023-09-05 – 2023-09-15 | 10 | — |
| LGA→CHS New York to Charleston | 2023-09-05 – 2023-09-15 | 10 | — |
| EWR→MSP Newark to Minneapolis | 2023-07-01 – 2023-09-04 | 66 | — |
Because the same number has served different journeys, the statistics above describe only the route DL2089 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.
54 min late
against a median of 2 min early
Percentiles over 414 operations. Cancelled and diverted flights have no arrival time and are counted separately rather than as very late arrivals.
Why DL2089 runs late
Where US DOT attributed the delay minutes on this flight.
crew, maintenance, boarding, fuelling — 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 DL2089 on MSP → SFO. A single late flight can carry more than one cause, and only delays of fifteen minutes or more are attributed at all.
Other departures on MSP → SFO
Same airports, same journey — and not the same odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| DL2074 | Delta Air Lines | 77.8% | 8 min early | 753 |
| DL756 | Delta Air Lines | 75.4% | 3 min early | 704 |
Every departure listed carries at least 600 operations, so the comparison is between figures that mean something. Schedules change; confirm the departure still operates before booking around this.
Data and methodology
Calculated by FlyerIntel from 414 records of DL2089 operating MSP → SFO, 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 · Report a problem
Analysis last recomputed