37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 402891 |
Time | |
Date | 199805 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : pit |
State Reference | PA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | Mixed |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : holding ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 6000 flight time type : 2000 |
ASRS Report | 402891 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 15000 flight time type : 3500 |
ASRS Report | 402894 |
Events | |
Anomaly | incursion : runway non adherence : clearance non adherence : far |
Independent Detector | other controllera other flight crewa |
Resolutory Action | flight crew : became reoriented none taken : insufficient time other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation other |
Situations | |
Airport | other physical facility |
Narrative:
After pushback from gate and contact with ATC ground control, we were informed that ZOB was not accepting departures for our direction of flight (presumably due to convective WX). A lengthy ground hold ensued while awaiting a rerted clearance. We were already well behind schedule due to a mechanical delay on the previous leg, followed by arrival holding due to thunderstorms at pit. We finally received our rerted clearance and were taxiing to runway 28C via taxiway V and taxiway east. I was pulling out en route charts to look up and verify our new route of flight (complete rerte). I was therefore unable to back up the captain as he taxied the aircraft. My eyes were 100% inside the aircraft, split cockpit duties. I felt safe doing this as we were clear of the congested area and the captain must have taxied this route thousands of times. Nevertheless, the captain failed to see the runway signs and rather than make a left turn on taxiway east, thought runway 28C was taxiway east. We were stopped from actually entering the runway by an alert ground controller. The captain is a very sharp pilot who is always on top of things. He told me he was expecting to see the sign for runway 28C, but never saw it so continued straight ahead. My head was down so I cannot verify, but I wonder if the sign was even illuminated. It was a dark and wet night, so visibility wasn't the best, but it was not actually raining at the time of the incident. I'm sure fatigue played a part as well. In the future I will always suspend other cockpit duties to monitor the captain as he approachs turn points which if missed could lead to a runway incursion. Factors: fatigue possibly, reduced visibility and split cockpit duties for sure, and possibly a sign that was not illuminated. Supplemental information from acn 402894: I was cleared to taxi via taxiway V and then left on taxiway east, but failed to see the runway marking signs. The runway and taxiway sign at pit are the new design lighted signs but were not obvious enough to command my attention. Upon returning to the same location the next day during daylight, I noticed that the taxiway at that intersection is very wide and the runway signs are farther than I expected from the taxiway centerline. I was focusing on the taxiway at the time of the incident due to the effect of 'tunnel vision' during a distraction or busy event, and that probably contributed to missing the signs. Pit has yellow lights on the taxiway ctrlines at many locations on the airport at potentially hazardous intxns, but not at this one that night. I feel this location on centerline is better for warning lights because when visibility is limited or restr, that is the area that gets the most attention, right in front of the aircraft where it is moving, not 100 ft or so off to the side.
Original NASA ASRS Text
Title: A TAXIING B737-200 FLC CROSSES AND STOPS OVER THE HOLD SHORT LINE FOR RWY 28C AT PIT. FO'S EYES WERE 'INSIDE' THE COCKPIT WORKING OUT A RERTE DURING THIS NIGHT FLT.
Narrative: AFTER PUSHBACK FROM GATE AND CONTACT WITH ATC GND CTL, WE WERE INFORMED THAT ZOB WAS NOT ACCEPTING DEPS FOR OUR DIRECTION OF FLT (PRESUMABLY DUE TO CONVECTIVE WX). A LENGTHY GND HOLD ENSUED WHILE AWAITING A RERTED CLRNC. WE WERE ALREADY WELL BEHIND SCHEDULE DUE TO A MECHANICAL DELAY ON THE PREVIOUS LEG, FOLLOWED BY ARR HOLDING DUE TO TSTMS AT PIT. WE FINALLY RECEIVED OUR RERTED CLRNC AND WERE TAXIING TO RWY 28C VIA TXWY V AND TXWY E. I WAS PULLING OUT ENRTE CHARTS TO LOOK UP AND VERIFY OUR NEW RTE OF FLT (COMPLETE RERTE). I WAS THEREFORE UNABLE TO BACK UP THE CAPT AS HE TAXIED THE ACFT. MY EYES WERE 100% INSIDE THE ACFT, SPLIT COCKPIT DUTIES. I FELT SAFE DOING THIS AS WE WERE CLR OF THE CONGESTED AREA AND THE CAPT MUST HAVE TAXIED THIS RTE THOUSANDS OF TIMES. NEVERTHELESS, THE CAPT FAILED TO SEE THE RWY SIGNS AND RATHER THAN MAKE A L TURN ON TXWY E, THOUGHT RWY 28C WAS TXWY E. WE WERE STOPPED FROM ACTUALLY ENTERING THE RWY BY AN ALERT GND CTLR. THE CAPT IS A VERY SHARP PLT WHO IS ALWAYS ON TOP OF THINGS. HE TOLD ME HE WAS EXPECTING TO SEE THE SIGN FOR RWY 28C, BUT NEVER SAW IT SO CONTINUED STRAIGHT AHEAD. MY HEAD WAS DOWN SO I CANNOT VERIFY, BUT I WONDER IF THE SIGN WAS EVEN ILLUMINATED. IT WAS A DARK AND WET NIGHT, SO VISIBILITY WASN'T THE BEST, BUT IT WAS NOT ACTUALLY RAINING AT THE TIME OF THE INCIDENT. I'M SURE FATIGUE PLAYED A PART AS WELL. IN THE FUTURE I WILL ALWAYS SUSPEND OTHER COCKPIT DUTIES TO MONITOR THE CAPT AS HE APCHS TURN POINTS WHICH IF MISSED COULD LEAD TO A RWY INCURSION. FACTORS: FATIGUE POSSIBLY, REDUCED VISIBILITY AND SPLIT COCKPIT DUTIES FOR SURE, AND POSSIBLY A SIGN THAT WAS NOT ILLUMINATED. SUPPLEMENTAL INFO FROM ACN 402894: I WAS CLRED TO TAXI VIA TXWY V AND THEN L ON TXWY E, BUT FAILED TO SEE THE RWY MARKING SIGNS. THE RWY AND TXWY SIGN AT PIT ARE THE NEW DESIGN LIGHTED SIGNS BUT WERE NOT OBVIOUS ENOUGH TO COMMAND MY ATTN. UPON RETURNING TO THE SAME LOCATION THE NEXT DAY DURING DAYLIGHT, I NOTICED THAT THE TXWY AT THAT INTXN IS VERY WIDE AND THE RWY SIGNS ARE FARTHER THAN I EXPECTED FROM THE TXWY CTRLINE. I WAS FOCUSING ON THE TXWY AT THE TIME OF THE INCIDENT DUE TO THE EFFECT OF 'TUNNEL VISION' DURING A DISTR OR BUSY EVENT, AND THAT PROBABLY CONTRIBUTED TO MISSING THE SIGNS. PIT HAS YELLOW LIGHTS ON THE TXWY CTRLINES AT MANY LOCATIONS ON THE ARPT AT POTENTIALLY HAZARDOUS INTXNS, BUT NOT AT THIS ONE THAT NIGHT. I FEEL THIS LOCATION ON CTRLINE IS BETTER FOR WARNING LIGHTS BECAUSE WHEN VISIBILITY IS LIMITED OR RESTR, THAT IS THE AREA THAT GETS THE MOST ATTN, RIGHT IN FRONT OF THE ACFT WHERE IT IS MOVING, NOT 100 FT OR SO OFF TO THE SIDE.
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.