The September 6, 2026 accident involving 21 Air Flight 7598 at Miami International Airport is no longer just a runway-overrun story. The NTSB preliminary report now shows a much more complex operational sequence: a fast approach, repeated speed concerns in the cockpit, a long touchdown, a go-around attempt after runway contact, and no recorded deployment of speed brakes or thrust reversers. Five people on the ground were killed, and Amazon later suspended operations with 21 Air.
Updated on October 7, 2026 with findings from the NTSB preliminary report and the operational consequences for Amazon Air.
The accident matters beyond one cargo operator. It raises questions about stabilized-approach discipline, cockpit decision-making, air traffic wind information and the risk controls built into outsourced cargo networks.
An Amazon Air flight operated by 21 Air
The aircraft was Boeing 767-33A freighter N1997A, operating from San Juan, Puerto Rico, to Miami. It was part of the Amazon Air network, but 21 Air was the certificated operator responsible for the flight crew and day-to-day operation.
That distinction is important. Amazon was the customer and network operator; 21 Air was the airline flying the airplane. The accident therefore sits at the intersection of airline safety oversight and the commercial model used by large e-commerce cargo networks.
According to the NTSB preliminary report, the 767 crossed the threshold of Runway 30 at about 105 feet above ground level with a groundspeed of roughly 177 knots. It then touched down about 3,750 feet beyond the threshold.
The first recorded wheel contact occurred at about 158 knots. By then, a substantial part of the runway had already been consumed. For investigators, this is central to understanding the energy the crew still had to manage after touchdown.
A fast, unstable approach with multiple warning signs
The cockpit voice recorder captured repeated comments from the first officer that the aircraft was too fast. The sequence also included automated “sink rate” and multiple “too low terrain” warnings in the final phase of the approach.
Those warnings do not establish probable cause. They do, however, show why the investigation is focusing so heavily on approach stability, crew coordination and the decision to continue toward landing.
The preliminary report also identifies an air traffic control issue that will require careful analysis. A few minutes before Flight 7598 was cleared to land, another aircraft had been given southerly wind information with gusts. That wind information was not repeated to the 21 Air crew with its landing clearance.
The NTSB notes that FAA procedures require wind direction and velocity to be issued when a tailwind component exists. This does not establish controller responsibility, but it creates another element investigators must place into the performance and decision-making timeline.
An unusually complex sequence after touchdown
The most unusual part of the sequence came after the airplane was already on the runway. Braking was applied at about 146 knots. The left main landing gear contacted the runway at about 134 knots.
Then, at roughly 120 knots, the brakes were released and thrust was advanced to a level consistent with a go-around attempt. Only seconds later, the thrust levers returned to idle and braking resumed.
Investigators will have to determine what options were still available at that stage, why the go-around was initiated so late, and why it was abandoned almost immediately.
Flight-data information released by the NTSB showed no recorded deployment of the speed brakes or thrust reversers during the landing sequence.
That is a major investigative point because these systems normally contribute substantially to deceleration after touchdown. It is still too early to say whether their absence resulted from crew action, system logic, the attempted go-around sequence or another factor.
The runway overrun and its human toll
After leaving the paved surface, the Boeing 767 continued beyond the runway end, struck airport equipment and then hit a Ford Econoline carrying seven people. Five occupants of the van were killed and two were seriously injured.
The aircraft later struck a Toyota Corolla Cross, whose occupant was also seriously injured. Both pilots survived with minor injuries.
N1997A was built in 1994 and later converted to cargo configuration. Its age is relevant background, but not evidence of cause. Freighters routinely remain in service for decades when maintained under approved programs.
The NTSB will examine the aircraft’s maintenance history, braking system, speed brakes, thrust reversers and performance calculations alongside the human and operational evidence.
Amazon’s suspension created an immediate business consequence
On September 14, Amazon suspended operations with 21 Air. Reuters and the Wall Street Journal reported that eight 21 Air aircraft had been dedicated to Amazon work.
The suspension does not determine fault and was not announced as a permanent contract termination. But it demonstrates how quickly a major safety event can alter a contractor relationship in an integrated cargo network.
Amazon Air relies on partner airlines to operate aircraft under their own operating certificates. This model gives Amazon flexible capacity without turning Amazon itself into the direct airline operator for every flight.
It also means safety performance depends not only on the network owner, but on the standards, training, culture and oversight of individual contractors. For the wider cargo sector, that makes this accident relevant far beyond 21 Air.
What the NTSB still has to answer
The preliminary report establishes facts, not a probable cause. Key questions remain: Why was the approach continued despite repeated speed concerns? How much did the wind component affect landing performance? Why was a go-around attempted after touchdown? Why were speed brakes and thrust reversers not recorded as deployed?
The final investigation will also examine crew resource management, 21 Air procedures, training, air traffic control, aircraft systems and runway-end safety considerations.
The most important lesson at this stage is not one single error, but the shrinking number of options as an unstable approach continues. Every additional second, every extra knot and every additional foot of runway consumed can make the recovery decision harder.
That is why stabilized-approach criteria and early go-around decisions remain core airline safety tools. The Miami accident shows how difficult the situation can become once the aircraft is committed deep into the landing sequence.
Related: Kinshasa: DC-8 freighter runs off runway at N’Djili
Main sources
NTSB investigation DCA26MA352, 21 Air Flight 7598
Reuters, Amazon suspension of 21 Air operations
Federal Aviation Administration; Miami-Dade Aviation Department; statements from 21 Air and Amazon.
Leave a Reply