3 ms·
I think context is what helps - - I’ve just taken off, and am going through the after take off checklist: Set the airspeed, power, climb rate, heading, talking
by _s 8y ago
I think context is what helps -
- I’ve just taken off, and am going through the after take off checklist: Set the airspeed, power, climb rate, heading, talking to ATC, planning the next stage of the flight
- Perhaps I’ve just raised the flaps and the plane starts behaving erratically
- My first / immediate thought is that my previous action led to an undesired aircraft state.
- I work from that point on
- I touch the electronic trim as habit, which resets the system briefly, and all seems well for a few seconds. I don’t know that the system reset itself.
- It goes all weird again all on its own
- Now I’m even more confused
Etc
Edit: I'm a low time private pilot flying a LSA, I genuinely don't know the procedures or processes in place for a 737, but I can empathise with their situation as I know how quickly things can go start going amiss in a plane.
- js2 8y agoI think that, not being a pilot, I can't really understand, but thank you again for the perspective. Edit: one last thing though - when the plane isn’t behaving as expected, why isn’t the first thing to check that all the control surfaces and the throttle are where you expect them to be?
- _s 8y agoOf course - generally the expectation is that control surfaces will not move on their own accord, unless specifically asked to; either directly by the pilot by moving the yoke/stick, trim wheel, rudder etc, or indirectly by setting the autopilot, which in turn moves those controls. If they move on their own accord - usually via autopilot - it's because they are trying to maintain a reference point the pilot asked them to. When they move on their own accord, outside of any pilot inputs or settings, without the pilot knowing / understanding why, that's where the issues start happening. Air France AF447 entering Alternate Law, Lion Air MCAS activating etc. The initial course of action is always to return to stable flight, disabling whatever systems you perceive to be changing the control surfaces. When you just don't know which system is causing the issue, then you're just fighting the end result (eg nose down), not the underlying system issue (eg MCAS preventing stall by enforcing trim). To find the cause of the end result (eg nose down), you work backwards to see what happened - because, chances are, you as a pilot made an erroneous setting / configuration somewhere to cause an undesirable aircraft state, not the system itself, as you are taught the system works under your command, plus no system acts to down an aircraft - they are all there to prevent an aircraft from getting into an undesirable state. You go back to the last known working configuration, and work from there to diagnose. Long winded answer, but yes, you do check control surfaces, but they only show an undesirable aircraft state which can be corrected (eg pull back on the stick), but it doesn't solve for the what and why, and thus preventing getting back into that undesirable state. Trim is also one of those ones right at the bottom to check, as it's for fine-tuning an aircrafts pitch - where an elevator can move an aircraft up or down tens of degrees in a seconds, trim usually only moves the pitch tenths of degrees. This is also where SOP's and training come in too - some airlines would have "set landing trim" on the final leg of the approach, others might have it on the base leg. Some companies require stall training in the sim once a year, other airlines don't even have sims. Some airlines are okay with reverse thrust on landing, others want to avoid wear and tear on the engine and want you to slam the brakes. The aircraft manufacturer would have their "recommended" training, and modify it in accordance to company practices / requirements, legal / regulatory frameworks etc. From what I understand, and this is just from reading the news and forums, there was no knowledge or training about the MCAS system. The closest thing is a runaway trim, and again this probably differs from airline to airline. All aircraft, pilots have a checklist of things - takeoff, landing, recovering from various undesirable aircraft states etc. Occasionally you do hit an edge case where a lack of knowledge and training collide with a background-running aircraft system acting out of the ordinary. Again - I'm just a private pilot so do take the above with a grain of salt, Airline Transport Pilots have far more training and experience, and can probably provide a far better insight to the behaviour of larger jets, difference between companies, SOP's etc.
- VBprogrammer 8y ago> - My first / immediate thought is that my previous action led to an undesired aircraft state. FYI This is shown in the Lion air preliminary report. They select flaps 0 (from flaps 5) and a few seconds later reselect flaps 5. Unfortunately a while after that they decide to go to flaps 0 again. With any flaps selected the MCAS system is disabled.
- js2 8y agoThis must have been mighty confusing without knowing about MCAS. It’s like trying to fly a black box instead of flying a plane.
- VBprogrammer 8y agoYeah, I can imagine. I mentioned elsewhere, the previous flight managed to develop a reasonable mental model (they thought that the Mach Trim System was responding to a wrong airspeed input). Saying that, failing to guess what's going wrong shouldn't result in a big hole in the ground. This is pretty interesting if you haven't seen it before: https://vimeo.com/159496346 https://vimeo.com/159496346
- fencepost 8y agoFor the curious, it's a presentation on "Automation Dependency" in flying, done by someone from American Airlines.