Flight profile · American Airlines
AA2920
Chicago (ORD) to Tampa (TPA) · scheduled 8:35 AM – 12:14 PM
How AA2920 performs
953 operations, 2023-07-01 to 2026-06-30.
AA2920 arrived on time 79.1% of the time, against 75.8% for all ORD → TPA flights — this specific departure is 3.3 percentage points better than the route as a whole. Against American Airlines’s own flights on this route it is 6.4 points better.
Source: US DOT Bureau of Transportation Statistics · 953 operations between 2023-07-01 to 2026-06-30
Against the rest of the route
| On time | Cancelled | Median delay | Severe | Flights | |
|---|---|---|---|---|---|
| AA2920 | 79.1% | 1.68% | -7 min | 6.6% | 953 |
| American Airlines on ORD → TPA | 72.7% | 1.67% | -4 min | 10.1% | 3,121 |
| All ORD → TPA flights | 75.8% | 1.55% | -6 min | 8.9% | 9,536 |
Source: FlyerIntel analysis of US DOT BTS data · 2023-07-01 to 2026-06-30
By day of week
Does AA2920 run worse on particular days?
Wednesday is historically the most reliable day and Saturday the least, a gap of 15.4 percentage points.
Source: FlyerIntel analysis of US DOT BTS data · 2023-07-01 to 2026-06-30 · Days with fewer than 120 operations are not scored.
Other routes AA2920 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 |
|---|---|---|---|
| DFW→SNA Dallas–Fort Worth to Santa Ana | 2026-04-07 – 2026-05-20 | 44 | — |
| SNA→DFW Santa Ana to Dallas–Fort Worth | 2026-04-07 – 2026-05-20 | 44 | — |
| CLT→JAX Charlotte to Jacksonville | 2026-03-08 – 2026-04-06 | 30 | — |
| JAX→CLT Jacksonville to Charlotte | 2026-03-08 – 2026-04-06 | 30 | — |
| TPA→ORD Tampa to Chicago | 2023-07-01 – 2026-02-11 | 834 | 75.0% |
| BFL→PHX Bakersfield to Phoenix | 2024-10-27 – 2024-11-03 | 4 | — |
| PHX→BFL Phoenix to Bakersfield | 2024-10-27 – 2024-11-03 | 4 | — |
Because the same number has served different journeys, the statistics above describe only the route AA2920 currently operates. Blending them would produce an average of two different flights.
Why AA2920 runs late
Where US DOT attributed the delay minutes on this flight.
the inbound aircraft was late, so this flight started late
airspace and airport capacity, including weather-driven flow control
crew, maintenance, boarding, fuelling — within the carrier’s control
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 AA2920 on ORD → TPA. 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 ORD → TPA
Same airports, same journey — and not the same odds of arriving on time.
| Flight | Airline | On time | Median arrival | Operations |
|---|---|---|---|---|
| UA2326 | United Airlines | 89.0% | 11 min early | 864 |
| AA1101 | American Airlines | 69.0% | 0 min early | 746 |
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 953 records of AA2920 operating ORD → TPA, 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