Quote:
Originally Posted by Alamo
I work very close to Den Haag...seems an odd place for you guys to stay at, right? Amsterdam would be a lot more logical. Any observations, stories or other stuff about Schiphol that you care to share? I guess you heard about the event of Turkish Airlines, that basically stalled on approach to landing, killed 9 I think7? What happened there?
Reference: http://en.wikipedia.org/wiki/Turkish...es_Flight_1951
I have no interesting stories about Schiphol...my flights in there have been uneventful. I hadn't heard about this Turkish Airlines accident. From what I read in the Wikipedia article, it's easy to see what happened. A coupled approach (i.e. on autopilot) will result in an autoland if the autopilot is not disconnected. Part of the autoland is to ****** the throttle to idle and transition to a landing attitude (i.e. nose up).
Of course, it's the altitude which determines when these things happen. So if the Radio Altimeter is malfunctioning (as it was for this flight) you can have these very critical events happening at a bad time. If the crew is monitoring the PFD (Primary Flight Display) and engine instruments, as they should be doing throughout a couple approach, this wouldn't matter as they could take corrective action well before it became critical.
Quote:
On a sidenote...it seems almost disrespectful to point out all these accidents to you, as if there is not much more to what you do than avoiding accidents. Please don't be taken aback by this, us groundpeople are in total awe of what you do, but the best we (or at least, myself) can come up with is all the things that can go wrong, or went wrong.
Let's face it, everyone's primary concern when flying is safety, so it's not surprising that accidents are of interest to frequent flyers. We all want to have explanations so that we can feel better about the inherent safety of this mode of transportation.
It's always a little disturbing when it comes down to simple pilot error (whether negligence or lack of ability or knowledge). Usually there's a lengthy "error chain" leading to any accident and we go to great lengths in our training and procedures to minimize the potential for human oversight or mistakes that add to that chain. A big part of that is the crew concept. A saying I heard a long time ago, and one I really like, is that "it's not a mistake unless we both make it."
That's why, for example, we're extremely anal about things like altitude changes. When ATC issues a new altitude, the non-flying pilot reads it back to ATC. The flying pilot sets it on the MCP (Mode Control Panel). And then
both pilots physically point at it and announce the new altitude. Then, when we're within 1000' of the new altitude, both pilots say aloud, "Thirteen for fourteen thousand" (for example). Almost sounds silly, but altitude busts are extremely serious.
Quote:
One thing I have always wondered about, is it basic part of training/policy to inform the passengers what is going on during the flight? I recall one flight from Cyprus to Amsterdam where we had turbulence for the full 4 hours of flight. Pilot came on the PA to tell the crew to sit down and strap in. Many white noses, let me tell you. But he would have done such a tremendous job (on a moral/human interest level) to tell the passengers it was gonna be a bumpy ride, unpleasant even, however, all was under control.
It seems such a small effort for a thing that can have such a tremendously positive effect?
Though this is included in our training, the level of communication with passengers becomes a very individual thing. The company even goes to the trouble to provide some sample PAs for us to use in certain situations but I can count on one hand the number of times I've seen a pilot use this reference.
In sim training, any time we have an emergency the instructor wants to hear the crew annunciate their intention to notify the FAs, make a PA, call dispatch to inform them of the emergency and, lastly of course, to notify ATC. We simplify this during sim training as "2 in and 2 out" (the 2 in are the FAs and pax; the 2 out are company and ATC). So, what you see in training is: engine failure; fly the plane; secure the engine; run the emergency checklist; "2 in and 2 out"; etc etc. No one wants to waste $1000/hour sim time with a 10 minute PA and FA brief, so we just use the phrase and that lets the instructor/examine know that we're aware of the need for this.
My point is: no one really hones this skill in training. So in the real world, some guys are good about it and some aren't. Even those who have the good intentions may not be very good at extemporaneous speaking and so they tend to avoid the unpleasant task...human nature.
I flew the Delta Shuttle on the MD-88 for a few years and whenever we were delayed I made a point of keeping the passengers up to date. I didn't bs them and I usually told them that we are also frustrated with delays and that I would pass any information I had on to them as it became available. I think that's all anyone really wants.
I was recently commuting on a Comair flight home from JFK and after pushback we just stopped. 10 minutes went by with not a word from up front so I finally called the flight attendant and asked her to suggest to the crew that a PA would be nice. They made a PA within a minute of that and maybe they resented my suggestion...I hope not, but to me it seems such a simple thing to do that can pay such dividends in customer satisfaction.
Last edited by W0X0F; 01-07-2010 at 11:00 PM.
Reason: ...and that's the answer in 2500 words or less.