Amazon Jet Overrun Sparks Miami Chaos

Runway overruns are one of commercial aviation’s most stubborn accident types; in Miami, that risk profile turned deadly when a Boeing 767 cargo jet operating for Amazon’s air network landed, failed to stop, left the pavement, and struck vehicles beyond the runway, killing five and injuring five more.

At a Glance

FAA and airport officials reported that 21 Air Flight 7598, a Boeing 767-300 cargo aircraft operating for Amazon’s Prime Air network, overran a runway at Miami International Airport after landing around 2 p.m. local time.
Miami-Dade officials confirmed five fatalities and five injuries, amid a large fire-rescue response and heavy smoke at the scene.
The incident forced a ground stop and closure of runways and taxiways before limited operations resumed.
Runway overruns are a well-documented subtype of runway excursions; investigators typically examine touchdown point and speed, braking and reverse-thrust performance, runway conditions, and crew decisions.

What happened on the ground in Miami

The basic sequence is clear from official and corroborated reports. After a scheduled cargo flight from San Juan, Puerto Rico, 21 Air Flight 7598 landed at Miami International Airport and overran the landing runway, coming to rest beyond the airport fence at the northwest side of the field. The aircraft, a Boeing 767-300 freighter, was operating on behalf of Amazon’s Prime Air network; Amazon confirmed an incident involving its contracted operator. The overrun triggered a major response: Miami-Dade Fire Rescue deployed dozens of units to fight a substantial post-landing fire and to triage and transport the injured. Airport operations were halted as runways and taxiways were closed during the emergency. Multiple outlets, aligning on core facts from aviation and local officials, reported the same contours of the event and the subsequent ground stop while federal investigators mobilized to the scene.

County leadership later confirmed the human toll: five people dead and five injured. Officials did not immediately specify whether the deceased were in the aircraft, in vehicles struck off-airport, or both—an understandable gap early in a complex scene that spanned the runway end, the perimeter fence, and an adjacent roadway. Imagery and on-scene reporting described heavy smoke and visible fire as responders worked around damaged vehicles and a disabled widebody freighter. The Federal Aviation Administration (FAA) announced it would investigate the runway overrun and coordinate with the National Transportation Safety Board (NTSB), which leads on-scene accident inquiries for significant U.S. aviation events.

Why runway overruns happen: the mechanics and the margins

An overrun is a type of runway excursion: an aircraft departs the end of the paved surface during takeoff or landing. On landing, four variables dominate stopping performance: touchdown point, groundspeed, lift dump (spoilers), and deceleration systems (wheel brakes, anti-skid, and thrust reversers). If a jet crosses the threshold high or fast, touches down long, or fails to achieve full deceleration due to a system fault or technique error, its landing distance balloons. Add a wet or contaminated runway—water, rubber deposits, reduced friction—or gusty conditions that complicate energy management, and the safety margin can be quickly consumed. Industry studies consistently show runway excursions, including overruns, as among the most common accident categories worldwide; they are usually multi-factor events rather than single-point failures.

Airports and regulators mitigate the hazard with runway safety areas (RSAs) or engineered materials arresting systems (EMAS) beyond runway ends. RSAs provide graded ground to reduce damage if an aircraft departs the pavement; EMAS uses crushable blocks to decelerate an aircraft that overruns. Design standards evolved over decades, with modern guidance calling for a 1,000-foot safety area beyond each runway end where practicable; where constrained by geography or development, EMAS can provide equivalent protection in a shorter footprint. Whether a specific runway end features an RSA, EMAS, or neither shapes the overrun outcome—how far a jet travels, whether it breaches a fence or reaches a road—and is a key part of NTSB analyses in cases like Miami’s.

How investigators will build the causal chain

The FAA and NTSB move methodically. Within hours, investigators secure and download the flight data recorder (FDR) and cockpit voice recorder (CVR). The FDR will reveal touchdown speed, point on the runway, spoiler deployment, brake pressures, anti-skid cycling, reverse-thrust commands, and auto-brake settings; the CVR provides crew callouts, wind and runway condition reports, and any abnormal indications that might have influenced the landing. Parallel workstreams examine the aircraft: brake assemblies, tires, anti-skid valves, spoilers, thrust reversers, and hydraulic systems. Investigators also gather airport data—runway length and slope, friction measurements, NOTAMs, recent rain and braking action reports—and air traffic control recordings for approach speeds and clearances. Security and airfield cameras often capture the touchdown point and rollout path, corroborating FDR data with geometry on the ground. This disciplined reconstruction is why preliminary findings arrive in weeks, while final reports—integrating metallurgical analysis, human factors, and organizational context—can take many months.

Victim identification and injury classification proceed on a separate official track, managed by local authorities and medical examiners. In Miami, the fatality and injury counts were established promptly; attribution—onboard versus on the ground—tends to take longer, especially when vehicle extrications and post-crash fire complicate the scene. For the traveling public, the operational impact is immediate: a ground stop, diversions, and cancellations ripple through the network until the disabled aircraft is removed and safety checks of runway surfaces and lighting systems are completed. That pattern is what unfolded at Miami following the 767’s overrun.

Context: a common accident archetype with uncommon consequences

Runway excursions persist despite decades of procedural refinements because they sit at the intersection of aircraft energy management, environmental variability, and human decision-making. Airlines mitigate with stabilized-approach criteria, go-around discipline when parameters are not met, and landing performance assessments that account for runway condition codes. Manufacturers tune autobrake logic and spoiler deployment to maximize deceleration once wheels spin up. Airports maintain grooving and rubber-removal programs to preserve friction. The data show progress, but not elimination: landing and takeoff excursions remain a significant share of commercial accidents in global safety databases, underscoring why regulators and operators treat them as a top-tier risk area.

Branding can blur roles in public perception. The aircraft in Miami carried Amazon livery, and Amazon confirmed it as part of its Prime Air network, but 21 Air was the certificated operator of the flight under FAA regulations. That distinction matters in regulatory oversight and investigative accountability, even if to an outside observer the most visible fact is a familiar logo. In coverage of Miami’s overrun, the operational basics—flight number, routing, runway overrun, emergency response, casualties, and federal investigation—were consistent across authoritative outlets, giving a reliable factual backbone even as causal analysis awaits the NTSB’s work.

5 Killed in Miami Airport Cargo Plane Crash

Footage shows the moment 21 Air Flight 7598, a Boeing 767 cargo aircraft operating for Amazon Prime Air, overran the runway while landing at Miami International Airport on Sunday.

The aircraft struck multiple vehicles and caught fire.… pic.twitter.com/TvxVEluuJm

— Jordan News (@jordannewsdaily) September 7, 2026

What this means going forward

Three consequences typically follow an event like Miami’s. First, the operator—here, 21 Air—conducts internal safety reviews on approach planning, performance calculations, and maintenance history, often issuing interim bulletins to crews about stabilized approaches in wet conditions, autobrake selections, or reverse-thrust technique pending formal findings. Second, the airport re-examines runway-end protections and perimeter risk: fencing, service-road routing, and whether EMAS or additional safety area enhancements could limit off-airport exposure. Third, the NTSB’s final report, when it arrives, tends to translate into industry-wide guidance or, where warranted, airworthiness or operational directives. Those downstream effects—quiet, technical, and incremental—are how an archetypal hazard like runway overruns is constrained over time, even if it can’t be entirely erased.