An Amazon Cargo Jet Overshot the Runway in Miami. It Didn't Stop at the Fence

It was a little before 2 p.m. on a quiet Sunday when the call came in: an aircraft down, off the runway, at the northwest edge of Miami International Airport. Within minutes, Miami-Dade County's dispatch logs show the first units already rolling. By the time firefighters reached the scene, they weren't just looking at a disabled airplane — they were looking at a Boeing 767 freighter sitting beside a public road, on fire, having already run through at least two vehicles in its path. More than 60 Miami-Dade Fire Rescue units eventually responded, one of the largest single-incident deployments the department has logged all year, to what had, moments earlier, been an unremarkable cargo landing.

A flight that never should have made news

The aircraft was 21 Air Flight 7598, a Boeing 767-300 operating under contract for Amazon's Prime Air cargo network, flying the kind of route that generates zero headlines on a normal day: freight up from Luis Muñoz Marín International Airport in San Juan, Puerto Rico, into Miami. Around 2 p.m. local time, the jet touched down on MIA's diagonal runway and, according to the Federal Aviation Administration, simply kept going — overrunning the pavement and coming to rest disabled near the airport's northwest boundary. Miami-Dade Fire Rescue said the plane struck multiple vehicles, including two semi-trucks, near the 2100 block of Northwest 42nd Avenue, just outside the airport's perimeter. Video circulating within the hour showed the aircraft's tail hanging over the boundary fence, black smoke pouring skyward as crews moved in with hoses.

Five people, two hospitals, and a lot of unanswered questions

Miami-Dade Fire Rescue's early statement was blunt: crews arrived to find heavy flames and smoke, and said "there are multiple patients" without immediately detailing their conditions. Later reporting citing a source familiar with the response narrowed that down: two pilots were taken to Jackson South Medical Center, and three additional people — reportedly caught up in the vehicles the plane struck — were taken to Jackson Memorial Hospital. As of Sunday evening, no fatalities had been confirmed by any official source, a detail that, given the size of the aircraft and the fact that it ended up on a public roadway, is closer to lucky than routine. Amazon's response was fast but guarded. Spokesperson Kelly Nantel confirmed the incident and said the company's priority was "the safety, well-being, and care of everyone involved," while cautioning that Amazon itself was "still gathering details" on what actually happened.

An airport built for 50 million passengers, stopped cold

The operational fallout was immediate and, for a few hours, total. Miami-Dade Aviation Department officials closed every runway and taxiway at MIA as of 3 p.m., and the FAA layered a ground stop on top of that — first through 3 p.m., then extended to 4:30, then again to 5:30 as crews worked the wreckage and cleared debris. One of the airport's four runways reopened by around 4:15 p.m., letting a trickle of traffic resume even as the crash site remained an active scene. By late afternoon, FlightAware was tracking roughly 250 delayed flights tied directly to the closure, with the FAA warning travelers that arrivals and departures would keep moving at a reduced pace well after the ground stop lifted. Even getting to the terminal became a small ordeal: MIA advised that Metrorail riders would need to transfer at the Earlington Heights station to reach the airport on the Orange Line for the rest of the day.

This isn't Amazon's first brush with a 767 disaster

For anyone who has followed Amazon's cargo operation, Sunday's images landed with an unpleasant echo. In February 2019, a Boeing 767 flying for Amazon under contract with Atlas Air went down in Trinity Bay outside Houston, killing all three people aboard. The NTSB later traced that crash to the first officer's mishandling of an inadvertent go-around activation, which sent the aircraft into a rapid, disorienting dive. Sunday's incident is a different animal entirely — a runway excursion after what appears to have been an otherwise normal landing, not a loss of control in flight — and investigators have been careful to say the cause here "has not been established." But it's the second time in seven years that the words "Amazon," "767" and "crash" have appeared in the same headline, and that pattern alone is going to get scrutiny the moment the NTSB opens its docket.

What happens now

The National Transportation Safety Board said it is leading the investigation and will send a team to Miami; the FAA is running a parallel inquiry into the circumstances that put the aircraft off the runway in the first place. Both will want the flight data and cockpit voice recorders, weather and wind data for the airport at the moment of landing, and 21 Air's maintenance and training records for the aircraft and crew. None of that moves fast — full NTSB reports on runway excursions typically take a year or more — but the early, more urgent questions belong to Miami-Dade Fire Rescue and Jackson Health System: how badly hurt are the five people who were hospitalized, and were there others on that stretch of Northwest 42nd Avenue who simply weren't home when a cargo jet came through the fence.

Additional reporting drawn from NPR, Fox News, NBC 6 South Florida, and Local 10 News.