The discussion centers on the NTSB preliminary report of a Prime Air Boeing 767 runway overrun. Ryandrake reminded readers that preliminary reports typically don’t assign probable cause. Userbinator and ocdtrekkie flagged that both pilots were recently hired and relatively inexperienced on type, while FabHK summarized FDR/ADS‑B and CVR snippets showing an approach well above Vref, touchdown about 3,750 ft beyond the threshold, strong crosswinds, speed brakes and thrust reversers not deployed, a late and aborted go‑around, and intermittent weight‑on‑wheels indications. Jeffbee added that reversers wouldn’t have armed without a proper ground state and noted the crew’s go‑around thrust input would have prevented reverser deployment.
Opinion coalesced around human factors but divides on emphasis. Several commenters (sokoloff, FabHK, xyzzy_plugh) called the sequence "appalling airmanship" and blamed the captain for failing to go around and for excessive speed/late touchdown, while jameshilliard argued the first officer should have called and executed a go‑around. Others (sippingabonedry, rootusrootus) pointed to GPWS and unstable approach alerts as clear go‑around triggers. A contrasting strand flagged systemic issues: pairing inexperienced crews with limited type time (ocdtrekkie) and the need to understand "why" to prevent recurrence (dylan604, mjevans), rather than simply restating pilot error.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.