Flight profile · American Airlines
AA670
Miami (MIA) to Kansas City (MCI) · scheduled 9:25 PM – 11:59 PM
How AA670 performs
608 operations, November 2023 – July 2026.
AA670 arrived on time 64.8% of the time, against 68.4% for all MIA → MCI flights, so this departure is 3.6 percentage points worse than the route as a whole.
Source: US DOT Bureau of Transportation Statistics · 608 operations, November 2023 – July 2026 · If AA670 is cancelled or significantly changed, DOT’s automatic refund rule may entitle you to your money back. The refund checker walks through eligibility.
Where AA670 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 AA670 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 |
|---|---|---|---|---|---|
| AA670 | 64.8% | 1.15% | 2 min | 13.6% | 608 |
| American Airlines on MIA → MCI | 65.2% | 1.72% | 0 min | 13.0% | 1,222 |
| All MIA → MCI flights | 68.4% | 1.49% | -1 min | 10.9% | 1,879 |
Source: FlyerIntel analysis of US DOT BTS data · November 2023 – July 2026
Why AA670 runs late
Where US DOT attributed the delay minutes on this flight.
the inbound aircraft was late, so this flight started late
crew, maintenance, boarding and fueling, all within the carrier’s control
airspace and airport capacity, including weather-driven flow 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 AA670 on MIA → MCI. Only delays of 15 minutes or more are attributed.
Source: US DOT Bureau of Transportation Statistics · Data covering November 2023 – July 2026
Does a late aircraft delay this flight?
How often the plane that flies AA670 comes in late, and what that does to the departure.
The aircraft flying AA670 came in 15 or more minutes late on 25% of the departures where its previous flight is known. There are not enough departures in both groups to say how the flight left after a late one and after an on-time one.
Each departure is matched to the flight the same aircraft flew into MIA just before it, using the tail number in the DOT file, 416 of 601 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 |
|---|---|
| AA670 | 25% |
| Network, same turn | 23% |
The schedule leaves a long gap on the ground, which gives a late aircraft room to catch up before this flight pushes back.
The network row is every flight with a scheduled turn of 90 minutes to 3 hours. How often AA670’s aircraft landed 15 or more minutes late is about the same as the network’s. There are not enough departures in both groups to compare how it left.
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 November 2023 – July 2026
From pushback to gate
When it leaves MIA late, does that still matter by the time it reaches MCI?
AA670 pushes back an average of 21.6 minutes late and reaches the gate at MCI an average of 16.6 minutes late. The 5.0 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. Its 22.7 minutes on the taxiways at MIA is about what any departure from the airport in that hour spends.
On arrival at MCI, AA670 spends 7.8 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 1.7 minutes longer than a typical MCI arrival (6.0 min).
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 MCI. Taxi-out is gate to wheels up and sits inside the scheduled block rather than on top of it; the comparison is 34,965 departures from MIA scheduled in the clock hour AA670 most often leaves in. Taxi-in is landing to gate, compared against every arrival FlyerIntel has on file at MCI (152,684 flights), not just AA670’s own. More on taxi time.
Source: FlyerIntel analysis of US DOT BTS data · November 2023 – July 2026
The hour it leaves MIA
Part of any flight’s record belongs to the clock rather than to the flight. AA670 has one departure time, so this is what that time is worth.
On-time arrival rate. 34,965 departures from MIA are scheduled in the 9 PM–10 PM hour over the period, against 340,469 across the whole day.
AA670 is scheduled out of MIA at 9:25 PM, in the 9 PM–10 PM bank. Departures from MIA in that hour arrive on time 69.1% of the time against 73.2% across the airport’s whole day — the slot alone is worth 4.1 points worse before anything about this particular flight is considered.
The two airport figures cover every departure from MIA 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 · November 2023 – July 2026 · Hours below 120 departures are not scored.
Other routes AA670 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 |
|---|---|---|---|
| RSW→PHX Fort Myers to Phoenix | February 12, 2026 – March 6, 2026 | 17 | — |
| PHX→TPA Phoenix to Tampa | December 18, 2025 – January 4, 2026 | 14 | — |
| PHX→PDX Phoenix to Portland | November 30, 2025 | 1 | — |
| DFW→RNO Dallas–Fort Worth to Reno | June 5, 2024 – November 4, 2024 | 153 | 67.3% |
| GRR→ORD Grand Rapids to Chicago | April 4, 2024 – June 4, 2024 | 59 | — |
| DCA→LAX Washington to Los Angeles | July 1, 2023 – November 4, 2023 | 127 | 79.0% |
Because the same number has served different journeys, the statistics above describe only the route AA670 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.
76 min late
against a median of 2 min late
AA670 has an average that understates its risk: a typical arrival is 2 min late, but the worst tenth are 74 minutes worse than that. If the trip has something unmissable at the end of it, the median is the wrong number to plan against.
Percentiles over 608 operations; cancelled and diverted flights are counted separately.
Source: US DOT Bureau of Transportation Statistics · Data covering November 2023 – July 2026
Data and methodology
Calculated by FlyerIntel from 608 records of AA670 operating MIA → MCI, 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