Flight profile · Delta Air Lines
DL478
Atlanta (ATL) to Portland (PDX) · scheduled 7:45 PM – 10:08 PM
How DL478 performs
384 operations, 2024-06-07 to 2026-06-06.
DL478 arrived on time 72.7% of the time, against 80.2% for all ATL → PDX flights — this specific departure is 7.5 percentage points worse than the route as a whole. Against Delta Air Lines’s own flights on this route it is 8.4 points worse.
Source: US DOT Bureau of Transportation Statistics · 384 operations between 2024-06-07 to 2026-06-06
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| DL478 | 72.7% | 1.30% | 1 min | 7.7% | 384 |
| Delta Air Lines on ATL → PDX | 81.1% | 0.79% | -5 min | 4.8% | 3,803 |
| All ATL → PDX flights | 80.2% | 0.75% | -4 min | 5.3% | 4,291 |
Source: FlyerIntel analysis of US DOT BTS data · 2024-06-07 to 2026-06-06
Other routes DL478 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 |
|---|---|---|---|
| EYW→LGA Key West to New York | 2025-12-20 – 2026-01-04 | 16 | — |
| LGA→EYW New York to Key West | 2025-12-20 – 2026-01-04 | 16 | — |
| BOS→LGA Boston to New York | 2025-04-19 – 2025-08-09 | 6 | — |
| DFW→BOS Dallas–Fort Worth to Boston | 2025-06-14 – 2025-07-05 | 4 | — |
| MSP→MSY Minneapolis to New Orleans | 2025-03-09 – 2025-06-06 | 51 | — |
| MSY→MSP New Orleans to Minneapolis | 2025-03-09 – 2025-06-06 | 51 | — |
| AUS→LAX Austin to Los Angeles | 2025-01-06 – 2025-03-08 | 62 | — |
| LAX→AUS Los Angeles to Austin | 2025-01-06 – 2025-03-08 | 62 | — |
| FAY→ATL Fayetteville to Atlanta | 2024-11-11 – 2024-12-18 | 38 | — |
| DTW→FLL Detroit to Fort Lauderdale | 2024-10-07 – 2024-11-10 | 33 | — |
| FLL→DTW Fort Lauderdale to Detroit | 2024-10-07 – 2024-11-10 | 33 | — |
| FLL→JFK Fort Lauderdale to New York | 2024-09-09 – 2024-10-06 | 28 | — |
| LGA→ATL New York to Atlanta | 2023-07-01 – 2024-06-06 | 300 | 80.3% |
| SFO→DTW San Francisco to Detroit | 2024-04-09 – 2024-05-06 | 28 | — |
| BOS→MSP Boston to Minneapolis | 2024-03-16 – 2024-04-06 | 4 | — |
| SEA→LAS Seattle to Las Vegas | 2024-01-13 – 2024-03-09 | 9 | — |
| LAS→SEA Las Vegas to Seattle | 2024-02-17 – 2024-03-09 | 3 | — |
Because the same number has served different journeys, the statistics above describe only the route DL478 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.
47 min late
against a median of 1 min late
Percentiles over 384 operations. Cancelled and diverted flights have no arrival time and are counted separately rather than as very late arrivals.
Why DL478 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
Share of the delay minutes US DOT attributed to each cause for DL478 on ATL → PDX. 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 ATL → PDX
Same airports, same journey — and not the same odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| DL503 | Delta Air Lines | 77.7% | 3 min early | 963 |
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 384 records of DL478 operating ATL → PDX, 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