Snoozing Pilot Mistakes Venus For Aircraft; Panic, Injuries Ensue 307
Cazekiel writes "In January 2011, an Air Canada Boeing 767 carrying 95 passengers and eight crew members was on route to Zurich from Toronto when its First Officer, fatigued and disoriented from a long nap he'd taken, panicked in seeing what he believed to be a U.S. cargo plane on a collision course with his aircraft. The panicking F.O. pushed forward on the control column to make a rapid descent. Only, it wasn't an aircraft he'd been looking at, but Venus. According to the article: 'The airliner dropped about 400 feet before the captain pulled back on the control column. Fourteen passengers and two crew were hurt, and seven needed hospital treatment. None were wearing seat belts, even though the seat-belt sign was on.' The only danger in this situation had been the F.O. napping for 75 minutes instead of the maximum 40, as the disorientation and confusion stemming from deeper sleep was the culprit in this mix-up. However, the Air Canada Pilots Association, 'has long pressured authorities to take the stresses of night flying into account when setting the maximum hours a pilot can work,' taking into account that North Atlantic night-flights are hardest on an already-fatigued pilot."
radar... (Score:2, Insightful)
Is this a bad thing? (Score:5, Insightful)
Personally, I'd prefer my pilots to take evasive action when they feel its neccessary, and not pick up a habit of second guessing themselves to avoid bad PR. Yes, passengers were injured, but TFA notes that the seatbelt light was on.
I read tfa and Im still not sure what happened (Score:4, Insightful)
It sounds like the FO was napping, woke up and immediately put the plane into a dive based on a snap judgement, and the Captian (who we presume was not flying the plane or manning the controls) recognized the error and corrected.
It sounded like nobody was flying the plan (autopilot presumably), but that the FO, who was napping, was actually on the controls. It sounds more like a problem with pilots sleeping while they should be awake and alert. The article was so light it was impossible to actually tell, through.
Re:Is this a bad thing? (Score:5, Insightful)
Yes it's a bad thing for pilots to sleep longer than they're supposed to because they're overworked, then panic because they just woke up from deep sleep and so can't tell the difference between an airplane and a planet despite being well experienced to tell the difference when awake.
The problem isn't that when the pilot thought he was about to hit another aircraft he took an evasive maneuver.
The problem is the circumstances that resulted in him mistaking Venus for an aircraft he was about to crash into.
What if his evasive actions had caused him to crash into an actual airplane that was at a lower altitude which he didn't notice because, again, he'd just woken from a deep sleep?
The whole point is that his judgment was temporarily impaired because he was fucking groggy, and you're asking "is this a bad thing?" Yes! Yes it is!
Re:Is this a bad thing? (Score:5, Insightful)
Personally, I'd prefer my pilots to take evasive action when they feel its neccessary, and not pick up a habit of second guessing themselves to avoid bad PR. Yes, passengers were injured, but TFA notes that the seatbelt light was on.
"However, the Air Canada Pilots Association, 'has long pressured authorities to take the stresses of night flying into account when setting the maximum hours a pilot can work,' taking into account that North Atlantic night-flights are hardest on an already-fatigued pilot."
Personally, I'd prefer my safety authorities actually listen to the men and women doing the damn job, and realize they could have likely prevented this from happening in the first place.
Re:Shame they don't have cabin video (Score:5, Insightful)
No video, but some nice photos at page 189-190 of http://www.atsb.gov.au/media/3532398/ao2008070.pdf [atsb.gov.au] (5.6MB)