Even if something was missed, it's very strange to not realize that the plane is still on the ground when you can see the end of the runway, despite what the computers are saying. Usually pilots have trouble trusting the instruments over their own senses, but in this case it's like the opposite.
Nothing can help you when you refuse to operate the plane correctly.
It makes sense that there’d be a “clean cockpit” magic button to push, but not only would the magic button need to be tested in every aspect of flight, in every configuration, in every combination of working and broken sensors… but airplanes are flippin’ complex, and flying modern airliners as part of an airline is even more complex.
At first I saw they might have been fired and thought damn that is strict.
Emirates has a pretty good rep but this doesn't help.
There has been another incident where an Emirates crew lacked any kind of basic aircraft handling: https://en.wikipedia.org/wiki/Emirates_Flight_521
Their main problem is a very bad rep for working conditions. Crews being overly fatigued, arcane labour laws in UAE, that makes it harder for them to hire pilots and to retain experienced pilots. Combined with a local market that doesn't have a big aviation history so less people to build on.
This is very bizarre. I once had a morning flight out of Denver (not too long ago, August 2008?) and talking to people there apparently the plane had an electronics malfunction of some sort. They said they would fly us out as soon as the plane was ready but about ten hours later, they gave up and flew us out on a plane with a different airline (which I assume was not free for them, I doubt American Airlines would fly a plane for free for United). Point is the initial problem, at least what they told us, was some lights failed to turn on but they refused to fly. I thought flight crew were very risk averse but clearly not everyone.
These guys even flew the plane back instead of being replaced by another crew, and that's with a plane that has just been used way in excess of its design parameters on more than one measure.
Really throwing failures at pilots without them knowing what's going on seems to mean too many fail or rather there is not enough time to train pre-discussed scenarios and do scenarios that aren't announced.
I'm not sure it's really what you'd want.
All pilots are trained to know the immediate actions required for a whole set of scenarios (we call these memory items) the point of the sim check is not to learn them but to check that you know all of them and to keep some recent experience. Because these things happen so rarely in real flights.
I've had for example only once had an engine failure after takeoff and it was a partial failure without fire. In the simulator I think I've done it at least 100 times and most times they put it on fire for good measure so you're in a hurry to get on the ground. The real world one was very uneventful, return to the airport, taxi back, do a lot of paperwork.
And that is how it should be. Pilots must be able to handle every possible failure. They don’t need to know every single procedure by heart, they’ve got the manuals in the cockpit for non-urgent procedures.
My father loves _flying_. He’s from a generation that trained on airplanes with little automation. He often talked about younger pilots relying too much on instruments. He would get annoyed with pilots that didn’t appreciate manually flying a plane.
I'm just asking if it's really a reality as i previously got the impression airline training wasn't quite at that level. As in mostly you get an engine out because that needs training every time. And if the unexpected scenario is an engine out most of the time ... it's not really unexpected.
I wonder how often stuff like static port blockages and even maybe the flight director being wrong during takeoff are trained in an unexpected fashion. I'd expect quite rarely if at all. That's ok i suppose as it's rare failures, but the descriptions here kinda suggested a level of random scenarios being thrown at pilots ... which isn't quite realistic i think due to limited simulator time alone.
> I am not a pilot, but that's exactly what I thought when I read the memo too. They should be putting responsibility for the next flight on the next flight's crew, not the prior flight's crew.
It's not a matter of responsibility, it's a risk mitigation measure. Adding the additional check is common in aviation. Yes, it is the next crew's responsibility, however if you can mitigate a risk by adding some procedure to what the previous crew does, at little or no cost until a software update is released fixing the issue, you do that every time.
Why on earth would you give the pilot an instruction that would almost certainly lead to a crash ? It seems like there aren’t enough sanity checks. Any such dodgy situation should trigger an alarm and disengage the auto pilot imo.
Commercial aviation is designed around highly trained people following defined procedures. Auto pilots are not supposed to second-guess the inputs because that adds to confusion and cognitive load on the pilots. Pilots tell the computer what to do, not the other way around.
What _should_ have happened here is the pilot monitoring should be watching the instruments and calling out flight stages. When the pilot flying didn’t initiate a proper climb they should have called this out, or taken over control until a safe altitude was established. This wasn’t an autopilot issue, this was a breakdown on crew resource management.
It's hard to say if it's a good thing or not, imagine an incorrect flight plan is entered but non 0, you could fly straight into another flight path or an obstacle, like a mountain.
I am not a pilot, but that's exactly what I thought when I read the memo too. They should be putting responsibility for the next flight on the next flight's crew, not the prior flight's crew. Train each crew to assume the plane they're prepping for their next flight is FUBAR in every way, checklist everything, fix it as necessary, and go from there. Don't rely on the prior crew for anything.