Having pilots fighting over the controls is not a situation anyone wants. The pilot monitoring saying go around should have caused an immediate reaction, the human factors behind why it didn't will probably feature prominently in the post-accident actions.
If any of the two pilots feel uncomfortable about the approach, they are actually drilled to just order a go-around, not politely ask and hint that they would prefer to do it like this FO did (wastes time). Ideally the pilot flying should then do it, but if they don't, the pilot monitoring can also take control (while clearly stating "my controls, going around") and do it. One major issue that I bet the NTSB will note in the final report is that both pilots were relatively new to the aircraft and to the airline, usually it's preferable to pair an inexperienced FO with more experienced captains.
(not an aviation expert, just summarizing various bits and pieces I gathered from various YouTubers over the last days)
Also not an expert, I wonder if there's some rule where a "Go around!" order has precedence over any other activity anyone in the cockpit wishes to perform.
As a passenger I had my first go around a few days ago, but we were 5km away from the runway.
Wouldn't be a case of "if I fix it then there was nothing wrong"? How do you, as an inferior rank, step in to correct something that you think is going to happen? Imagine the inferior officer steps in and lands the plane, wouldn't the superior officer say well duh that's what I was doing why did you intervene? It's an interesting conundrum, I think, and may exacerbate the reaction or lack thereof..
The PM got his rating about 18 months ago. The PF only got his this past May. The PM had more overall hours, but this is looking a lot like a skills issue. He was flying an unstable approach. He wasn't configured for landing.
This pairing, considering past incidents with similar airframe vs. total hours disparity, really does look to be bad practice. You've got to acknowledge the human psychology. Part of it is probably the crazy pipeline over the past few years where people are racing to 1500 hours no matter how they log them, or they're getting on restricted certs with lower hours.
I really don't think time in this particular type is a factor. None of what I've heard or read has anything to do with familiarity with its unique systems. Everything sounds like sloppy flying. Sounds like he, the PF/PIC/Captain, started the descent late, stayed too high, didn't manage the power curve well, landed long and fast and willfully ignored his first officer. One bad decision after another where instead of properly correcting it or making the safe decision to try again he decided to plow onwards.
The training pilots go through to get type rated and to be allowed to fly by airlines is incredible. But knowledge is one thing, attitudes and behavior and truly taking safety to heart outside the sim is another. I bet this guy was slightly reckless in every model he's flown.
Another alternative is external social factors acting on the captain. Maybe he was distracted by personal issues. There again though, if you're not fit to fly that day, you call out.
Having pilots fighting over the controls is not a situation anyone wants. The pilot monitoring saying go around should have caused an immediate reaction, the human factors behind why it didn't will probably feature prominently in the post-accident actions.
If any of the two pilots feel uncomfortable about the approach, they are actually drilled to just order a go-around, not politely ask and hint that they would prefer to do it like this FO did (wastes time). Ideally the pilot flying should then do it, but if they don't, the pilot monitoring can also take control (while clearly stating "my controls, going around") and do it. One major issue that I bet the NTSB will note in the final report is that both pilots were relatively new to the aircraft and to the airline, usually it's preferable to pair an inexperienced FO with more experienced captains.
(not an aviation expert, just summarizing various bits and pieces I gathered from various YouTubers over the last days)
Also not an expert, I wonder if there's some rule where a "Go around!" order has precedence over any other activity anyone in the cockpit wishes to perform.
As a passenger I had my first go around a few days ago, but we were 5km away from the runway.
Isn't it? Pretty sure its actually the drilled and trained commandment. If you doubt, speak up, and if that fails, take control. [0]
[0] https://en.wikipedia.org/wiki/Crew_resource_management
There are a lot of things which are drilled and trained which have gone wrong in this incident.
Wouldn't be a case of "if I fix it then there was nothing wrong"? How do you, as an inferior rank, step in to correct something that you think is going to happen? Imagine the inferior officer steps in and lands the plane, wouldn't the superior officer say well duh that's what I was doing why did you intervene? It's an interesting conundrum, I think, and may exacerbate the reaction or lack thereof..
Your comment doesn't answer my question.
> Having pilots fighting over the controls is not a situation anyone wants
Nor crashing and killing 5 people.
The PM got his rating about 18 months ago. The PF only got his this past May. The PM had more overall hours, but this is looking a lot like a skills issue. He was flying an unstable approach. He wasn't configured for landing.
This pairing, considering past incidents with similar airframe vs. total hours disparity, really does look to be bad practice. You've got to acknowledge the human psychology. Part of it is probably the crazy pipeline over the past few years where people are racing to 1500 hours no matter how they log them, or they're getting on restricted certs with lower hours.
I really don't think time in this particular type is a factor. None of what I've heard or read has anything to do with familiarity with its unique systems. Everything sounds like sloppy flying. Sounds like he, the PF/PIC/Captain, started the descent late, stayed too high, didn't manage the power curve well, landed long and fast and willfully ignored his first officer. One bad decision after another where instead of properly correcting it or making the safe decision to try again he decided to plow onwards.
The training pilots go through to get type rated and to be allowed to fly by airlines is incredible. But knowledge is one thing, attitudes and behavior and truly taking safety to heart outside the sim is another. I bet this guy was slightly reckless in every model he's flown.
Another alternative is external social factors acting on the captain. Maybe he was distracted by personal issues. There again though, if you're not fit to fly that day, you call out.
This isn’t a skill issue, it’s laziness and negligence.