Originally published at: NTSB: FO Twice Called for Go-Around Before Runway Overrun
Preliminary report details captain’s decision to continue approach in heavy rain at Roanoke despite go-around calls.
I don’t know about CommuteAir, but I thought in aircraft/operations like this a go-around call by either crew member was mandatory. We’ll see what happens to the Captain on that point. It will be interesting to see whether the NTSB will talk about whether the FO should have taken control from the Captain and gone around.
I share the same thoughts as Ron Levy.
Frankly, I have to question the judgment/headwork of the captain.
Even without the go-around calls from the FO, he should have initiated a go-around once he passed the picket fence and half the runway.
This is basic, good airmanship - sound judgment - and something taught early in one’s training.
Cleary, a completely preventable mishap.
Mark Denari
The regional I flew with had that policy. If either crew member called for a go-around there was no question; a go-around would happen. We would talk about it on the ground afterward if there was a disagreement. Most, if not all, U.S. airlines have a no-fault go-around policy for a reason.
My regional airline also had a policy about landing within the touchdown zone or first third of the runway, whichever was smaller. It seems that either of those policies would have stopped this incident.
I remember the question from a job interview for my first crewed flying job. “If you, as a first officer, call for a go around and the Captain doesn’t commence the go around, what do you do?” The answer they wanted was “physically push the power levers forward and be assertive.”
It’s noteworthy that the EMAS turned it into a safety non-event for the crew/pax and a minor event for the aircraft. Imagine if that’d been just grass with lighting or other equipment out there… or a road.
This topic was automatically closed after 7 days. New replies are no longer allowed.