Cargo Jet Flown by 21 Air for Amazon Overruns Miami Runway, Killing Five; NTSB Opens Investigation
A Boeing 767-300 freighter arriving from San Juan left the end of Runway 30 at Miami International Airport on September 6 and struck vehicles on an adjacent road; five people died, five were hurt, and a federal go-team is on site[1][4][7].
A Cargo Jet Went Off the End of the Runway
A Boeing 767-300 freighter came in from San Juan, Puerto Rico, and landed at Miami International Airport shortly before 2 p.m. on Sunday, September 6, 2026[1][7]. It was flying as 21 Air Flight 7598[7]. Instead of stopping on the runway, it kept going.
The jet ran off the end of Runway 30, crossed onto ground outside the airport, and struck several vehicles[1][6]. It caught fire[2]. Five people were killed. Five more were hurt, three of them critically, according to Miami-Dade officials[1][4].
Miami-Dade Fire Rescue sent more than 60 units and roughly 200 personnel to the scene[1]. The airport shut down every runway. One reopened around 4:15 p.m., and a second about half an hour after that[1].
The plane carried Amazon Prime Air markings. Amazon did not own it, fly it, or maintain it. It was operated by 21 Air, a cargo airline based in Greensboro, North Carolina, flying under contract[10][11]. Amazon said in a statement that it was "heartbroken to learn that five people lost their lives in today's incident at Miami International Airport"[4].
What the Recorders Know That No One Has Said Yet
The National Transportation Safety Board sent a go-team to Miami, led by Chair Jennifer Homendy, with a first briefing set for Monday, September 7[7]. The agency's own public language has stayed narrow. It calls this a "runway excursion accident" and names the flight, the route, and the aircraft type. Nothing more[7].
That restraint is deliberate. The NTSB finds probable cause; it does not write aviation rules, and it does not want to be wrong in public. A preliminary report is expected within weeks. A final finding on what caused the crash typically takes a year or more[2].
One number is already circulating that did not come from the NTSB. Flight-tracking data from Flightradar24 show the jet departed San Juan at 15:42 UTC, touched down in Miami at 17:53 UTC, and was moving at about 112 knots — roughly 129 miles per hour — as it left the runway[6][9]. That speed is checkable and real, but it is not a finding. It does not say whether the plane touched down long, whether the runway was wet, whether the brakes or thrust reversers worked, or what the crew did in the final seconds[9].
The aircraft itself was 32 years old. It was delivered as a passenger jet in 1994 and converted to a freighter around 2015[6][3]. That is normal for cargo aviation, which runs heavily on older airframes because they are cheaper to operate than new ones[3][6]. Age alone does not point to a cause.
Whose Name Is on the Plane, and Whose Name Is on the Certificate
The gap between the Amazon logo and the actual operator is not an accident of branding. It reflects how most air cargo works. Amazon Air contracts nearly all of its flying to certified cargo airlines under arrangements the industry calls ACMI or CMI. The contractor supplies the aircraft, the crew, the maintenance, and the insurance, and holds the actual FAA operating certificate[10][11].
That matters here because it determines whose records the NTSB will pull. The pilots on Flight 7598 worked for 21 Air, not Amazon. 21 Air's training records, maintenance program, and dispatch decisions are the ones under scrutiny — not Amazon's[10][11]. 21 Air says it operates as a certified Part 121 all-cargo carrier, the same regulatory category as a scheduled passenger airline, with its own safety management system in place[10].
That split creates two very different kinds of exposure. Amazon's risk is mostly reputational — its brand is on a plane involved in a fatal crash it did not fly[3][5]. 21 Air's risk is regulatory and financial: its FAA certificate faces scrutiny, and a company of its size could face wrongful-death litigation from the families of ground victims that exceeds its scale[11].
An Argument That Predates This Crash, and a Question the Cockpit Debate Skips
Pilot unions and cargo-labor advocates have argued for years that Amazon's contracted carriers grew faster than they could safely staff, and that cargo pilots have historically flown under looser duty and rest rules than passenger pilots[12]. They are not saying that argument caused the Miami crash. They are saying it is the question worth asking, because in their view, when the company that sets the schedule isn't the one holding the certificate, cost pressure flows down without accountability flowing back up[12]. The stakes for them are concrete: a recent labor deal at Amazon partner airline ATI was worth about $114 million over four years for roughly 550 pilots, a sign of what shifts when safety becomes a bargaining issue[12].
Miami-Dade officials and the families of the ground victims are asking a different question entirely: how did a plane that overran a runway reach people in cars at all. Many U.S. airports use a system called EMAS — a bed of crushable concrete blocks laid past the runway's end that collapses under a plane's weight and drags it to a stop, similar to a runaway truck ramp. It's the standard backup where there isn't room for a full paved safety buffer. Early accounts describe victims trapped in vehicles that were struck near the airport[6]. Whether MIA's runway safety area or its EMAS system played any role hasn't been addressed by investigators yet, but it puts the county's own airport design under a level of scrutiny a crew-only accident wouldn't draw[1][6].
A Headline Fight Over Whose Name Goes First
Coverage of the crash split largely over which name led the sentence. CNN's headline read "Amazon cargo aircraft overruns runway in Miami," placing the brand ahead of the certificate holder[2]. NBC News wrote "Amazon-branded cargo plane," a phrasing that signals the ownership gap right in the headline rather than burying it[5]. The Hill went further, pairing "Amazon" and "Boeing" in one headline while leaving out 21 Air entirely — stacking two brand names that neither flew nor built the specific fatal outcome, on a story where no cause is yet known[thehill]. WRAL, reporting from 21 Air's home state, was the outlet that centered the operator instead of the brand[11].
Al Jazeera and India's The Tribune both led international coverage with the aircraft's age, describing a "32-year-old" jet while also stating plainly that the cause is unknown[3][8]. Aviation trade outlet AeroTime put the 112-knot figure in its headline, a number pulled from public flight-tracking data rather than any NTSB finding[9]. None of these framings is false. Each just chooses, before the investigation is finished, which fact does the most work in the reader's mind.
What's Left Once the Wreckage Is Cleared
The sequence of events in Miami is not in dispute. The cause is. The flight data recorder and cockpit voice recorder are in federal hands, and they hold most of the answers nobody has yet — whether it was speed, weather, mechanical failure, or something else[9]. Until the NTSB's preliminary report comes out, likely within weeks, and its final finding, likely within a year or more, every theory in circulation is exactly that: a theory, offered by people with a real stake in which one turns out to be true[2][7].
Summary
A Boeing 767-300 cargo jet ran off the end of a runway at Miami International Airport on Sunday afternoon, September 6, 2026. The plane did not stop on the pavement. It crossed onto ground next to the airport and hit vehicles, then caught fire[1][2]. Five people were killed and five were injured, three of them critically, according to Miami-Dade officials[1][4].
The flight was 21 Air Flight 7598, arriving from San Juan, Puerto Rico[7]. The jet carried Amazon Prime Air markings, but Amazon did not own or fly it. It was operated by 21 Air, a cargo airline based in Greensboro, North Carolina, that flies planes under contract for larger shippers[10][11]. That arrangement — one company's brand on the tail, another company's pilots in the cockpit — is standard in air freight, and it is already shaping how different outlets describe the crash.
The National Transportation Safety Board sent a go-team led by Chair Jennifer Homendy, with a first briefing set for Monday, September 7[7]. The Federal Aviation Administration is also involved[4]. Investigators say they will look at where the jet touched down, its speed, its brakes and thrust reversers, the runway surface, the weather, and what the crew did — using the flight data recorder and cockpit voice recorder[9].
Nothing about the cause is settled. The one hard number circulating is from flight-tracking data, not from the NTSB: the freighter was still moving at about 112 knots — roughly 129 miles per hour — when it left Runway 30[6][9]. The genuine dispute right now is not over what happened but over what the story is about: an aging converted freighter, an outsourced contracting model, airport ground-safety design, or simply an accident whose cause is unknown. Each of those framings is being asserted before the evidence that would settle it exists.
The Event
On Sunday, September 6, 2026, a Boeing 767-300 freighter operating as 21 Air Flight 7598 landed at Miami International Airport shortly before 2 p.m. Eastern time after a flight from Luis Muñoz Marín International Airport in San Juan, Puerto Rico[1][7]. The aircraft overran the end of Runway 30, crossed onto adjacent ground, struck multiple vehicles and caught fire[2][6]. Miami-Dade officials reported five people dead and five injured, three of them critically; Miami-Dade Fire Rescue said more than 60 units and about 200 personnel responded[1][4]. All airport runways were closed; one reopened around 4:15 p.m. and a second about 30 minutes later[1].
Undisputed Facts
- The flight was 21 Air Flight 7598, flying from San Juan, Puerto Rico, to Miami, Florida[7].
- The aircraft was a Boeing 767-300 freighter, registration N1997A, serial number 27310, delivered as a passenger jet in 1994 and converted to cargo use in 2015 — about 32 years old[6][3].
- The jet overran Runway 30, the airport's diagonal runway, and struck vehicles outside the airport perimeter[1][6].
- Five people were killed and five were injured, three of them in critical condition, according to Miami-Dade officials[1][4].
- The NTSB launched a go-team, led by Chair Jennifer Homendy, and scheduled its first media briefing for September 7, 2026[7].
- 21 Air is a U.S. Part 121 all-cargo carrier headquartered in Greensboro, North Carolina, that flies Boeing 767s under contract for other companies[10][11].
- Amazon said it was "heartbroken to learn that five people lost their lives in today's incident at Miami International Airport"[4].
- Flight-tracking data indicate the aircraft departed San Juan at 15:42 UTC and touched down in Miami at 17:53 UTC, and was moving at about 112 knots when it left the runway[6][9].
The Pressure
Strip away the moralizing and blame. What structural realities persist regardless of which narrative wins?
- Brand risk versus certificate risk
- In contract air freight, the company whose name is on the tail is usually not the company the FAA can act against. Amazon's exposure here is reputational; 21 Air's is regulatory and financial. That split shapes every statement each will make[10][11].
- Investigative silence has a purpose
- The NTSB withholds cause findings for months because early theories anchor public understanding and are frequently wrong. That silence creates a vacuum that flight-tracking data, aviation trade press and litigation-side commentators fill within hours[6][7][9].
- Ground victims change the legal shape
- When people not connected to the flight are killed on or near airport land, the questions extend past the cockpit to perimeter design, runway safety areas and county responsibility — a very different liability map than a crew-only accident[1][6].
- Freighters are old by design
- Air cargo runs on converted ex-passenger jets because the economics favor cheap airframes over new ones. A 32-year-old 767 is normal in this business, not an outlier — which is exactly why age alone proves nothing about cause[3][6].
Material realityA Boeing 767-300 freighter left Runway 30 at Miami International Airport at roughly 112 knots — about 129 mph — crossed onto ground beyond the runway end, hit vehicles and burned[1][6][9]. Five people are dead and three more are in critical condition[1][4]. The recorders that will answer most of the open questions exist and are in federal hands; the answers do not exist yet, and by the NTSB's normal timeline a probable-cause finding is roughly a year away[2][9]. Meanwhile the airport reopened runways within hours because MIA is a primary freight gateway to the Caribbean and Latin America, and the freight does not stop[1]. Amazon's air network is built on contracted operators flying converted 767s; nothing about the Miami crash has yet altered that structure.
Narrative as a weaponThree groups are shaping perception faster than the evidence is arriving. Amazon wants readers to understand that it did not own, crew or maintain this aircraft — true, and consistently underplayed in headlines that say "Amazon plane." Pilot unions and cargo-labor advocates want readers to see an outsourcing model under strain, an argument they have made for years and which this crash has not yet confirmed or refuted. Aviation trade outlets and flight-tracking services want to be first with a number, and the 112-knot figure is now traveling as if it were a federal finding when it is a public data reading. The NTSB, which will eventually settle most of this, is the actor deliberately saying the least. For a reader, the honest position today is narrow: the sequence of events is well established, the cause is not, and anyone offering one this week is offering a theory.
How Each Side Sees It
Each major actor’s view — how it frames things, its underlying incentive, and how it’s materially affected. Tap a side to read it.
Frames it asThe agencies' position is that cause claims made in the first 48 hours are usually wrong, and that saying so is not evasion. Their public language is deliberately narrow: the NTSB called this a "runway excursion accident" and named the operator and route, nothing more[7]. A runway overrun has many possible drivers — a long or fast touchdown, wet pavement, a brake or thrust-reverser problem, a weight or configuration error, a late go-around decision. Only the flight data recorder and cockpit voice recorder can separate them[9]. The agencies also draw a hard line between the NTSB, which finds probable cause but writes no rules, and the FAA, which regulates. A preliminary report typically comes within weeks; a probable-cause finding usually takes a year or more[2].
WhyInstitutional credibility rests on being the last word, not the first. An early public theory that later collapses damages every future finding the board issues[7].
Impact on themThe board commits a go-team and its chair to a high-visibility accident, with a public briefing schedule that will be judged against how fast information emerges from other channels such as flight-tracking sites[6][7].
Frames it asTheir strongest point is a factual one that gets lost in headlines: the plane said "Prime Air" but Amazon did not fly it. Amazon Air contracts out nearly all of its flying to certificated cargo airlines under arrangements the industry calls ACMI or CMI — the contractor supplies the aircraft, crew, maintenance and insurance, and holds the FAA operating certificate. That means the pilots answered to 21 Air, and 21 Air's maintenance program, training records and dispatch decisions are the ones the NTSB will pull[10][11]. 21 Air's case is that it is a certificated Part 121 all-cargo carrier with a safety management system in place — the same regulatory tier as a scheduled passenger airline, not a loosely supervised charter[10]. Amazon's position is human first and legal second: it expressed grief for the dead and is cooperating, while the operating responsibility sits with its contractor[4].
WhyAmazon wants the brand separated from the operation without appearing to dodge; 21 Air, a company of modest size, faces potential liability that could exceed its scale, so establishing that it met every federal standard is close to existential[10][11].
Impact on themAmazon loses an aircraft from a network built on 767 freighters and faces reputational exposure every time the plane is described as "an Amazon plane"[3][5]. 21 Air faces FAA scrutiny of its certificate, insurance consequences, and wrongful-death litigation from ground victims' families[11].
Frames it asTheir argument predates this crash and does not depend on it. The Teamsters and pilot groups have argued for years that Amazon's contract carriers took on volume faster than they could staff it, and that fatigue and thin pilot pipelines at outsourced freight operators create risk that passenger aviation would not tolerate[12]. The underlying principle they invoke is that safety follows accountability: when the brand that sets the schedule is not the entity that holds the certificate, cost pressure travels down and responsibility does not travel back up. They also point to a real regulatory asymmetry — cargo pilots have historically operated under different duty and rest rules than passenger pilots, a gap the unions have fought to close[12]. They are not claiming this caused the Miami crash; they are claiming it is the question worth asking.
WhyContract leverage and rulemaking. Every high-profile cargo accident strengthens the case for closing the cargo-passenger rest-rule gap and for direct bargaining with Amazon rather than its contractors[12].
Impact on themConcretely: a labor agreement at Amazon partner ATI in this cycle was valued at about $114 million over four years for roughly 550 pilots — the scale of what is at stake when the safety argument moves the bargaining table[12].
Frames it asThis side asks a question the flight-deck debate skips entirely: why did an overrunning jet reach people in vehicles at all. Modern airports are supposed to have a cleared runway safety area past the pavement, and many U.S. airports use EMAS — a bed of crushable concrete blocks laid past the runway end that collapses under a heavy plane's wheels and drags it to a stop, like a truck runaway ramp. Where terrain leaves no room for a full safety area, EMAS is the standard substitute. The five people killed were not on the airplane by choice or by job at the flight deck; early accounts describe people trapped in struck vehicles[6]. The county's other immediate interest is operational: MIA closed all runways, then reopened two within about two and a half hours, because it is one of the busiest cargo gateways in the hemisphere[1].
WhyThe county must both run the airport and answer for its perimeter design; the families' interest is a full public accounting and, likely, civil recovery[1][6].
Impact on themAirport closure disrupted a hub that moves Caribbean and Latin American freight; a finding about the runway safety area would carry capital costs and potential county liability[1].
Like this article?
The Bias Ledger average rating 3
The same story, as framed by outlets across the spectrum, ordered least to most biased. The bias score (1 = straight, 10 = heavily spun) is an AI assessment of that framing — click an outlet to see its track record. The tell is the word choice or omission that reveals the angle.
| Outlet | Vantage | Bias | How they frame it | The tell |
|---|---|---|---|---|
| NBC News | U.S. center-left | 2 | "Five dead after Amazon-branded cargo plane overruns runway at Miami airport, striking multiple vehicles" | The word "branded" is the most precise choice in the ledger — it signals the ownership gap in the headline itself rather than burying it. |
| The Tribune | Indian, independent | 2 | "US: Amazon cargo aircraft overruns runway in Miami, striking multiple vehicles" | Datelined "US:" and written as a compact wire item. Low framing, but the URL path itself is filed under "21-air" while the headline says Amazon — the operator disappears from the reader-facing text. |
| CNN | U.S. center-left | 3 | "5 dead and 5 injured after Amazon cargo aircraft overruns runway in Miami, striking multiple vehicles" | Leads with the Amazon brand rather than the operator, 21 Air, which held the certificate and supplied the crew. Accurate about the branding, but the headline places a company that did not fly the plane at the center of the sentence. |
| Al Jazeera | Qatari state-funded | 3 | "At least five killed after Amazon cargo plane crash in Miami airport" | Foregrounds the airframe's age — a 32-year-old jet converted from passenger service in 2015 — while stating the cause is unknown. Age is a real fact, but placing it high does argumentative work no investigator has endorsed. |
| WRAL | U.S. local, North Carolina | 3 | "Deadly Amazon cargo plane crash has North Carolina connections" | Localizes through the operator's Greensboro headquarters — the only major framing in this set that centers 21 Air rather than Amazon. The angle is parochial, but it points at the entity that actually holds the certificate. |
| The Hill | U.S. center | 4 | "Investigation launched after Amazon Boeing 767 crashes at MIA" | Stacks two brand names — Amazon and Boeing — neither of which operated the flight, and omits 21 Air. No cause is known, so pairing a manufacturer with a crash in the headline supplies an implication the story does not support. |
| AeroTime | Lithuania-based aviation trade press | 4 | "Miami 767 left runway at 112 knots in fatal overrun" | Puts a precise speed in the headline that comes from public flight-tracking data, not from the NTSB. The number is checkable and useful, but a headline figure carries an authority the source does not yet have. |
References
- Amazon cargo plane crash at Miami airport leaves 5 dead, 5 injured — NewsNation · U.S. center-right cable network owned by Nexstar
- 5 dead and 5 injured after Amazon cargo aircraft overruns runway in Miami, striking multiple vehicles — CNN · U.S. center-left, Warner Bros. Discovery
- At least five killed after Amazon cargo plane crash in Miami airport — Al Jazeera · Qatari state-funded
- 5 dead, 5 injured after Amazon cargo plane overruns runway at Miami International Airport — ABC News · U.S. center-left, Disney-owned network news
- Five dead after Amazon-branded cargo plane overruns runway at Miami airport, striking multiple vehicles — NBC News · U.S. center-left, Comcast-owned network news
- 21 Air 767 overruns runway on landing in Miami — Flightradar24 · Swedish commercial flight-tracking company; sells data access
- NTSB Newsroom statement: go-team launched for runway excursion accident, 21 Air Flight 7598 — National Transportation Safety Board · U.S. federal independent investigative agency; no rulemaking power
- US: Amazon cargo aircraft overruns runway in Miami, striking multiple vehicles — The Tribune · Indian daily, trust-owned, editorially independent
- Miami 767 left runway at 112 knots in fatal overrun — AeroTime · Lithuania-based commercial aviation trade publication
- 21 Air, LLC — company site and fleet — 21 Air · The operator itself; self-描述 promotional material
- Deadly Amazon cargo plane crash has North Carolina connections — WRAL · U.S. local broadcaster, Raleigh; Capitol Broadcasting
- Amazon partner airline ATI, pilots agree on provisional 4-year contract — FreightWaves · U.S. logistics trade press; industry-advertiser funded