Replies

Wouldn't it be a shame...if it was something as simple as the Air Traffic controller NOT seeing that he was on the wrong runway..and didn't tell him to stop??

God Bless them all....

Wouldn't it be a shame...if it was something as simple as the Air Traffic controller NOT seeing that he was on the wrong runway..and didn't tell him to stop??

In the final analysis it's not their responsibility to ensure the pilot obeys instructions, although they (ATC) normally observe to see that they do. Could be reasons why he/she didn't or couldn't. From diagram of the airport, it looks like visibility should be good between the tower and the ends of 22 and 26. Unless the tower is so tall that they'd have to stand and lean over to look down far enough, but I wouldn't think so.

This scenario is unfortunately very likely. Most likely, this single controller was working not only the aircraft at LEX, but all of the aircraft up to 8,000 or 10,000 feet within 30 miles of LEX, which means his attention might have been directed toward coordinating something with Louisville approach or working some Cessna into Frankfort. Not an excuse for not watching his departure, but nonetheless a potential factor.

ATC does screw up time to time...but the final go/no-go decision rests with the pilot. And in this case, the controller cleared the aircraft for takeoff on the correct runway.

The thing that still gets me with this is the lights. Departure was at 6:07, but according to airnav.com, civil twilight wasn't until 6:38 and sunrise wasn't until 7:05...so it had to be DARK. And with runway 26 being unlit...we still have a lot to learn about this. And ATC might still get in trouble over any airport lighting issues.