MIAMI — Newly released preliminary findings from the National Transportation Safety Board (NTSB) have shed light on the final, chaotic moments inside the cockpit of an Amazon Prime Air cargo jet before it overran a runway at Miami International Airport (MIA) on Sunday, September 6, 2026.
The catastrophic accident resulted in the deaths of five airport workers on the ground, critical injuries to several others, and has raised urgent questions regarding cockpit communication, landing procedures, and the safety of cargo flight operations under challenging weather conditions.
According to NTSB investigators, cockpit voice recordings reveal a stark breakdown in communication between the flight crew. For nearly two minutes leading up to and immediately following touchdown, one pilot repeatedly warned that the aircraft was traveling "too fast." However, these warnings were met with silence or inconsistent responses from the flying pilot, culminating in a series of desperate, conflicting maneuvers that ultimately sent the heavy Boeing 767 careening off the runway and into airport support vehicles.
Main Facts of the Incident
The accident involved a Boeing 767 cargo aircraft operating as Amazon Prime Air Flight 21, managed and flown by charter cargo carrier 21 Air under contract for the retail giant. The flight crew consisted of Captain Joseph Carroll, 55, and First Officer Jaime Felipe Silva Molina, 37. Both pilots survived the crash with injuries and have since been interviewed by federal investigators.
The Aircraft and Operators
The aircraft involved was a twin-engine Boeing 767 widebody cargo jet, a workhorse of the global logistics industry. The flight was operated by 21 Air, an ACMI (Aircraft, Crew, Maintenance, and Insurance) provider headquartered in North Carolina that frequently operates domestic and international cargo routes on behalf of major logistics networks, including DHL and Amazon.
The Human Cost on the Ground
While both flight crew members survived, the tragedy unfolded on the airport perimeter. After overrunning the runway, the massive jet struck a transport van occupied by a contracted ground crew.
- Fatalities: Five passengers inside the van, identified as members of an airport contract cleaning crew responsible for preparing aircraft cabins between flights, were killed instantly.
- Injuries: Five additional ground workers were injured in the collision and subsequent debris field. As of Tuesday, September 8, two of those injured remained in critical condition at local trauma centers.
- Flight Crew Status: Both Captain Carroll and First Officer Molina were treated for non-life-threatening injuries and released from the hospital.
Chronology of the Disaster
To understand how a routine cargo arrival transitioned into a fatal runway excursion, investigators reconstructed the flight’s final minutes using data from the Cockpit Voice Recorder (CVR) and the Flight Data Recorder (FDR).
[Approach Phase] ──> [Unstable Descent] ──> [Late Touchdown (5,000ft)] ──> [Aborted Go-Around] ──> [Runway Overrun & Impact]
(Speed Warnings) (Sink Rate Alerts) (Remaining: 4,360ft) (4-Second Window) (1,300ft past runway)1. The Descent and Cockpit Disconnect
As Flight 21 descended toward Miami International Airport on the afternoon of September 6, the crew encountered strong, shifting winds. The NTSB’s initial readout of the CVR indicates that as the aircraft approached the runway, one of the pilots grew increasingly alarmed by the aircraft’s airspeed.
For nearly two minutes, this pilot repeatedly warned the other that the jet’s speed was well above safe landing parameters. Despite the urgency of these alerts, the receiving pilot failed to offer a "consistent verbal response," according to the NTSB. During this time, the aircraft’s automated Ground Proximity Warning System (GPWS) began triggering loud, repetitive auditory alerts, including "sink rate" and "too low terrain," signaling that the aircraft was descending too rapidly and was dangerously close to the ground without being properly configured or stabilized.
2. A Late and Awkward Touchdown
Despite the unstable approach and the lack of a coordinated response in the cockpit, the crew proceeded with the landing. FlightRadar24 tracking data shows that the Boeing 767 crossed the threshold of Runway 30 at a high rate of speed and floated deep down the strip.
The aircraft did not touch down until it was nearly 5,000 feet into the 9,360-foot runway. This late touchdown left the pilots with less than 4,400 feet of remaining runway to bring the heavy widebody aircraft to a complete stop—a distance far below standard safety margins for a Boeing 767 under wet or windy conditions.
3. The Fatal Go-Around Attempt
Immediately after a highly awkward and bounced touchdown, the flight crew attempted to salvage the landing through a series of rapid, conflicting control inputs:
- The Go-Around Decision: Realizing they were running out of pavement, the pilots briefly attempted to abort the landing and go around. They advanced the engine throttles to climb thrust and released the wheel brakes.
- The Aborted Maneuver: Just four seconds after initiating the go-around, the crew abandoned the attempt. Believing they no longer had sufficient runway or engine spool-up time to safely take off, they pulled the throttles back to idle and slammed on the brakes once more.
- The Overrun: This four-second hesitation consumed hundreds of feet of precious runway. With braking effectiveness severely compromised by the high speed and wet runway conditions, the aircraft could not decelerate in time.
The Boeing 767 barreled past the end of Runway 30, traveling approximately 1,300 feet through the runway safety area and over airport service roads before slamming into the cleaning crew’s transport van and coming to rest with its nose on the ground near a parking lot.
Supporting Technical and Flight Data
The NTSB’s preliminary report highlights several critical technical anomalies that contributed to the crash.
| Parameter | Recorded Metric | Standard Safety Target |
|---|---|---|
| Touchdown Point | ~5,000 feet down Runway 30 | Within first 1,000–1,500 feet |
| Remaining Runway | ~4,360 feet | Upwards of 7,500 feet (for B767) |
| Approach Stability | Unstable (multiple GPWS alerts) | Stabilized by 1,000 feet altitude |
| Go-Around Attempt | 4 seconds (initiated then aborted) | Immediate, decisive action |
Unstable Approach Criteria
In commercial aviation, an approach is considered "unstable" if the aircraft does not meet specific speed, descent rate, and configuration parameters by a designated altitude (typically 1,000 feet above the ground in instrument conditions). Standard Operating Procedures (SOPs) for virtually all commercial airlines dictate that if an approach is unstable, the crew must immediately execute a missed approach (go-around). The FDR data confirms that the Amazon cargo jet violated multiple stabilization criteria, yet the crew pressed on with the landing.
The Role of High Winds and Wind Shear
Miami-Dade County was experiencing turbulent weather and strong, gusty winds on the afternoon of the crash. Investigators are analyzing whether wind shear—a sudden change in wind speed and direction—contributed to the high approach speed and the floated touchdown. High tailwinds can significantly increase an aircraft’s groundspeed, making it difficult to slow down and dramatically increasing the landing distance required.
Official Responses and Investigation Status
The tragedy has prompted a massive federal investigation led by the NTSB, alongside representatives from the Federal Aviation Administration (FAA), Boeing, and the pilots’ union.
NTSB Chair Jennifer Homendy’s Statement
During a press briefing, NTSB Chair Jennifer Homendy expressed deep condolences to the families of the ground crew workers.
"This was a horrific tragedy that claimed the lives of five dedicated airport workers who were simply doing their jobs," Homendy said. "Our investigators are looking closely at the cockpit dynamics, the decision-making process regarding the aborted landing, and why the flight crew did not execute a go-around much earlier when it became clear the approach was unstable."
Homendy confirmed that the CVR and FDR were recovered in good condition and transported to the NTSB laboratory in Washington, D.C., for exhaustive analysis. While a preliminary summary of the recordings has been released, the full, word-for-word transcript of the cockpit conversation will not be made public until a later date.
"My Career is Over"
Shortly after the crash, as emergency responders swarmed the airfield, one of the pilots reportedly made a phone call to his spouse. According to sources close to the investigation, the pilot was overheard saying, "My career is over," reflecting an immediate, agonizing realization of the catastrophic errors that led to the overrun. Investigators have interviewed both Captain Carroll and First Officer Molina to determine who was flying the aircraft and why the critical airspeed warnings went unheeded.
Wider Implications for Aviation Safety
The crash of Flight 21 has reignited critical debates surrounding cargo aviation safety, pilot training, and airport infrastructure.
Crew Resource Management (CRM) Failures
At the heart of the NTSB’s preliminary findings is an apparent breakdown in Crew Resource Management (CRM). Developed in the late 1970s, CRM is a set of training procedures designed to foster open communication, situational awareness, and collaborative decision-making in the cockpit.
When one pilot repeatedly warned of excessive speed for nearly two minutes without receiving a structured, consistent response, it pointed to a dangerous breakdown in CRM. Investigators will examine whether steep cockpit hierarchies, fatigue, or training deficiencies prevented the monitoring pilot from taking active control of the aircraft to initiate a go-around.
Cargo vs. Passenger Safety Standards
The air cargo sector has expanded rapidly over the past decade, fueled by the rise of e-commerce giants like Amazon. However, aviation safety advocates have long questioned whether cargo operations are subjected to the same level of safety oversight and fatigue management as passenger airlines. Cargo flights often operate during overnight hours, when pilot fatigue is most acute. The NTSB will review the duty schedules and sleep histories of both Carroll and Molina to determine if fatigue played a role in their delayed reactions and poor decision-making.
Airport Runway Safety Areas and Infrastructure
The fact that the Boeing 767 traveled 1,300 feet past the end of the runway before striking ground vehicles has also turned attention toward airport design. Many major airports employ Engineered Materials Arrestor Systems (EMAS)—collapsible concrete blocks installed at the end of runways designed to safely decelerate an overrunning aircraft.
Investigators are looking into whether Runway 30 at Miami International Airport was equipped with an adequate runway safety area or EMAS, and whether such systems could have mitigated the severity of the overrun before the aircraft reached the perimeter roads where the ground crew van was parked.
As the NTSB continues its meticulous investigation, the aviation industry awaits a final report, which could take up to a year or more to complete. The findings are expected to yield sweeping safety recommendations aimed at preventing similar runway excursions and ensuring that the ground crews who keep the world’s aviation network moving are protected from the aircraft they service.
