37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 402599 |
Time | |
Date | 199805 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : phl |
State Reference | PA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Beech 1900 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : cfi pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 30 flight time total : 2100 flight time type : 100 |
ASRS Report | 402599 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | incursion : runway non adherence : far non adherence : clearance other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course flight crew : became reoriented |
Consequence | Other |
Supplementary | |
Primary Problem | Airport |
Air Traffic Incident | Pilot Deviation |
Situations | |
Airport | other physical facility |
Narrative:
Flight from phl to acy. The flight was running late due to the poor WX (heavy rain, winds and poor visibility at night). We exchanged crews and called for taxi. Both the captain and I were new to the area and were very unfamiliar with airport layout, especially taxiing to runway 9L. As we pulled out of our parking area following the airport diagram to runway 9L (this area is very poorly lit with no centerline taxi lights in this section), taxiway K makes a 'Y' and we proceeded to veer towards the right in the proper direction of runway 9L. However, we didn't veer sharp enough and ended up taxiing onto runway 9L. We immediately recognized our error and were able to take the immediate exit on taxiway left. We were merely on the runway for split seconds, with no other airplanes in or outbound on that runway at that time. Ground control didn't even notice we had deviated. Remainder of the taxi/flight was uneventful. Contributing factors: 1) unfamiliarity with airport. 2) poorly lit and marked area. 3) WX -- pools of water standing on taxiway, reflecting overhead lighting making it difficult if not almost impossible (with wind effects on standing water) to clearly identify taxiway/runway centerline/markings. Callback conversation with reporter revealed the following information: reporter was flying as first officer. Taxiing from taxiway east, their instructions were to turn right on taxiway K to runway 9L. During the turn onto taxiway K, there is a 'Y' intersection of taxiway K and taxiway K2. The area by taxiway K2 is poorly lit. Further confusion was caused by standing water on the taxiway. As the aircraft began its turn to the right, it stopped the turn early, the flight crew taxied onto runway 9L for a few seconds then immediately off the runway. The tower never said anything about the runway incursion, probably because of reduced visibility. Reporter stated that runway and taxiway lighting were poor only where the incursion took place, all the rest of the lighting was proper.
Original NASA ASRS Text
Title: A B1900 TAXIING FOR TKOF IS CONFUSED DURING TAXI AS TO WHICH PATH TO FOLLOW TO GET TO THE TKOF END OF THE RWY. FEW TXWY LIGHTS AT TXWY K WITH RAIN CAUSED THE CONFUSION. ACFT ENTERS ACTIVE RWY WITHOUT CLRNC AT PHL.
Narrative: FLT FROM PHL TO ACY. THE FLT WAS RUNNING LATE DUE TO THE POOR WX (HVY RAIN, WINDS AND POOR VISIBILITY AT NIGHT). WE EXCHANGED CREWS AND CALLED FOR TAXI. BOTH THE CAPT AND I WERE NEW TO THE AREA AND WERE VERY UNFAMILIAR WITH ARPT LAYOUT, ESPECIALLY TAXIING TO RWY 9L. AS WE PULLED OUT OF OUR PARKING AREA FOLLOWING THE ARPT DIAGRAM TO RWY 9L (THIS AREA IS VERY POORLY LIT WITH NO CTRLINE TAXI LIGHTS IN THIS SECTION), TXWY K MAKES A 'Y' AND WE PROCEEDED TO VEER TOWARDS THE R IN THE PROPER DIRECTION OF RWY 9L. HOWEVER, WE DIDN'T VEER SHARP ENOUGH AND ENDED UP TAXIING ONTO RWY 9L. WE IMMEDIATELY RECOGNIZED OUR ERROR AND WERE ABLE TO TAKE THE IMMEDIATE EXIT ON TXWY L. WE WERE MERELY ON THE RWY FOR SPLIT SECONDS, WITH NO OTHER AIRPLANES IN OR OUTBOUND ON THAT RWY AT THAT TIME. GND CTL DIDN'T EVEN NOTICE WE HAD DEVIATED. REMAINDER OF THE TAXI/FLT WAS UNEVENTFUL. CONTRIBUTING FACTORS: 1) UNFAMILIARITY WITH ARPT. 2) POORLY LIT AND MARKED AREA. 3) WX -- POOLS OF WATER STANDING ON TXWY, REFLECTING OVERHEAD LIGHTING MAKING IT DIFFICULT IF NOT ALMOST IMPOSSIBLE (WITH WIND EFFECTS ON STANDING WATER) TO CLRLY IDENT TXWY/RWY CTRLINE/MARKINGS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR WAS FLYING AS FO. TAXIING FROM TXWY E, THEIR INSTRUCTIONS WERE TO TURN R ON TXWY K TO RWY 9L. DURING THE TURN ONTO TXWY K, THERE IS A 'Y' INTXN OF TXWY K AND TXWY K2. THE AREA BY TXWY K2 IS POORLY LIT. FURTHER CONFUSION WAS CAUSED BY STANDING WATER ON THE TXWY. AS THE ACFT BEGAN ITS TURN TO THE R, IT STOPPED THE TURN EARLY, THE FLC TAXIED ONTO RWY 9L FOR A FEW SECONDS THEN IMMEDIATELY OFF THE RWY. THE TWR NEVER SAID ANYTHING ABOUT THE RWY INCURSION, PROBABLY BECAUSE OF REDUCED VISIBILITY. RPTR STATED THAT RWY AND TXWY LIGHTING WERE POOR ONLY WHERE THE INCURSION TOOK PLACE, ALL THE REST OF THE LIGHTING WAS PROPER.
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.