Comment by cyberrock
9 hours ago
Looking at it from the glass-half-full perspective, I'm impressed that pilots declare go-around as often as they do. As someone who sometimes can't decide whether I should declare a production incident (even if it's not my change), I wonder if it's possible to learn that decisiveness.
> I wonder if it's possible to learn that decisiveness.
If the culture allows for it, yes.
On final my instructor was talking about the next approach. I heard the words 'go around' and immediately executed one. He realized that (1) that conversation was unnecessary at that phase of the flight and (2) to not use those words unless he wants me to immediately go around :)
After soloing, I sometimes report that I had to go around because I didn't like how the approach or landing was looking like. I got praised for it every time.
So yes, it's all culture.
> can't decide whether I should declare a production incident
A supportive culture encourages you to declare early at the first sign you feel something isn't right.
The fact you're struggling to decide means it should be declared but you feel some negative force if ends up not as serious as you think.
A supportive culture will work with you and if necessary down grade the priority if it can wait until a regular release cycle.
It's the same rot that set into Telstra https://news.ycombinator.com/item?id=49534127
That's why there are standards that define when to go around. If you aren't stable, on glide slope, at proper airspeed, and the before-landing checklist complete at 1000 feet, a go-around is mandatory. There's no choice at that point (or should not be).
Way better to abort and try again, than commit and run the risk of something going wrong. What harm is there in doing a go around if you can? They have plenty of fuel to try multiple times, and have clearance to do so if required.