A rapidly deteriorating approach into Miami sits at the center of a debrief that tries to explain not merely how a Boeing 767 left the runway, but why an experienced flight crew continued after multiple opportunities to abandon the landing. The presentation reconstructs the sequence from nine miles out, showing the aircraft initially in a reasonably comparable position to traffic ahead before remaining substantially faster, leveling and even climbing, then descending aggressively toward the runway. That progression gives the analysis a clear foundation: whatever ultimately explains the crew’s decisions, the approach became increasingly difficult to salvage long before touchdown.
The most useful work comes from combining the aircraft’s reported flight data with the changing weather and preceding traffic. The comparison with a 737 ahead is particularly effective: both were around 215–222 knots at nine miles, but near 5.7 miles the 737 was reportedly around 192 knots while the 767 remained around 224 knots. The debrief then traces the 767 leveling near 1,500 feet, gaining speed, disconnecting the autopilot and descending at a very high rate while still improperly configured. By 1,000 feet, the presenter describes an aircraft roughly 30 knots fast and descending around 2,000 feet per minute, followed by repeated sink-rate and terrain warnings. Those details make the continued landing attempt increasingly difficult to understand.
Weather receives considerably more attention than a simple thunderstorm explanation. Historical tower audio is used to demonstrate winds shifting from 280 degrees at nine knots to 210 at 12–14 knots and later 190 at 19 knots gusting to 22. The reported conditions around touchdown are described as 190 at 17 knots gusting to 26, producing the presenter’s calculated combination of tailwind and crosswind components. He appropriately stops short of claiming that weather caused the crash, instead arguing that rapidly changing winds were relevant to pilot decision-making. His discussion of the controller not consistently providing updated winds raises a legitimate investigative question, although he is careful not to assign responsibility to the controller before the investigation establishes what information the crew actually received.
The runway discussion adds another important piece. Although runway 30 is described as 9,360 feet long, its displaced threshold leaves a stated landing distance available of 7,913 feet. The presenter emphasizes that this was still adequate under ordinary circumstances and focuses instead on the extraordinary state in which the aircraft eventually reached the pavement. According to the reconstruction, the left main gear touched down with only about 1,800 feet remaining, spoilers and thrust reversers were not used according to the information cited, and a go-around was attempted with roughly 970 feet remaining before the aircraft exited the runway at about 117 knots. The explanation of the approximately 1,300-foot runway safety area also provides valuable context for why an otherwise compliant safety zone could not reasonably absorb such a high-speed excursion.
Two earlier accidents are used to broaden the discussion of crew performance and runway overruns. The lengthy examination of the 2019 Atlas-operated 767 crash is informative, especially its account of documented training difficulties, spatial disorientation and an inadvertent go-around-mode activation. It demonstrates how investigators examine a pilot’s training history rather than treating the final seconds of an accident in isolation. However, the presenter pushes the comparison too far when he says he can “almost guarantee” investigators will uncover something relevant in the Miami captain’s or pilot’s past. He repeatedly acknowledges that their records could prove spotless, but the prediction still invites suspicion about individuals whose training histories have not yet been established.
The fatigue discussion is similarly worthwhile but necessarily conditional. By tracing the aircraft’s earlier legs and explaining the difference between possible crew report times, the presenter identifies a question investigators should resolve rather than claiming fatigue as an established cause. His comparison with passenger-duty limitations under Part 117 makes the cargo exemption understandable: under his hypothetical early report time, he argues that an equivalent three-leg passenger schedule would have exceeded the applicable duty period. Because the crew may instead have joined the aircraft later in Miami, however, the entire fatigue argument depends on information that remains unknown. The debrief generally recognizes that limitation even while giving the issue substantial prominence.
The closing examination of unstable approaches gives the accident a broader safety context. Statistics attributed to Flight Safety Foundation and FAA-related work are used to argue that crews frequently continue approaches that technically fall outside stabilization criteria, potentially normalizing small deviations until pilots become too willing to salvage larger ones. The presenter wisely notes that many recorded unstable approaches may involve comparatively minor deviations, making the headline percentages sound more alarming than their practical significance warrants. Applied to this crash, though, his distinction is persuasive: the reconstructed combination of excessive speed, extreme descent rate, incomplete configuration and repeated automated warnings represents something far more serious than a marginal technical exceedance.
Pros
- Reconstructs the approach with specific distances, speeds, altitudes and reported flight-recorder information rather than relying solely on crash footage.
- Historical tower audio makes the rapidly shifting wind conditions unusually clear and gives useful context to the crew’s operating environment.
- Clearly distinguishes changing weather as a potential decision-making factor from claiming that weather caused the crash.
- Explains runway length, displaced threshold, runway safety areas and stabilization concepts in accessible terms.
- Appropriately identifies fatigue as an unresolved investigative question because the crew’s actual report time is not yet established.
- The final discussion distinguishes minor stabilization deviations from the much more severe conditions described during this approach.
Cons
- The extensive 2019 crash comparison sometimes overwhelms the analysis of the Miami accident itself.
- Predicting that investigators will probably uncover something problematic in a pilot’s history goes beyond the evidence currently presented.
- Several interpretations of cockpit actions, including why the aircraft leveled and which pilot was likely flying, remain explicitly speculative despite receiving substantial discussion.
- Some aircraft-limit and system discussions are accompanied by admissions that the presenter is not certain of the applicable 767 details.
- The live-stream format creates repetition and lengthy detours that could have been tightened without sacrificing the technical substance.
The careful reconstruction of speed, descent profile, configuration, winds and runway geometry makes a compelling case that numerous warning signs accumulated well before the fatal overrun. Its strongest contribution is showing how many investigative questions remain open, though occasional predictions about pilot history and cockpit behavior stray beyond the otherwise disciplined reliance on available evidence.
