37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 807539 |
Time | |
Date | 200810 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : rap.airport |
State Reference | SD |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 5900 flight time type : 900 |
ASRS Report | 807539 |
Events | |
Anomaly | incursion : runway non adherence : clearance non adherence : far |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Chart Or Publication Flight Crew Human Performance |
Primary Problem | Chart Or Publication |
Narrative:
We landed from an ILS on runway 32 in rap. I'd briefed the runway length; approach light system and a left turnoff at the end or at one of the taxiways before; depending on braking and touchdown. Upon landing rollout; I executed a left turn as briefed; but instead of turning onto the taxiway I expected to see just after the crossing runway; I turned left onto the runway. The commercial chart taxiway diagram indicates a shaded area parallel to that runway (it looks like a taxiway on the diagram) just north of the crossing runway; and I thought I was turning onto that. Instead; I turned onto runway 23 and was chastised by tower. I apologized for my error; and we taxied to the gate without further incident. This problem arose due to the low visibility and inaccurate taxiway diagram; and a contributing factor was my error to recognize that I was turning onto a crossing runway; despite the lights and visual cues. No real excuse for the latter.
Original NASA ASRS Text
Title: AN ACR PILOT EXITED RAP RWY 32L ON TO RWY 5/23 MISTAKING THE RWY FOR A TXWY BECAUSE THE COMMERCIAL ARPT DIAGRAM SHADING INDICATES A TXWY ADJACENT TO THE RWY.
Narrative: WE LANDED FROM AN ILS ON RUNWAY 32 IN RAP. I'D BRIEFED THE RUNWAY LENGTH; APPROACH LIGHT SYSTEM AND A LEFT TURNOFF AT THE END OR AT ONE OF THE TAXIWAYS BEFORE; DEPENDING ON BRAKING AND TOUCHDOWN. UPON LANDING ROLLOUT; I EXECUTED A LEFT TURN AS BRIEFED; BUT INSTEAD OF TURNING ONTO THE TAXIWAY I EXPECTED TO SEE JUST AFTER THE CROSSING RUNWAY; I TURNED LEFT ONTO THE RUNWAY. THE COMMERCIAL CHART TAXIWAY DIAGRAM INDICATES A SHADED AREA PARALLEL TO THAT RUNWAY (IT LOOKS LIKE A TAXIWAY ON THE DIAGRAM) JUST NORTH OF THE CROSSING RUNWAY; AND I THOUGHT I WAS TURNING ONTO THAT. INSTEAD; I TURNED ONTO RUNWAY 23 AND WAS CHASTISED BY TOWER. I APOLOGIZED FOR MY ERROR; AND WE TAXIED TO THE GATE WITHOUT FURTHER INCIDENT. THIS PROBLEM AROSE DUE TO THE LOW VISIBILITY AND INACCURATE TAXIWAY DIAGRAM; AND A CONTRIBUTING FACTOR WAS MY ERROR TO RECOGNIZE THAT I WAS TURNING ONTO A CROSSING RUNWAY; DESPITE THE LIGHTS AND VISUAL CUES. NO REAL EXCUSE FOR THE LATTER.
Data retrieved from NASA's ASRS site as of May 2009 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.