Technical question
What was that 35 second delay all about when they were showing the simulations? I didn't understand it.
shareWhat was that 35 second delay all about when they were showing the simulations? I didn't understand it.
shareBasically Sully was saying that the simulations were BS because as soon as the birds hit the simulations went right for the airport, there are checks & calls to the airflight control that were never done in the sims
shareYeah, they basically took 30 sec to say "What the hell happened? The engines haven't really shut down, have they?".
And if you've ever had to handle a real emergency, you'd realize that grasping the scope of the problem within 30 sec is pretty good. So yeah, the simulations we're BS as they didn't allow time to figure out what the hell was going on.
Yup... and if the delay had been set closer to what they experienced they would have crashed somewhere in Manhattan like Sully imagines thought the movie.
shareFor a trained professional where something can be grasped in the context of what they are already trained for, 30 seconds can be a very long time. Sully's point was good, and not over-exaggerated. It shows how a lot of critics can sometimes not have any idea what they are talking about. Talk is easy, but in this case, results cannot be argued with.
Perhaps what they could have done to be even more realistic was to try different intervals to see just how much time what the panel recommended would have needed and them back-figured to see if there would have been time to plot a workable landing scenario.
Perhaps it's like hitting the brakes in a car when a road hazard appears.
There's always a one second delay or whatever while the brain registers it and gets the body to react. All a driver does is hit the brakes. With all those people in the back and a lot of instruments to read on multiple engines (which may still be indicating some fuel flow and power generation), the decision time before a major action is a lot longer.