Posted on 08/27/2006 4:38:10 AM PDT by BigBlueJon
Edited on 08/27/2006 5:02:21 AM PDT by Admin Moderator. [history]
Possible plane crash in Lexington, KY. My brother works security for Lexington UK Hospital and was just called in. No news locally or on major news outlets yet. I didn't want to post anything for fear of being wrong, but he's still waiting for an official call while on stand-by.
Update from WTVQ 36 Lexington:
A plane has crashed near the Blue Grass Airport this morning. No word on details at this time. We are told it was a commercial aircraft. Versailles Road is blocked as emergency vehicles circle around the site. We have live coverage beginning at 7:20am. Stay with Action News 36 for more details.
Comair: "Lexington Ground, Comair 191 ready to taxi with the ATIS information."
LEX: "Comair 191, Lexington Ground, taxi to runway 22."
Comair: "Taxi to runway 22, Comair 191."
Comair: "Lexington Tower, Comair 191 ready for departure at runway 22."
LEX: "Comair 191, Lexington Tower, fly runway heading (or another assigned heading), runway 22 cleared for takeoff."
Comair: "cleared for takeoff, runway heading, Comair 191."
Another great one was the way they mounted the LANTIRN pod. I'm still convinced that because it wasn't flush mounted on the LAU that it caused some significant Yaw moment in the landing configuration.
I left the fleet right before they put in the digital SAS. When they first fielded it you would get some massive wing rock whenever you got above 25 units AOA. When the pilots complained to NAVAIR the engineers response was "Why would you ever want to get slow in a fighter?" AAAAAAAAAAAAGGGHHHGGHHH!
Isn't there ANYBODY in these news orgs that knows a damn thing about flying??
The really stupid thing is that there are high resolution pictures of just about ever single commercial plane that is flying today posted on the internet. All they needed to to was negotiate a price from the photographer for a picture of the plane that crashed.
COEXERJ145 found a picture of the plane that probably was the one that crashed and posted a link to it. Below is a link to his post.
http://www.freerepublic.com/focus/news/1690739/posts?page=483#483
You say two-two... all the time, every time when talking about runways, headings, speeds, or altitudes. They have to repeat the info since this is a controlled airport. Really, I'm having trouble wrapping my finger around this one. The tower should've been all over this, as well. Despite the darkness, you should be able to easily see that the a/c is on the wrong runway. Awful, awful stuff.
That is what I would expect.
But the news report (by civilians so who know how badly they have screwed it up) said the conversation was
LEX: "(use) Runway 22"
Comair: "Roger."
Things that make you go Hmmmm....
Oh, I know :-) . I'm sure this discussion has been played up numerous times in airport break rooms everywhere.
Just hit refresh and it should load.
Anybody know the answer to this question. Are runway remaining markers required at all airfields? You would think that would have clued them in as well when they started rolling and the first one they saw said "3"
Bad phraseology also tends to happen a lot when traffic is light to nil. The fact that this happened at 6:00am on a Sunday does not give me a warm fuzzy...
The heading displayed in the EFIS displays in front of both pilots shows the runway that they are on via their heading.
Shouldn't the pilot have figured out he was on the wrong runway just by looking at his compass? Don't pilots have to know information about the airports they fly into?
No, unfortunately they're not. At TOL for example, we have runway distance remaining markers on our long runway, but not our short one.
BTW, kudos to Trace Gallagher on Fox for knowing how runway numbering works...
Forgive me, but your question is like asking me shouldn't I cook my hamburgers to well-done instead of rare.
The answers are all yes, but that don't mean it gets done.
If they were on 26 it would have been almost an incapable feat to hit V1, perhaps an abort was started and then realized that it was impossible to follow through.
You don't really do that unless you are assigned a different heading after takeoff. Large airports often have more than one runway on the same heading, so its futile exercise if you're trying to takeoff on 35R, your compass says 350, but you're cleared for takeoff on 35L.
There are plenty of signs indicating the runway you are turning onto. The controller should've probably saw something was amiss too.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.