A Comair flight carrying at least 50 people crashed a mile from the Blue Grass Airport in Lexington Sunday morning.
http://www.wcpo.com/news/2006/local/08/27/plane_crash.html
"Multiple fatalities"
A Comair flight carrying at least 50 people crashed a mile from the Blue Grass Airport in Lexington Sunday morning.
http://www.wcpo.com/news/2006/local/08/27/plane_crash.html
James_Dean said:*** Speculation Warning ***
Pure Speculation on my part. Did they try to take off on the wrong runway?
They closed 8/26 this morning
08/035 - 8/26 CLSD WIE UNTIL UFN
http://download.aopa.org/ustprocs/20060803/airport_diagrams/00697AD.PDF
26 is only 3500 feet, 22 is 7000 feet.
Can a fully loaded CRJ-100 get off the ground in only 3500 feet?
KLEX 271254Z 22007KT 7SM BKN050 BKN060 24/21 A3004
Sure, Adam, sureAdamZ said:Grrrrr just saw Mike posted the same thing in hangar talk. I looked for one I swear. Chuck can you merge this in with Mikes post?
Done.AdamZ said:Grrrrr just saw Mike posted the same thing in hangar talk. I looked for one I swear. Chuck can you merge this in with Mikes post?
They could have mistaked the markings, especially realizing the crew was tired. [Part of post removed]wsuffa said:22 and 26 are fairly close together on the departure end, but you can't really miss the markings. I hope this wasn't an attempt to save a bit of time on TO.
Tired? At 6 in the morning? When did they get there?HPNPilot1200 said:I think they may have mistaked the markings, especially realizing the crew was tired. The media (so take this like a grain of salt) has reported the crew was tired and from that, my own speculation would be that the crew taxiied to runway 26 and started their takeoff run. By the time the wheels were spinning and realized what they had done, they were already half-way down the runway and likely a few knots faster than stall speed, tried to get off, and somehow got themselves into a secondary stall.
Not sure, but it'll be interesting to find out how much rest they were given (the full 10 hours or not). Even with full rest, if they worked a full 14 hour day the previous day, you can still be pretty tired the next day and not fully on top of things.mikea said:Tired? At 6 in the morning? When did they get there?
Because they closed 26 this morning.SkyHog said:how are you getting the idea that it departed runway 26 instead of 22? I'm just curious
mikea said:Because they closed 26 this morning.
WCPO web site said:Families of the crash victims are asked to provide dental records, as the victims were all severely burned.
SkyHog said:Not only that, but the airplane is pretty much right off the end of runway 8. Sigh. I can't believe it, its a real shame for pilot error to cause such a loss of life.
Yet another reason to fly GA.
123456 said:I guess that the NTSB Go Team can be recalled since you have already reviewed all the data avaialble and reached the conclusion. Will your written report be available for distribution later today? Sheesh. Low time experts.
123456 said:I guess that the NTSB Go Team can be recalled since you have already reviewed all the data avaialble and reached the conclusion. Will your written report be available for distribution later today? Sheesh. Low time experts.
jangell said:I have had a few instances as I blaze down a "runway" where I wonder if I'll actually lift off before the end...I'm sure I'm not the only one who has been in this situation...Ugh.
The problem is quite often there really is no good abort point. The point in which you lift off from the runway does not have adequate room to abort takeoff and come to a stop without bending metal. You are committed to a takeoff. If your engine quits it's game over. Also it's really hard to take book numbers and relate them to runways that may be rough, wet, high grass...etc.. There are just too many variables.wsuffa said:Run the numbers. And pick an abort point. If you're used to flying out of long runways, the ground and trees can look awfully close on the first few times out of a short field.
Unfortunately, fields like 6Y9 don't offer that ability (for my Cherokee at least). To pick a safe abort point would mean never lifting off.wsuffa said:Run the numbers. And pick an abort point. If you're used to flying out of long runways, the ground and trees can look awfully close on the first few times out of a short field.
123456 said:I guess that the NTSB Go Team can be recalled since you have already reviewed all the data avaialble and reached the conclusion. Will your written report be available for distribution later today? Sheesh. Low time experts.
SkyHog said:Unfortunately, fields like 6Y9 don't offer that ability (for my Cherokee at least). To pick a safe abort point would mean never lifting off.
AdamZ said:Reports ( keep in mind this is the news, sigh) indicated the plane ( don't know the type) took off of the wrong runway a 3700' runway and it was supposed to take off of a 7000'+ runway.
jangell said:The problem is quite often there really is no good abort point. The point in which you lift off from the runway does not have adequate room to abort takeoff and come to a stop without bending metal. You are committed to a takeoff. If your engine quits it's game over. Also it's really hard to take book numbers and relate them to runways that may be rough, wet, high grass...etc.. There are just too many variables.