|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||atc facility : bna|
|Altitude||agl bound lower : 0|
agl bound upper : 0
|Operator||general aviation : corporate|
|Make Model Name||Light Transport, Low Wing, 2 Turbojet Eng|
|Flight Phase||ground other : taxi|
|Function||instruction : trainee|
|Qualification||pilot : atp|
pilot : cfi
|Experience||flight time last 90 days : 75|
flight time total : 8000
flight time type : 2
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
|Anomaly||incursion : runway|
other anomaly other
|Independent Detector||other controllera|
|Resolutory Action||none taken : detected after the fact|
|Consequence||faa : investigated|
|Air Traffic Incident||Pilot Deviation|
|Airport||other physical facility|
No passenger on board, taxiing northwest on taxiway charlie to runway for takeoff, alleged that the runway 20L/2R runway overrun at taxiway charlie was unintentionally crossed west/O authorization. Runway end and overrun were not clearly designated and were not readily identifiable from the cockpit to a pilot familiar or unfamiliar with the airport. The current nos and airport diagrams are also unclear as to the nature of the intersection. A rep of the local flight standards office has indicated a similar incident occurs at this specific location approximately 3 times per week and he has been trying to get a warning sign put up. Aviation safety is everyone's primary concern. While there were no other aircraft involved in this alleged incident, as a former part 141 chief flight instructor and accident prevention counselor, I am acutely aware of the potential hazards created by garbled or misunderstood communications, distrs and unclear or confusing signage on airports. Callback conversation with reporter revealed the following: reporter feels this incident was being used to get some local action. Controller made no comment to crew at time. FSDO made contact later. FAA administrator is said to have made same mistake at this intersection previous week. Reporter's first time in a jet, being checked out. Had many distrs just trying to learn instruments and technique of taxiing aircraft. 2 days after incident, holding lines were painted, signs were installed.
Original NASA ASRS Text
Title: TAXI ACROSS RWY OVERRUN.
Narrative: NO PAX ON BOARD, TAXIING NW ON TXWY CHARLIE TO RWY FOR TKOF, ALLEGED THAT THE RWY 20L/2R RWY OVERRUN AT TXWY CHARLIE WAS UNINTENTIONALLY CROSSED W/O AUTHORIZATION. RWY END AND OVERRUN WERE NOT CLEARLY DESIGNATED AND WERE NOT READILY IDENTIFIABLE FROM THE COCKPIT TO A PLT FAMILIAR OR UNFAMILIAR WITH THE ARPT. THE CURRENT NOS AND ARPT DIAGRAMS ARE ALSO UNCLEAR AS TO THE NATURE OF THE INTXN. A REP OF THE LCL FLT STANDARDS OFFICE HAS INDICATED A SIMILAR INCIDENT OCCURS AT THIS SPECIFIC LOCATION APPROX 3 TIMES PER WK AND HE HAS BEEN TRYING TO GET A WARNING SIGN PUT UP. AVIATION SAFETY IS EVERYONE'S PRIMARY CONCERN. WHILE THERE WERE NO OTHER ACFT INVOLVED IN THIS ALLEGED INCIDENT, AS A FORMER PART 141 CHIEF FLT INSTRUCTOR AND ACCIDENT PREVENTION COUNSELOR, I AM ACUTELY AWARE OF THE POTENTIAL HAZARDS CREATED BY GARBLED OR MISUNDERSTOOD COMS, DISTRS AND UNCLEAR OR CONFUSING SIGNAGE ON ARPTS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR FEELS THIS INCIDENT WAS BEING USED TO GET SOME LCL ACTION. CTLR MADE NO COMMENT TO CREW AT TIME. FSDO MADE CONTACT LATER. FAA ADMINISTRATOR IS SAID TO HAVE MADE SAME MISTAKE AT THIS INTXN PREVIOUS WK. RPTR'S FIRST TIME IN A JET, BEING CHKED OUT. HAD MANY DISTRS JUST TRYING TO LEARN INSTRUMENTS AND TECHNIQUE OF TAXIING ACFT. 2 DAYS AFTER INCIDENT, HOLDING LINES WERE PAINTED, SIGNS WERE INSTALLED.
Data retrieved from NASA's ASRS site as of August 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.