TL;DR / 30 SECOND SUMMARY

The National Transportation Safety Board has released preliminary recorder observations from the September 6 runway overrun of 21 Air cargo Flight 7598 at Miami International Airport. A pilot repeatedly raised concerns about speed during the approach, and a go-around was called after a sound consistent with touchdown. Those observations establish a sequence to investigate, not a conclusion about cause or responsibility.

Key facts

  • 21 Air Flight 7598 was a Boeing 767 cargo flight from San Juan to Miami.
  • The recorder summary is preliminary and subject to change.
  • Voice and flight-data times have not been precisely synchronized.
  • The NTSB has not issued a cause finding in this update.

Timeline

THEN

September 6 — Flight 7598 overruns Runway 30 at Miami International Airport. September 9 — the NTSB publishes preliminary recorder observations. Next — investigators review the full cockpit recording and prepare a transcript; the inquiry remains open.

NOW

The new details explain why the final approach and landing sequence is central to the inquiry. They do not, by themselves, establish whether weather, aircraft systems, crew decisions or another factor caused the overrun. Treating a recorder excerpt as a final accident finding would run ahead of the investigation.

NEXT

The next substantive milestone is the NTSB's planned cockpit-voice-recorder transcript and later investigative findings. This is not a live airport-operations advisory; travelers should use Miami airport and airline channels for current flight status.

A sequence, not a verdict

The NTSB's selected cockpit observations show speed concerns voiced during the approach. Its flight-data summary describes touchdown, braking, a brief application of thrust consistent with a go-around attempt and renewed braking. The agency cautions that the two clocks are not precisely synchronized, so the excerpts should not be fused into a second-by-second reconstruction.

What remains unanswered

The public update does not establish why the aircraft overran the runway. Investigators still need to interpret the full recordings alongside other evidence and produce their written findings. The Associated Press also reported the speed warnings while emphasizing that the inquiry is still underway.

What to watch next

The NTSB says a cockpit-voice-recorder group will review the accident flight and prepare a transcript. A new transcript or formal investigative finding—not an isolated excerpt—would materially change this account. Passengers checking a current Miami flight should consult their airline and the airport rather than use an accident investigation as an operations feed.

ASK NIVEGU AI

What are you still wondering?

Answers will use this briefing and its cited sources.

Sources and further reading

01NTSB — Flight 7598 investigation and recorder update02Associated Press — Miami cargo-plane recorder account
FAQ

Questions, answered.

What is the short version?

The National Transportation Safety Board has released preliminary recorder observations from the September 6 runway overrun of 21 Air cargo Flight 7598 at Miami International Airport. A pilot repeatedly raised concerns about speed during the approach, and a go-around was called after a sound consistent with touchdown. Those observations establish a sequence to investigate, not a conclusion about cause or responsibility.

Why does this matter now?

The new details explain why the final approach and landing sequence is central to the inquiry. They do not, by themselves, establish whether weather, aircraft systems, crew decisions or another factor caused the overrun. Treating a recorder excerpt as a final accident finding would run ahead of the investigation.

What should readers watch next?

The next substantive milestone is the NTSB's planned cockpit-voice-recorder transcript and later investigative findings. This is not a live airport-operations advisory; travelers should use Miami airport and airline channels for current flight status.

Related companies and projects

See an error? Let us know.