Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

LEX Comair Crew on a nap/cdo/

  • Thread starter Thread starter pipi
  • Start date Start date
  • Watchers Watchers 58

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
Soverytired said:
Ah, another perfect pilot enters our midst.

By your "logic"

Pilots don't need EGPWS . . . we have altimeters and navs for positional awareness.

Pilots don't need gear warning horns . . . we have checklist.

Pilots don't need TCAS . . . . for that is the job of equally infallible ATC.

Pilots don't need runway incursion warning systems or hold short lighting at busy airports. . . .for we have paint on the pavement.

Pilots don't need Windshear warning systems . . . for we have weather reports and airspeed indicators.

Pilots don't need stall warning systems and shakers . . . for pilots would never fly below Vs 1.3.

Pilots don't need overspeed indicators . . . for we would never exceed a flap speed for VMO thanks to our airspeed indicators.
I would agree with every one of those statments. Thanks for making my point for me.
 
Last edited:
ReportCanoa said:
Correct. The only time I've seen the CDI lined up with the runway is on an off-the-runway RNAV DP out of Atlanta where the first path terminator is runway heading to an altitude.

777jackarse, you have been ignored.
Your wit is as fast as that electric scooter you use as your avatar
 
Last edited:
I have read only sections of this post. OMG! Are you_all really "reagional" pilots flying under the same crack head regs that I am? Because, there is a lot of strange comments out there about this accident. To me it reeks of fatigue, but that is my opinion. If you think it is human to fly these "regional" schedules and make good decisions, then fine,,, have a nice time. Also, you may try an iron man triathalon, sounds like that would suit you as well. The mistake these pilots made here was extraordinary, so maybe some of your thoughts should reflect that...
 
777_Jackpot said:
I would agree with every one of those statments. Thanks for making my point for me.
Yup... I agree...

Jerkpot is an A$$HOLE.

Next on the hit parade is YPF come to tell us what he does in YIP...

The best two on that list was:

Pilots don't need TCAS . . . . for that is the job of equally infallible ATC.
I have filed no fewer than 6 TCAS RA deviations in my career because ATC wasn't paying attention to what they were doing.

and,

Pilots don't need Windshear warning systems . . . for we have weather reports and airspeed indicators.
I have TWICE been in clear-air Windshear as annunciated by the Windshear alerting system a good 2-3 seconds before the ASI and VSI dropped out from under us. Both times the nearest cell was more than 10 miles away. Thanks to that software, I had an extra 2-3 seconds of engine spoolup that I wouldn't have otherwise had.

Jackpot, you have been officially b*tch slapped. You should know better, you pompous a$$.

Can't wait for the day people like you get your tit in a wringer and look back on this with rueful regret...

"There's two kinds: those that have and those that will". You can't escape the laws of probability... no matter HOW good you are.
 
Lear70 said:
Yup... I agree...

Jerkpot is an A$$HOLE.

Next on the hit parade is YPF come to tell us what he does in YIP...

The best two on that list was:


I have filed no fewer than 6 TCAS RA deviations in my career because ATC wasn't paying attention to what they were doing.

and,


I have TWICE been in clear-air Windshear as annunciated by the Windshear alerting system a good 2-3 seconds before the ASI and VSI dropped out from under us. Both times the nearest cell was more than 10 miles away. Thanks to that software, I had an extra 2-3 seconds of engine spoolup that I wouldn't have otherwise had.

Jackpot, you have been officially b*tch slapped. You should know better, you pompous a$$.

Can't wait for the day people like you get your tit in a wringer and look back on this with rueful regret...

"There's two kinds: those that have and those that will". You can't escape the laws of probability... no matter HOW good you are.

How many times did you launch down the wrong runway?
 
777_Jackpot said:
How many times did you launch down the wrong runway?
That is the issue of this thread.

That is NOT the issue we all have with YOU, Mr. Perfect.

I've started to enter / choose a wrong runway at least once or twice before either the runway heading, size, or some other external input (the F/O smacking me upside the head with the QRH) straightened me out.

The problem I have here is that YOU seem to have all the answers.

YOU seem to be perfect.

YOU are ready to be the pilots' judge, jury, and executioner WITHOUT knowing ALL the FACTS.

Here's a news flash, hotshot. NONE OF US have all the facts as of yet.

