NTSB cockpit voice data on the Amazon Prime cargo jet crash in Miami
Newly released cockpit voice and flight data show a rushed, unstable approach and missed chances to stop the jet — bad news for 21 Air and the crew as blame comes into focus.
- The plane came in too fast and too high, touched down nose-wheel first, and landed thousands of feet past the normal touchdown zone.
- The co-pilot repeatedly called out the excessive speed, but got no clear response from the pilot flying.
- Wing spoilers never came up and reverse thrust was never used, even after the crew gave up on a last-second go-around.
- The go-around attempt failed because big jet engines need seven to nine seconds to build power — the plane barely slowed at all in four seconds.
- The jet ran off the paved runway ten seconds before impact and hit a van and an SUV at highway speed, killing five people.
Outlook: The findings point toward crew decision-making and communication as the central cause, with pressure likely to build on 21 Air's training and stabilized-approach procedures.