A touchdown nearly 4,000 feet down a 9,360-foot runway immediately establishes why the newly released flight-data information matters. Juan Brown walks through the final 30 seconds of the 21Air 767’s movement in Miami, using the NTSB’s reported speeds and control inputs to reconstruct an increasingly precarious sequence. His presentation is strongest when it stays close to those released data points rather than trying to determine prematurely why the crew made them.
The timeline is exceptionally clear. Brown explains that the right main and nose landing gear touched down at 158 knots, braking was recorded seven seconds later at 146 knots, and the left main gear did not touch until the aircraft had slowed to 134 knots. He also appropriately flags an important uncertainty: the indication that brakes were applied does not necessarily establish exactly what brake pressure reached the wheels. That kind of qualification is valuable in an investigation where recorded parameters can be easier to describe than to interpret.
The most startling portion comes near the runway’s end. According to the flight-data information presented, the brakes were released and go-around thrust applied at 120 knots, only for thrust to be returned to idle four seconds later at 117 knots while the brakes were reapplied. Brown estimates that the attempted go-around began within roughly the final 1,000 feet of runway, and the aircraft was still traveling 96 knots at its first impact and 65 knots when the recording ended. Presenting those figures sequentially gives viewers an unusually tangible sense of how little time and distance remained.
Equally important is what apparently did not happen. Brown reports the NTSB finding that the speed brakes or ground spoilers never deployed and neither did the thrust reversers, but he does not claim to know why. He specifically leaves open crew action, mechanical problems and possible complications involving ground-air logic because of the unusual landing sequence. That restraint is one of the report’s better features, particularly because the delayed left-main touchdown could make simplistic explanations misleading.
Additional information about the aircraft and crew provides useful context without proving causation. The stated cargo weight was 32,222 pounds and landing weight 231,236 pounds, which Brown characterizes as normal for the 767. He also reports that the 55-year-old captain received his 767 type rating in May 2026 and listed 7,145 total hours on his medical, while the 37-year-old first officer received his type rating in April 2025 and listed 2,655 hours. Those figures are relevant background, but neither total flight time nor recent type qualification by itself explains the overrun.
The weakest moment comes after an otherwise disciplined presentation, when Brown characterizes the event as a familiar case of a pilot entering a panic state, deciding to go around too late and then rejecting that go-around. The flight data certainly supports describing a late application of go-around thrust followed seconds later by a return to idle, but it does not establish the crew’s mental state or even identify which pilot made which decision. Brown himself notes that the pilot flying and pilot monitoring were not yet known, and the cockpit recording and crew interviews were still pending. His interpretation may ultimately prove insightful, but at this stage it moves further beyond the available evidence than the rest of the report.
Pros
- The final 30 seconds are reconstructed with specific speeds, control changes and elapsed times, making a complicated sequence unusually easy to follow.
- Brown carefully distinguishes several important unknowns, including actual brake response, the reason spoilers and reversers did not deploy, and the respective crew roles.
- Correlating the reported touchdown speed with preliminary ADS-B positioning provides useful runway context while being identified as an estimate.
- Crew experience, aircraft weight and the status of the cockpit recording add relevant investigative context without overwhelming the central timeline.
Cons
- The closing description of a pilot being in a “panic state” goes beyond what the flight-data information presented can establish.
- Characterizing the occurrence as a familiar late-go-around scenario risks settling on a causal narrative before the cockpit recording, crew interviews and further investigation are available.
- The discussion of reported safety concerns at 21Air is too undeveloped to contribute much beyond noting that the NTSB requested relevant information.
Brown turns a compact set of newly released flight-data points into a remarkably understandable reconstruction of an unusual and consequential landing sequence. The report is strongest when preserving the distinction between recorded aircraft behavior and its still-unknown causes, while its more confident closing interpretation would have been better reserved for additional investigative evidence.
