Miami 767 Fatal Crash: It Just got WORSE

Summary of main points and analysis

• NTSB update and timeline from flight data recorder: The video discusses a late-night NTSB press briefing that provided a timeline based on the flight data recorder for the final seconds of the Amazon Prime 767 accident at Miami (runway 30). The creator argues the disclosed data confirms earlier concerns and is “not especially good” for the crew.

• Key performance issues before touchdown (unstable approach):

  • The aircraft was too fast and too high throughout the approach. The narrator repeatedly characterizes the landing as never being close to acceptable.
  • Touchdown conditions: Approximately 30 seconds before the recording ended, the nose gear and right main gear touched down at 158 knots ground speed. The narrator compares this with expected speeds, claiming the aircraft was ~18 knots faster than it should have been and ~37 knots too fast at 500 feet, and also above the glide path.
  • Flap configuration concerns: The narrator suggests they likely used flaps 25 (rather than flaps 30) and that airspeed remained near/above flap overspeed limits for extended portions of the approach.
  • Delay in braking / ineffective stop effort: Brakes were applied very late relative to when the aircraft should have been slowing down, resulting in only limited deceleration.

• Touchdown location and missed safety zone:

  • Using ADSB data and AI-assisted calculation, the narrator estimates the aircraft landed ~3,900 ft past the threshold, while the permissible touchdown zone ends at ~2,638 ft. This implies the crew landed about a quarter-mile outside the zone, where a go-around is required.
  • The video emphasizes that landing too fast/high and outside the touchdown zone left minimal margin to stop on the remaining runway.

• Failed/absent deceleration aids: speed brakes and go-around timing:

  • As described from the NTSB briefing, the flight data recorder did not show speed brakes or thrust reversers deploying during the event.
  • The narrator explains that speed brakes normally reduce lift and can improve braking performance; their absence would likely increase stopping distance.
  • The crew attempted a go-around only very late, and the narrator argues it was initiated too late for the engines to spool up and for recovery to be possible.

• Overall judgment (creator’s opinion):

  • The narrator claims that “pretty much everything the pilots could have done wrong, they did,” describing it as one of the most egregious deviations from reasonable decision-making they’ve seen in a decade.
  • They list multiple missed go-around decision points, including:
    • not being properly configured early
    • high/climbing then diving
    • likely overspeeding
    • crossing the threshold too fast and too high
    • touching down outside the touchdown zone
    • no meaningful braking benefit for several seconds
    • speed brakes not deploying
  • The narrator says they hope there is a “hidden explanation” (potentially clarified later by the cockpit voice recorder) but argues the preliminary data does not suggest a clear equipment failure or environmental factor.

• Additional controversy mentioned:

  • The video also references a streamer trespassing on the wreckage property the same night—being kicked off for trespassing—and potentially facing consequences on the platform. The narrator includes this as a broader “new world” side note.

Presenters / contributors (as named in the subtitles)

• Jennifer Homdy (NTSB chairwoman)
• The video narrator / presenter (name not provided in the subtitles)