37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 289423 |
Time | |
Date | 199411 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : stl |
State Reference | MO |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | ATR 42 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 270 flight time total : 20000 flight time type : 5400 |
ASRS Report | 289423 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | incursion : runway non adherence : far non adherence : clearance |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : exited adverse environment |
Consequence | faa : investigated |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Situations | |
ATC Facility | procedure or policy : unspecified |
Narrative:
Landing runway 24 to hold short of runway 30L. First officer flying landed long but stopped short of runway 30L. Very poor and somewhat nonexistent markings (night) for hold short or to establish location on runway 24. Slightly disoriented as to exact position on runway 24. Thought controller said 'turn left and hold short of runway 30L.' in my mind, I thought we must be short of ctrfield taxiway P and started taxi to taxiway P to turn left and then contact ground for hold short of runway 30L. However, immediately after starting taxi, realized we were entering runway 30L. Only traffic was L-1011 that had already rolled out was already in turnoff of runway 30L at echo. Only action was to expedite crossing and get off runway. Lighting confusing. Only hold short marking is line on runway 24 that cannot be seen at night. I feel this maneuver is unsafe at night and this will occur again. Callback conversation with reporter revealed the following: reporter states there is no question that they held short of runway 30L but were very disoriented by the multitude of lights in the area. Under the old regulations there was no ability to give a hold short of crossing runway clearance. When the FAA change occurred the requirement was to hold short at least 200 ft from the intersecting runway. A line was painted across the runway at that point. May be great in the daytime, but at night it is impossible to see this line. That is why reporter thought he was further back on the runway. What he thought was a taxiway turned into a runway. Tower supervisor is in agreement that there should be no hold short of crossing runway at night. Reporter and many other company pilots are very concerned regarding the problem and now refuse the accept such a clearance. FAA has sent a 10 day letter and reporter has sought legal assistance.
Original NASA ASRS Text
Title: TAXIING OFF RWY AFTER LNDG FLC BECOMES DISORIENTED AND ENTERS ACTIVE RWY.
Narrative: LNDG RWY 24 TO HOLD SHORT OF RWY 30L. FO FLYING LANDED LONG BUT STOPPED SHORT OF RWY 30L. VERY POOR AND SOMEWHAT NONEXISTENT MARKINGS (NIGHT) FOR HOLD SHORT OR TO ESTABLISH LOCATION ON RWY 24. SLIGHTLY DISORIENTED AS TO EXACT POS ON RWY 24. THOUGHT CTLR SAID 'TURN L AND HOLD SHORT OF RWY 30L.' IN MY MIND, I THOUGHT WE MUST BE SHORT OF CTRFIELD TXWY P AND STARTED TAXI TO TXWY P TO TURN L AND THEN CONTACT GND FOR HOLD SHORT OF RWY 30L. HOWEVER, IMMEDIATELY AFTER STARTING TAXI, REALIZED WE WERE ENTERING RWY 30L. ONLY TFC WAS L-1011 THAT HAD ALREADY ROLLED OUT WAS ALREADY IN TURNOFF OF RWY 30L AT ECHO. ONLY ACTION WAS TO EXPEDITE XING AND GET OFF RWY. LIGHTING CONFUSING. ONLY HOLD SHORT MARKING IS LINE ON RWY 24 THAT CANNOT BE SEEN AT NIGHT. I FEEL THIS MANEUVER IS UNSAFE AT NIGHT AND THIS WILL OCCUR AGAIN. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: RPTR STATES THERE IS NO QUESTION THAT THEY HELD SHORT OF RWY 30L BUT WERE VERY DISORIENTED BY THE MULTITUDE OF LIGHTS IN THE AREA. UNDER THE OLD REGS THERE WAS NO ABILITY TO GIVE A HOLD SHORT OF XING RWY CLRNC. WHEN THE FAA CHANGE OCCURRED THE REQUIREMENT WAS TO HOLD SHORT AT LEAST 200 FT FROM THE INTERSECTING RWY. A LINE WAS PAINTED ACROSS THE RWY AT THAT POINT. MAY BE GREAT IN THE DAYTIME, BUT AT NIGHT IT IS IMPOSSIBLE TO SEE THIS LINE. THAT IS WHY RPTR THOUGHT HE WAS FURTHER BACK ON THE RWY. WHAT HE THOUGHT WAS A TXWY TURNED INTO A RWY. TWR SUPVR IS IN AGREEMENT THAT THERE SHOULD BE NO HOLD SHORT OF XING RWY AT NIGHT. RPTR AND MANY OTHER COMPANY PLTS ARE VERY CONCERNED REGARDING THE PROB AND NOW REFUSE THE ACCEPT SUCH A CLRNC. FAA HAS SENT A 10 DAY LETTER AND RPTR HAS SOUGHT LEGAL ASSISTANCE.
Data retrieved from NASA's ASRS site as of July 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.