So before you get back on your high horse and bash the crew some more, why don't you sit back, relax, wait for the NTSB final report to come out and, in the meantime, have a nice hot cup of STFU.

mmmKay? :uzi:
 
Lear70 said:
I've started to enter / choose a wrong runway at least once or twice before either the runway heading, size, or some other external input (the F/O smacking me upside the head with the QRH) straightened me out.

There is a huge difference between entering the wrong runway and rolling down the wrong runway. My point, and excuse me if everyone has misunderstood me, is that the solution/prevention to similar situations, is NOT more automation, prevention systems, etc. Its doing what you get paid to do... be a pilot, and all of the duties included with the title, most notably... not fu*king up.
 
Lear70 said:
"There's two kinds: those that have and those that will". You can't escape the laws of probability... no matter HOW good you are.

Well said.

"There you are, fat as can be. The whole world is yours and you’re the answer to the Wright brothers’ prayers. You say to yourself, nothing can go wrong ... all my trespasses are forgiven. Best you not believe it." - Ernest K. Gann
 
acaTerry said:

acaTerry...

Your original point was to agree with the poster who said "maybe we should never fly early mornings". I said as long as there was adequate rest...and I explained this I meant they had been given time toc adjust their sleep schedule (pattern) prior to the event, then beginning duty early mornings meant nothing. Sun up, sun down, big deal. We're humans not vampires, and given opportunity and time, we can adjust and perform just fine.

I've seen the expert produced circadian rythmn studies. They are studies, not definitive absolutes of performance. They've been produced and updated and revised for years now. Is that the first one you've seen? Good helpful information, but I've also seen people brainwash themselves into thinking they couldn't function if they didn't meet exactly what the latest revision suggested. Kind of like health food nuts who feel like crap if they don't get granola every day at 7 AM. Circadian rythmn studies can also convince you that we should work only 5 hours duty days...something I agree with.

Getting up early to fly if you're well -rested....adequately rested... means you might be tired for awhile. This is not the same as fatigue, and the ONLY way to acertain if fatigue exists is to see what someone's done over a period of days. Your problem is you haven't read my posts. If you had you'd see that when I say "rested" I'm not talking about the paperwork, FAA minimum "legal" rest period.

Which is why you misunderstood my point about more accidents occuring at the end of a long duty day than the beginning after a "legal" rest. If a person is fatigued and gets "legal" rest (not adequate), they can still usually function to a fairly high degree soon after a period of sleep, but only for awhile. 14 hours later, however, that fatigued yet "legal" person is functioning well below standard. That's when fatigue-related accidents are most likely to occur, at the end of that long duty day, and why the NTSB goes back so many days to check what rest actually occured. It's the only indicator that fatigue may be present.

I don't need a job..I've had the same one for years. You obviously misunderstood again and I was referring to your "Three strikes and you're out" company and how much it sucked.

No thanks on the NJA thing despite your good fatigue policy. I love my current situation and no offense but your pay scale is brutal.
 
777 JACKPOT: The moral of this tragedy is not "Don't F#%k UP".
There are valuable lessons that will be learned from the sacrifice of people lives here.
First, that it was not a single error by the pilots, but rather the culmination of errors by the crew, the tower controller and a list of other things yet to be determined. This may lead to devices to detect when aircraft are on the wrong taxiway/runway and further improve avaiation safety. All of us fly, or have flown, GA aircraft with raw data and we know it's very safe. When it comes to the flying public, we are bound by professional ethics to incorporate all means available and necessary to ensure their safety. More preventive measures and technology will be put into place to help illiminate the possibilities of another accident like this, and the victims will not have perished in vain.
 
Last edited:
777_Jackpot said:
My point, and excuse me if everyone has misunderstood me, is that the solution/prevention to similar situations, is NOT more automation, prevention systems, etc. Its doing what you get paid to do... be a pilot, and all of the duties included with the title, most notably... not fu*king up.
If that was your point, you might have delivered it with a little less god-hood.

Otherwise, I agree with your statement, in certain less inflamatory terms.

At the end of the day, unless completely and totally snowed over by fatigue or being told incorrect data to where he / she doesn't know any better, it's the Captain's ultimate responsibility to be the show-stopper; the F/O shares a close 2nd responsibility as well - he's got a set of brakes, too.

