http://uk.news.yahoo.com/5/20091023/tod-ar...by-870a197.html
Bet some Bozo tells the media and they will make a right ho-ho out of really nothing
Full Version: Arguing Pilots Miss Tod
QUOTE
When professional pilots act like amateurs.
Maybe we should be glad they weren’t texting while flying.
But how comforting is it to learn that two Northwest Airlines pilots flew right by their destination last week because they were on their laptops messing with their schedules?
Earth to the crew of Flight 188?
Aren’t the pilots supposed to be flying the plane?
Somehow, it seems this is not what flight attendants mean when they warn that electronic devices will interfere with communications.
On the way from San Diego to Minneapolis on Oct. 21, the flight crew was out of contact for more than an hour, which is what you might expect if a flight is in trouble.
The trouble was that Capt. Timothy B. Cheney, 53, and First Officer Richard Cole, 54, were violating company policy by using their laptops during the flight and were too distracted to notice that Northwest dispatchers were trying to reach them.
The National Transportation Safety Board reported Monday that "the pilots said there was a concentrated period of discussion where they did not monitor the airplane or calls from [the control tower] even though both stated they heard conversation on the radio."
Flight 188 flew 150 miles past its destination, the NTSB reported, and "neither pilot was aware of the airplane’s position until a flight attendant called about five minutes before they were scheduled to land and asked what was their estimated time of arrival."
With the lives of 144 passengers and three other crew members in their hands at 37,000 feet, you’d think that responsible adults would do their jobs and save personal business for personal time.
The traveling public wants to believe that transportation professionals are just that. But there’s plenty to shake that confidence.
Remember the tourist helicopter and Piper airplane that crashed over the Hudson River in August?
An air traffic controller who initially was responsible for the Piper apparently was on an inappropriate personal call when the crash occurred; his supervisor wasn’t even in the building as required, CNN reported this month.
Nine people died in that crash. The Federal Aviation Administration hasn’t faulted the controllers’ improprieties for the accident, but who can feel good knowing that controllers aren’t paying attention when they’re supposed to?
In 2008, a Metrolink engineer who plowed his commuter train into a Union Pacific freight train in California was having texting conversations on duty and was planning to have unauthorized guests in the cab, the Los Angeles Times reported. Twenty-four passengers and the engineer died, and 135 people were hurt.
The investigation also revealed that the freight train conductor had used his cellphone repeatedly the day of the crash and tested positive for marijuana, according to the Times.
After the Hudson River collision, an NTSB official spoke about "complacency and inattention to duty."
The traveling public should be asking whether companies to which we pay a pretty penny to get us from here to there appreciate their responsibility for ensuring safety.
Only in the movies and on the computer screen are planes, trains and automobiles just a game.
Maybe we should be glad they weren’t texting while flying.
But how comforting is it to learn that two Northwest Airlines pilots flew right by their destination last week because they were on their laptops messing with their schedules?
Earth to the crew of Flight 188?
Aren’t the pilots supposed to be flying the plane?
Somehow, it seems this is not what flight attendants mean when they warn that electronic devices will interfere with communications.
On the way from San Diego to Minneapolis on Oct. 21, the flight crew was out of contact for more than an hour, which is what you might expect if a flight is in trouble.
The trouble was that Capt. Timothy B. Cheney, 53, and First Officer Richard Cole, 54, were violating company policy by using their laptops during the flight and were too distracted to notice that Northwest dispatchers were trying to reach them.
The National Transportation Safety Board reported Monday that "the pilots said there was a concentrated period of discussion where they did not monitor the airplane or calls from [the control tower] even though both stated they heard conversation on the radio."
Flight 188 flew 150 miles past its destination, the NTSB reported, and "neither pilot was aware of the airplane’s position until a flight attendant called about five minutes before they were scheduled to land and asked what was their estimated time of arrival."
With the lives of 144 passengers and three other crew members in their hands at 37,000 feet, you’d think that responsible adults would do their jobs and save personal business for personal time.
The traveling public wants to believe that transportation professionals are just that. But there’s plenty to shake that confidence.
Remember the tourist helicopter and Piper airplane that crashed over the Hudson River in August?
An air traffic controller who initially was responsible for the Piper apparently was on an inappropriate personal call when the crash occurred; his supervisor wasn’t even in the building as required, CNN reported this month.
Nine people died in that crash. The Federal Aviation Administration hasn’t faulted the controllers’ improprieties for the accident, but who can feel good knowing that controllers aren’t paying attention when they’re supposed to?
In 2008, a Metrolink engineer who plowed his commuter train into a Union Pacific freight train in California was having texting conversations on duty and was planning to have unauthorized guests in the cab, the Los Angeles Times reported. Twenty-four passengers and the engineer died, and 135 people were hurt.
The investigation also revealed that the freight train conductor had used his cellphone repeatedly the day of the crash and tested positive for marijuana, according to the Times.
After the Hudson River collision, an NTSB official spoke about "complacency and inattention to duty."
The traveling public should be asking whether companies to which we pay a pretty penny to get us from here to there appreciate their responsibility for ensuring safety.
Only in the movies and on the computer screen are planes, trains and automobiles just a game.
http://www.star-telegram.com/242/story/1715931.html
You sched guys and gals have any thoughts here? As a corporate dog, I'm at a loss. I usually am in such a rush to visit the boy's room or the nearest lunch counter at my destination, its never been an issue.
How does this stuff even happen?
How does this stuff even happen?
QUOTE(bernoulli @ Oct 29 2009, 05:52 AM) 
You sched guys and gals have any thoughts here? As a corporate dog, I'm at a loss. I usually am in such a rush to visit the boy's room or the nearest lunch counter at my destination, its never been an issue.
How does this stuff even happen?
How does this stuff even happen?
Bernoulli - You are for real man !
QUOTE(bernoulli @ Oct 28 2009, 09:52 PM)
You sched guys and gals have any thoughts here? As a corporate dog, I'm at a loss. I usually am in such a rush to visit the boy's room or the nearest lunch counter at my destination, its never been an issue.
How does this stuff even happen?
How does this stuff even happen?
I've missed a reporting point over the Atlantic by 4- 5 minutes or so during dark and quiet long nights in total VHF silence. Usually by the 5 minute mark somebody catches it ( the other pilot , ATC through SELCAL or simply the inner clock ) but the last hour before the destination usually becomes very exciting and even hectic preparing yourself as well as the plane and galley for the landing. A lot of times all the coffee, juices and waters you've consumed during the last 7 hours or so has to be "dumped" just before landing causing the " gotta go right now" syndrome.
So, sched guys with similar issues.
QUOTE(trijetflyermd11 @ Oct 30 2009, 06:08 AM)
I've missed a reporting point...
Done the same, but in a slow King Air over the Gulf of Mexico. Of course, all we had on board was DC-3 era avionics. The good thing was that there is no radar coverage to "grade" me.
Does the A320 have any such thing as a VNAV alarm? Even in the planes I fly now with all this GPS technology, VNAV tells me when to start a descent when programmed with the rate of descent I'm planning. But, I have to frequently spot check it to know when to make my descent request. I would think that any Airbus variety would offer a means, avionics wise, to let the crew know that, "1. You're flying to Minneapolis, you're at FL350 and you'd like to descend at 2000 FPM, so I'll let you know when that scenario happens. 2. You then work with ATC to make it happen. Give or take."
Apparently not. Or the crew didn't employ it.
This VNAV technology is nice, but I am still mostly using my old-school means of starting down. Simple math. But that VNAV function has me slowly, but surely moving into relying on it. Always works out, depending on the runway. Makes for a good cross-check option.
Still wish I had an option for a lav, and/or galley that you sched folks have...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.