Amazon Prime Air Boeing 767 Crash Update: 120-Knot Go-Around Attempt & More Accidents

The Amazon Prime Air Boeing 767 crash in Miami remains the lead story in this episode as new information from the NTSB provides important details about the final seconds of Flight 7598.

The Boeing 767 ran off the end of the runway at Miami at more than 100 knots. In the previous episode, Max Trescott analyzed the aircraft’s ADS-B track and found that the airplane initially appeared to be descending normally before leveling at approximately 1,600 feet. That left the Boeing about 500 feet above its desired vertical path only two miles from the runway.

The crew subsequently descended at an angle approaching six degrees—roughly twice a normal three-degree descent.

Now the NTSB has released a summary of the cockpit voice recorder.

One minute and 42 seconds before the recording ended, one pilot called for flaps 20 and the other cautioned that the aircraft was too fast. According to the NTSB, additional comments about excessive speed continued through the remainder of the recording, but there was not a consistent verbal response to those warnings.

The aircraft touched down 31 seconds before the recording ended.

Then came one of the most striking details: 16 seconds after touchdown, a pilot called for a go-around.

One second later, the brakes were released while the Boeing was still traveling at approximately 120 knots, and the throttles were advanced to a setting consistent with go-around thrust. Four seconds later, the throttles returned to idle and the brakes were reapplied.

About one second after that, sounds consistent with the aircraft leaving the paved surface were recorded at approximately 117 knots.

The recorded data showed no indication that either the speed brakes or thrust reversers were deployed.

Max also expands on a possible explanation for how the approach became unstable. The Boeing 767’s VNAV PATH mode can follow a computed vertical path, but unlike glideslope mode, it will level the airplane when it reaches the altitude selected by the crew. Max believes it is possible the crew expected the airplane to continue descending but instead encountered an automation surprise when it leveled at 1,600 feet.

That could help explain how Flight 7598 ended up both high and fast close to the runway.

The episode also looks at Amazon’s history with contract cargo operators. The 767 involved in the Miami accident had previously been operated for Amazon by Atlas Air before being transferred to Twenty One Air. One week after the Miami accident, Amazon announced that it was pausing operations with Twenty One Air.

Another major accident this week involves KNBC television helicopter N358TV, a Eurocopter AS350B2 that crashed in Los Angeles on September 15, killing both people aboard and one person on the ground.

Audio from the helicopter’s live television broadcast captured a change in engine sound and warning tones shortly before the crash. Experts have said the warning resembles the AS350’s low-rotor-RPM warning, although investigators have not established that conclusion.

Max’s analysis of the ADS-B data shows the helicopter slowing to roughly five knots at approximately 800 feet above the ground before beginning a rapidly increasing descent. During the final 18 seconds, it lost roughly 925 feet while accelerating to about 40 knots, with a reported final descent rate near 4,800 feet per minute.

The episode next examines a fatal accident involving N734ZK, a Cessna 172N, at Montgomery-Gibbs Executive Airport in San Diego. The aircraft had been conducting repeated traffic-pattern operations when the pilots announced a go-around. Seconds later, the airplane crashed.

Photographs appear to show the Cessna’s flaps still fully extended. The older 172N can use as much as 40 degrees of flaps, producing substantial drag during a go-around if they are not promptly retracted to the prescribed setting.

ADS-B data also shows the airplane becoming extremely slow before the runway threshold.

A new preliminary report covers N9485P, a fatal Piper Comanche accident at Seldovia, Alaska, that killed four people. Witnesses described a fast approach, several hard bounces, full power being applied, and the airplane remaining extremely low before striking a tree and entering the water.

Among the final reports, Max and Rob examine the crash of N93R, a Lockheed 12A at Chino, California. Investigators found the airplane attempted takeoff with its flaps fully extended, while engine RPM was also below the normal takeoff range.

They also discuss N413AW, a Pipistrel Alpha trainer that suffered fuel exhaustion after the flight instructor and student relied on difficult-to-read fuel indicators rather than visually checking the tanks through the filler openings.

Finally, N188PC, a Pilatus PC-12 accident near San Angelo, Texas, demonstrates the deadly danger of spatial disorientation. After confusing ATC vectors and an incorrect heading selection, the airplane entered an extreme unusual attitude in IMC, ultimately descending at approximately 15,000 feet per minute.

The episode closes on a positive note with with a story from the NASA ASRS Callback newsletter. A Cirrus SR22 pilot in IMC became distracted troubleshooting electrical problems, recognized that the airplane was slowing dangerously, stopped troubleshooting, regained control, and landed safely—a powerful reminder of the order of priorities: aviate, navigate, communicate.