Northwest jet overshoots Minneapolis airport
#22
Gets Weekends Off
Joined APC: Feb 2007
Position: FO
Posts: 3,031
I know most manuals say "no reading of non-company material" in the cockpit and I usually don't (most my legs are under 2 hours) , but something as simple as reading keeps your mind engaged and alert, especially on a long flight. I understand why the rule is there, for liability reasons. I doubt it will ever change, but I think a rule such as "Reading is allowed from 20 minutes after TOC to 20 minute before TOD" wouldn't compromise safety and keep crewmembers alert.
#23
When I was a controller in the AF at Eglin, we had a controller on the midnight shift fall asleep at the scope and never took a overflight handoff from PNA approach. That boy paid the price for that. It happens (falling asleep) everywhere unfortunately.
Hoser
Roll Tide!
#24
This stuff is all happening while management pushes for their precious SOC.
Hurry up. Faster. Quicker. Shortcut this. Finesse that. Time is money.
Listen to today's earnings call. SOC is all about revenue and "synergies".
Not a word about safety.
Maybe we should slow down just a bit.
Let's hope the FAA has not lost sight of the real purpose behind granting an airline operating certificate.
Hurry up. Faster. Quicker. Shortcut this. Finesse that. Time is money.
Listen to today's earnings call. SOC is all about revenue and "synergies".
Not a word about safety.
Maybe we should slow down just a bit.
Let's hope the FAA has not lost sight of the real purpose behind granting an airline operating certificate.
#25
#27
I'm going to be riding on this SAN-MSP flight in a few weeks. What eventually happened to the crew of the Mesa CRJ that fell asleep in Hawaii? We've definitely had people get dead out here on the left coast when they fell asleep and went out over the ocean.... Waking up when the motors ran out of gas.
Sounds like the crew of the ATL taxiway landing is covering for their buddy who was either in the jumpseat (unlikely) and watched/let it happen, or was supposed to be there, and now had a convenient reason why he wasn't.
Sounds like the crew of the ATL taxiway landing is covering for their buddy who was either in the jumpseat (unlikely) and watched/let it happen, or was supposed to be there, and now had a convenient reason why he wasn't.
Please elaborate on the bolded part of your post above. The way I read it, you're saying they invented the medical emergency after they realized 6 eyes let a 767 land on a taxiway. 2 of those eyes belonging to a Check Airman.
#28
New Hire
Joined APC: Oct 2009
Posts: 1
Here's an interview with a passenger. He reports the pilots had been making announcements. Also says the "dark suits" removed a "case" from the cockpit on landing.What might that have been?
#29
Banned
Joined APC: Feb 2008
Position: The Beginnings
Posts: 1,317
Just saw this on the WSJ. This blurb below is from the Minneapolis paper. The WSJ suggests the crew might of fallen alsleep. Here's the flightaware data too:
Northwest jet overshoots Minneapolis airport
Associated Press
Last update: October 22, 2009 - 2:46 PM
MINNEAPOLIS - Federal officials say a Northwest Airlines jet overflew the Minneapolis airport by 150 miles before crew members discovered their mistake. The plane landed safely Wednesday evening, and none of the 147 passengers and crew were injured. The National Transportation Safety Board says the Airbus A320 was flying from San Diego to Minneapolis and lost radio contact with controllers before 7 p.m. The NTSB says the jet flew about 150 miles past the Minneapolis airport before communications were re-established at 8:14 p.m. The Federal Aviation Administration says the crew told authorities they became distracted during a heated discussion over airline policy and lost track of where they were.
Northwest jet overshoots Minneapolis airport
Associated Press
Last update: October 22, 2009 - 2:46 PM
MINNEAPOLIS - Federal officials say a Northwest Airlines jet overflew the Minneapolis airport by 150 miles before crew members discovered their mistake. The plane landed safely Wednesday evening, and none of the 147 passengers and crew were injured. The National Transportation Safety Board says the Airbus A320 was flying from San Diego to Minneapolis and lost radio contact with controllers before 7 p.m. The NTSB says the jet flew about 150 miles past the Minneapolis airport before communications were re-established at 8:14 p.m. The Federal Aviation Administration says the crew told authorities they became distracted during a heated discussion over airline policy and lost track of where they were.
This one is pretty hard to defend on any level. If, in fact, this is actually what happened. I love the WSJ, but when it comes to aviation stories, I don't really believe anything I read in the newspapers.
#30
This stuff is all happening while management pushes for their precious SOC.
Hurry up. Faster. Quicker. Shortcut this. Finesse that. Time is money.
Listen to today's earnings call. SOC is all about revenue and "synergies".
Not a word about safety.
Maybe we should slow down just a bit.
Let's hope the FAA has not lost sight of the real purpose behind granting an airline operating certificate.
Hurry up. Faster. Quicker. Shortcut this. Finesse that. Time is money.
Listen to today's earnings call. SOC is all about revenue and "synergies".
Not a word about safety.
Maybe we should slow down just a bit.
Let's hope the FAA has not lost sight of the real purpose behind granting an airline operating certificate.
Thread
Thread Starter
Forum
Replies
Last Post