We whine and b*tch all the time about how underpaid we are for the kind of risk we manage. We just proved that two of us, for WHATEVER reasons, didn't catch a fatal mistake and, therefore, didn't perform those duties and responsibilities that passengers entrust their lives to us to perform.

Do I think this could happen to any one of us on a bad day with a bad set of circumstances leading you down a bad path? You betcha. Would I welcome another addition in the electronic department to help? Absofreakinglutely! Does that relieve us of the moral responsibility to make sure, to the BEST of our ability, that it DOESN'T happen to us?

Absolutley NOT.

Use every resource, keep your situational awareness, don't get in a rush, screw the company's on-time performance in the face of safety. Period. I know all of you already do this anyway, but I like to remind myself from time to time as well.

-out-
 
CatYaaak said:
No thanks on the NJA thing despite your good fatigue policy. I love my current situation and no offense but your pay scale is brutal.

...should've seen it before the contract...

Anyway, I think you STILL misread the jist of my points. Try reading them like a book, not a personal attack on your disagreement with me. Perhaps if you spent some time at the regionals recently you'd see the point I and the other guys are making.
 
Lear70 said:
If that was your point, you might have delivered it with a little less god-hood.

Otherwise, I agree with your statement, in certain less inflamatory terms.

At the end of the day, unless completely and totally snowed over by fatigue or being told incorrect data to where he / she doesn't know any better, it's the Captain's ultimate responsibility to be the show-stopper; the F/O shares a close 2nd responsibility as well - he's got a set of brakes, too.

We whine and b*tch all the time about how underpaid we are for the kind of risk we manage. We just proved that two of us, for WHATEVER reasons, didn't catch a fatal mistake and, therefore, didn't perform those duties and responsibilities that passengers entrust their lives to us to perform.

Do I think this could happen to any one of us on a bad day with a bad set of circumstances leading you down a bad path? You betcha. Would I welcome another addition in the electronic department to help? Absofreakinglutely! Does that relieve us of the moral responsibility to make sure, to the BEST of our ability, that it DOESN'T happen to us?

Absolutley NOT.

Use every resource, keep your situational awareness, don't get in a rush, screw the company's on-time performance in the face of safety. Period. I know all of you already do this anyway, but I like to remind myself from time to time as well.

-out-


True words. Good post.
 
"Whenever we talk about a pilot who has been killed in a flying accident, we should all keep one thing in mind. He called upon the sum of all his knowledge and made a judgment. He believed in it so strongly that he knowingly bet his life on it. That his judgment was faulty is a tragedy, not stupidity. Every instructor, supervisor, and contemporary who ever spoke to him had an opportunity to influence his judgment, so a little bit of all of us goes with every pilot we lose."​
— author unknown,
R.I.P.​
 
This is a difficult time for the Comair family. While I am not an official spokesperson I know that all of us thank all of you that have expressed condolences.

With the help of the Creator, "we shall overcome."

In accordance with your individual beliefs we solicit your spiritual help for the speedy recovery of our stricken brother.

Thank you,

Surplus1
 
The latest and greatest news is that the controller was looking away and doing administrative duties. It also was a violation of policy to only have one controller on duty at a time.
Now I do not know about you guys but one contoller should be able to handle the 6 average nightly operations and serve whatever radar obligations are called for. Plus, when you only have 6 departures during you 8 hour shifts, seems reasonable to think you can acutally watch them depart.
None of this relieves the crew from noticing they were on an unlite runway on the wrong magnetic heading. I do not know if Comair uses go around mode for departure or sets departure heading but command bars would have been looking a bit strange. They screwed up but the controller who could of saved the day by watching his 6th operation of the night sure could have served them better.
 
Publishers said:
I do not know if Comair uses go around mode for departure or sets departure heading but command bars would have been looking a bit strange.

They wouldn't have looked strange at all. They would be commanding wings level, regardless of where the heading bug was set.
 
The problem is at that time of the morning, all 6 of those departures are getting ready to go at the same time. That means other clearances and taxi instructions need to be issued in a relatively short time span. As for the command bars on takeoff, they go into TO/TO mode and will point straight ahead, even if you aren't aligned with the heading bug.
 
ReportCanoa said:
They wouldn't have looked strange at all. They would be commanding wings level, regardless of where the heading bug was set.

That must be different than ours. On the ERJ, the command bars would show a turn on the ground if the hdg bug was significantly off.
 

Latest resources

Back
Top