37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 146527 |
Time | |
Date | 199005 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bwi |
State Reference | MD |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : corporate |
Make Model Name | Small Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : atp pilot : commercial |
Experience | flight time last 90 days : 120 flight time total : 27500 flight time type : 600 |
ASRS Report | 146527 |
Person 2 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 75 flight time total : 1900 flight time type : 390 |
ASRS Report | 146637 |
Events | |
Anomaly | incursion : runway |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
After landing, we turned off runway 10 at 'east' intersection (left turn off) and proceeded southeast on 'O'. We contacted ground and were cleared to general aviation. I had studied the airport diagram prior to landing and while taxiing I mistook runway 04/22 for taxiway 'O'. We entered the runway (which was notamed closed for landing traffic only) at 'P' intersection. At that point, ground instructed us to proceed on up the runway and clear at 'C' (the next available intersection), and proceed to general aviation. As we cleared the runway, I noticed an military small transport holding in position for a runway 22 departure. While this was the first time in 27 yrs that this has happened to me, I know of several other cases where it has happened. Of course, I did not see any markings on the taxiway, or I wouldn't have entered the runway. I feel the cause was due to a strange field and being unfamiliar with where I was or where I was going, except by the airport diagram. I feel like most airports are adequately marked; however, some aren't and perhaps that was contributory to my not noticing the runway markings.
Original NASA ASRS Text
Title: CPR TWIN JET MISSED TURN ON TXWY INADVERTENTLY TRANSGRESSED ACTIVE RWY.
Narrative: AFTER LNDG, WE TURNED OFF RWY 10 AT 'E' INTXN (L TURN OFF) AND PROCEEDED SE ON 'O'. WE CONTACTED GND AND WERE CLRED TO GENERAL AVIATION. I HAD STUDIED THE ARPT DIAGRAM PRIOR TO LNDG AND WHILE TAXIING I MISTOOK RWY 04/22 FOR TXWY 'O'. WE ENTERED THE RWY (WHICH WAS NOTAMED CLOSED FOR LNDG TFC ONLY) AT 'P' INTXN. AT THAT POINT, GND INSTRUCTED US TO PROCEED ON UP THE RWY AND CLR AT 'C' (THE NEXT AVAILABLE INTXN), AND PROCEED TO GENERAL AVIATION. AS WE CLRED THE RWY, I NOTICED AN MIL SMT HOLDING IN POS FOR A RWY 22 DEP. WHILE THIS WAS THE FIRST TIME IN 27 YRS THAT THIS HAS HAPPENED TO ME, I KNOW OF SEVERAL OTHER CASES WHERE IT HAS HAPPENED. OF COURSE, I DID NOT SEE ANY MARKINGS ON THE TXWY, OR I WOULDN'T HAVE ENTERED THE RWY. I FEEL THE CAUSE WAS DUE TO A STRANGE FIELD AND BEING UNFAMILIAR WITH WHERE I WAS OR WHERE I WAS GOING, EXCEPT BY THE ARPT DIAGRAM. I FEEL LIKE MOST ARPTS ARE ADEQUATELY MARKED; HOWEVER, SOME AREN'T AND PERHAPS THAT WAS CONTRIBUTORY TO MY NOT NOTICING THE RWY MARKINGS.
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.