A 172-knot threshold crossing sits at the center of Captain Steve’s reconstruction of the Miami overrun. He repeatedly stresses that no probable cause has been established and that the NTSB investigation is still underway, but argues that the available flight data and landing footage show an aircraft arriving roughly 30 to 35 knots faster than he would expect for a normal full-flap landing. That distinction between confirmed observations and his interpretation is important, especially because the presentation is being made very soon after a fatal accident.
His greatest contribution is the unusually specific explanation of how a Boeing 767-300 behaves during touchdown. Drawing on more than two decades flying the type, he explains the forward-tilting main landing gear, the tilt sensors involved in spoiler deployment, and why getting both main gear assemblies properly on the runway matters for braking effectiveness. The description turns what initially looks like a simple runway overrun into a more understandable sequence involving lift, wheel loading, spoilers, brakes and reverse thrust.
Repeated slow-motion examination of the landing provides the clearest evidence for his argument. He identifies an early-looking flare, a prolonged float, the nose gear appearing to contact before both main gear assemblies are settled, and the left main gear remaining tilted for an extended distance. His broader point—that every second spent floating or partially airborne consumes runway while delaying the aircraft’s most effective stopping systems—is presented clearly and makes the runway geometry meaningful rather than merely dramatic.
The analysis becomes less secure when visible clues are converted into conclusions about systems the footage cannot fully reveal. Captain Steve says the spoilers appear not to deploy and that he cannot see the engine entering reverse until very late, but camera angle, distance and obstruction limit what can confidently be established from the recording alone. He generally qualifies those statements, yet phrases such as saying the aircraft apparently had nothing wrong with it or describing the landing technique as terrible move closer to judgment than the still-incomplete evidence warrants.
His use of the “Swiss cheese” model is effective because it avoids reducing the crash to one mistake. Excess speed, an early flare, extended floating, delayed full gear contact and potentially delayed deployment of stopping devices are presented as interacting factors that could collectively explain the overrun. He also leaves room for possibilities such as an unexpected tailwind, microburst, mechanical issue or other circumstance that might substantially change the interpretation once investigators obtain more information.
The closing discussion of a go-around is therefore both useful and somewhat premature. Based on the conditions he believes the footage shows, Captain Steve says a go-around appears to have been available and would have been appropriate, while still withholding a final judgment pending additional evidence. His emotional response to the deaths and injuries gives the analysis an appropriate human dimension, although the strongest portions remain those where his 767-specific technical knowledge explains precisely why a long, fast touchdown can rapidly exhaust even a runway that would ordinarily be adequate.
Pros
- Uses extensive Boeing 767-300 experience to explain landing-gear geometry, spoiler logic and braking effectiveness in accessible terms.
- Connects reported ADS-B speeds with visible floating and delayed touchdown to build a coherent preliminary reconstruction.
- Slow-motion examination makes subtle details such as main-gear tilt and touchdown sequence easier to understand.
- Correctly emphasizes that an adequate runway can become inadequate when excess speed and delayed deceleration combine.
- Repeatedly acknowledges that the NTSB has not established a probable cause and that environmental or mechanical factors could alter the picture.
- The Swiss cheese framework usefully presents the accident as a possible chain of interacting factors rather than a single failure.
Cons
- Some conclusions about spoiler and reverse-thrust deployment rely heavily on limited external footage that may not reveal every system action clearly.
- Statements about poor landing technique and the apparent absence of aircraft problems occasionally sound more definitive than the unfinished investigation supports.
- The same landing sequence is replayed and explained several times, creating unnecessary repetition after the technical point is established.
- The microburst possibility is raised largely from personal experience and visible clouds rather than evidence that one actually affected this approach.
- The go-around judgment is plausible within the presented reconstruction but remains dependent on facts that investigators had not yet established.
Captain Steve provides a technically valuable early analysis because his familiarity with the 767 turns an apparently simple runway overrun into a detailed explanation of speed, lift, landing-gear sensing and delayed deceleration. The strongest conclusions remain provisional, however, because external video and ADS-B data cannot establish every cockpit action, system condition or environmental factor. As a preliminary reconstruction rather than a determination of cause, it is informative, unusually specific and appropriately worth revisiting once the investigation supplies firmer evidence.
