Flight profile · Delta Air Lines
DL2186
Seattle (SEA) to Fairbanks (FAI) · scheduled 9:30 PM – 12:50 AM
How DL2186 performs
750 operations, 2024-06-07 to 2026-06-30.
DL2186 arrived on time 81.0% of the time, against 76.9% for all SEA → FAI flights — this specific departure is 4.1 percentage points better than the route as a whole.
Source: US DOT Bureau of Transportation Statistics · 750 operations between 2024-06-07 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| DL2186 | 81.0% | 1.87% | -7 min | 5.3% | 750 |
| Delta Air Lines on SEA → FAI | 81.4% | 1.13% | -7 min | 5.8% | 1,505 |
| All SEA → FAI flights | 76.9% | 0.76% | -3 min | 4.0% | 6,983 |
Source: FlyerIntel analysis of US DOT BTS data · 2024-06-07 to 2026-06-30
Other routes DL2186 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 |
|---|---|---|---|
| RIC→ATL Richmond to Atlanta | 2023-07-01 – 2024-06-06 | 214 | 86.3% |
| EWR→MSP Newark to Minneapolis | 2024-04-09 – 2024-05-06 | 24 | — |
| MSP→EWR Minneapolis to Newark | 2024-04-09 – 2024-05-06 | 24 | — |
| RIC→DTW Richmond to Detroit | 2024-03-11 – 2024-04-08 | 25 | — |
| OMA→MSP Omaha to Minneapolis | 2024-03-31 – 2024-03-31 | 1 | — |
| ONT→SEA Ontario to Seattle | 2024-01-08 – 2024-03-09 | 62 | — |
| ATL→RIC Atlanta to Richmond | 2023-12-16 – 2024-01-07 | 23 | — |
Because the same number has served different journeys, the statistics above describe only the route DL2186 currently operates. Blending them would produce an average of two different flights.
Data and methodology
Calculated by FlyerIntel from 750 records of DL2186 operating SEA → FAI, 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.