A September 6, 2026 crash involving 21 Air Flight 7598, a Boeing 767-300 operating an Amazon Prime Air cargo flight, overran a runway at Miami International Airport around 2 p.m. local time after arriving from Luis Muñoz Marín International Airport in San Juan, Puerto Rico. Miami-Dade Aviation said the jet became disabled at the northwest end of the airport, while the FAA said it will investigate and Amazon spokesperson Kelly Nantel said the company’s “absolute priority is the safety, well-being, and care of everyone involved.”
- FAA said, “21 Air Flight 7598 overran the runway after landing at Miami International Airport around 2 p.m. local time on Sunday, Sept. 6. The Boeing 767-300 cargo aircraft departed from Luis Muñoz Marín International Airport in San Juan, Puerto Rico. The FAA will investigate.”
- Miami-Dade Aviation confirmed the aircraft was a Prime Air plane that overran the airport’s diagonal runway and became disabled at the northwest end of the airport.
- Miami-Dade Fire Rescue said the aircraft hit several vehicles near the 2100 block of Northwest 42nd Avenue, with more than 60 units responding and multiple patients involved.
- Kelly Nantel said, “This is a fast-moving situation and we’re still gathering details. We’re working closely with local authorities and officials to understand exactly what happened. Right now, our absolute priority is the safety, well-being, and care of everyone involved.”
- An Amazon Prime Air Boeing 767 overran Runway 30 at Miami International Airport and stopped in a nearby field.
- The airport halted all departures at 2:30 p.m. Sunday while emergency crews responded to the disabled cargo jet.
- FAA and NTSB investigators will examine the runway excursion; injuries and the cause remain unconfirmed.
An Amazon Prime Air Boeing 767 overran Runway 30 at Miami International Airport on Sunday and stopped in a nearby field, the Federal Aviation Administration said.
The cargo jet went beyond the runway’s departure point before coming to rest outside the paved airport surface. No official injury information had been released while emergency crews handled the disabled aircraft.
Video footage shows the aircraft crossing a perimeter road and NW 67th Ave after leaving the runway. It then stopped in the field beyond the runway area.
The airport halted all departures at 2:30 p.m. Sunday. Emergency personnel responded as officials managed the aircraft and airport operations.
The incident disrupted departures. The duration of the restriction was not provided.
Federal agencies are preparing to examine the runway excursion
The Federal Aviation Administration identified the incident, while the National Transportation Safety Board prepared to investigate. The agencies’ work will follow the initial response to the aircraft outside the runway boundary.
The FAA and NTSB had not released findings on the sequence of events. Officials also had not confirmed whether anyone was injured.
A runway overrun describes an aircraft continuing beyond the end of the paved runway because it cannot stop within the available surface. Such an event can trigger an emergency response, especially when the aircraft crosses roads or reaches land outside the runway area.
The aircraft’s path created a response area beyond the runway itself. Crews had to address a disabled cargo plane that had crossed both a perimeter road and NW 67th Ave.
| Incident detail | Current status |
|---|---|
| Aircraft | Boeing 767 cargo jet |
| Operator | Amazon Prime Air |
| Runway | Runway 30 |
| Final location | Nearby field beyond the runway area |
| Departure restriction | Ground stop for all departures |
| Restriction start | 2:30 p.m. Sunday |
The table separates the aircraft and airport details from questions that require an investigation. Those questions include the plane’s registration, its operating condition and the events that led to the overrun.
The aircraft identity and cause remain unresolved
Officials had not released the aircraft registration number. They also had not identified the exact cause of the runway excursion.
The material available about the aircraft does not establish whether it was carrying cargo or operating empty. The aircraft itself was identified as a cargo jet, but its load and operating condition remained separate questions.
Injuries also remained unconfirmed. That status does not establish that anyone was hurt or that everyone aboard was safe; it reflects the absence of an official confirmation in the incident information.
The airport is one of the busiest cargo gateways in the United States. A disabled cargo aircraft can therefore affect movement around the airport even when the immediate incident involves a single runway.
The ground stop applied to departures while emergency personnel responded. The information released did not establish whether arrivals were affected, whether the runway sustained damage or how long the airport restriction continued.
Official findings will fill in the missing sequence
The federal investigation is expected to address the aircraft’s registration, the exact cause and the injury status. It will also help establish how the jet traveled beyond Runway 30 and crossed the roads before stopping in the field.
Those details were not available as officials continued managing the emergency response and airport operations. The aircraft’s final position was known, but the events leading to it remained under examination.
The airport’s immediate action came at 2:30 p.m., when it stopped all departures. Further updates from the FAA and NTSB will determine what happened before the aircraft left the paved runway.
