Ron Lee wrote:
FUBAR wrote:


Sound Familiar? Let's see!

What has the flying public found out so far about the
Kentucky tragedy?

We know FAA violated their own orders for minimal ATCT
staffing at this location. We know the Veteran controller
was being worked like a dog as many "Veteran and
experienced" controllers and technicians are. (While many
incompetent FAA employees who can't control traffic or
repair sophisticated equipment are promoted into Management
to meet diversity goals)

The controller just missed violating orders regarding sleep
requirements by one hour. We know staffing and funding in
the FAA for critical people like controllers and technicians
is cut short. (All while some contractors swim in FAA tax
gravy money treated like Kings and Queens)

.
Delleted fluff

Steven already covered the reasons why your view is flawed.
Bottom line is that there is ZERO evidence that the controller made
the pilots take off the wrong runway. The pilots alone are suspect
IMO. Taxiway painting, runway work, closed taxiway...etc are
irrelevant. They had one useable runway and they missed it.

Ron Lee


We won't learn much if we categorically state at this time that the
pilots were the only reason for the crash. Almost certainly their
actions will end up being the probable cause, but we have yet to know
about contribution factors; i.e., the Jeppesen and NACO charts show
different taxiway names. Was the signage up to snuff? Did the company
dispatcher do his/her part? Runway 26 shows on the airport diagrams as
being much narrower than 22, but this was done with paint; the physical
runway appears to be as wide as 22.

I do agree that the controller was almost certainly not a contributing
factor, except the NTSB might say he contributed to the slight extent
that he was not watching (even though he was not required to). This one
is sticky because there should have been two of them on duty. This can
end up being a contribution cause without the controller having failed
to do his job.