Originally posted by Evan
View Post
Announcement
Collapse
No announcement yet.
Sunwings Incident Writeup
Collapse
X
-
--- Judge what is said by the merits of what is said, not by the credentials of who said it. ---
--- Defend what you say with arguments, not by imposing your credentials ---
-
Originally posted by Gabriel View PostAnd most likely you are right not believing that. It's by far most likely NOT_what happened. Again, even crew with their head NOT_in the game and a NO_respect for procedure would NOT_make THE SAME error at the same time like that.
Comment
-
Originally posted by Evan View PostYour really not following me. If one pilot makes the error and the other just copies his data entries, this is bound to happen. That's what I sort of suspect happened here (see disclaimer).
Now, do you know what was the procedure that they were SUPPOSED to follow? Do you know if the procedure required them to make independent entries in the FMS and let the FMS compare? Do you even know if this particular version of the FMS and its software is even capable of that?
I am by no means discarding this possibility and I totally take it as a valid hypothesis. It is not the only plausible explanation though, and we don't even know if it is possible at this point. You cannot blame the pilots for not doing independent entries in the FMS and let the FMS compare if that was not what the procedure required, if that was not what they were trained to do, or if the FMS is not capable of such thing. Which I am not saying any of that is the case, but I cannot discard it either.
--- Judge what is said by the merits of what is said, not by the credentials of who said it. ---
--- Defend what you say with arguments, not by imposing your credentials ---
Comment
-
Originally posted by Gabriel View PostBlah, blah, blah, procedure, training, blah blah...
The reckless, improvisational, jack leg, monkey, cowboy pilots screwed up and must be shamed on discussion fora and physically punished...period.Les règles de l'aviation de base découragent de longues périodes de dur tirer vers le haut.
Comment
-
Originally posted by Gabriel View PostYou cannot blame the pilots for not doing independent entries in the FMS and let the FMS compare if that was not what the procedure required, if that was not what they were trained to do, or if the FMS is not capable of such thing.
Comment
-
Originally posted by 3WE View PostSlightly off topic- but I am wondering how you (and or Eric and or Schwartz) are going to design TOPMS to not take errant temperature entries (or other errant entries like weight) and correctly tell the pilots that the takeoff is progressing as it should (or shouldn't). Does TOPMS take it's own temperatures and calculate a nice, buffered takeoff and just give a yellow light that says you might want to go to 100% power...and then a red flashing one that says go to cook-the-engine-but-save-your-a$$ settings?
1) Reduce or eliminate all values selected by a pilot
2) Provide warnings or validations on bounds of expected values
3) Ensure that both pilots are forced to enter numbers independently, or one person having to do it twice DIFFERENTLY so they don't make the same mistake twice.
4) Make sure the context of the numbers on the screen are clear -- form design makes a difference, so at a glance or in a hurry, something out of whack is more likely to be noticed
Lots of strategies. I am guessing this old software was built like a spreadsheet with a long list of fields, little to no validation and no connection to actual measures. Given the number of times this software is used, even a small percentage will result in a good number of incidents.
Comment
Comment