37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 643264 |
Time | |
Date | 200501 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : iah.airport |
State Reference | TX |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : iah.tower |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | ground : takeoff roll |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 170 flight time total : 8000 flight time type : 5500 |
ASRS Report | 643264 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : ground less severe incursion : taxiway non adherence : company policies non adherence : clearance non adherence : published procedure non adherence : far other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : returned to intended or assigned course flight crew : became reoriented |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airport |
Primary Problem | Flight Crew Human Performance |
Narrative:
Current ATIS showed runways 15L and 15R being used for takeoff. Taxi instructions given to us directed us to runway 33R due to a runway change. Instructions were nr; wf; wa. On ramp south of wf; there was a lot of construction; which was not on ATIS. At wf; controller told us to turn right on wf and continue. When I turned south of wa; I made a comment to the first officer about there being no signage on wa and feeling like we were on some road heading nowhere. (Both of us had never taxied to runway 33R before.) with noticing no signage; I must have thought I was on wb instead of wa; then turned right onto wg. I then made another comment as to the signage on wg looking strange. The first officer was heads down most of the time trying to type information into ACARS to our dispatcher; because we needed required information for takeoff; due to our automatic speed brakes being inoperative. Our current system doesn't allow the runway weights to automatically come up; so we need to take all the time with ACARS asking our dispatchers for every runway we'll possibly use. I don't remember seeing a hold short; nor do I remember seeing a runway entrance sign for runway 15L/33R. By the time I realized we were coming up on the active runway; I stopped the aircraft short. We told the tower where we were and that we had taken a wrong turn. He cleared an aircraft for takeoff; then cleared us back onto wa. Upon arrival at our destination; I called iah tower. I wanted to know if there was in fact a runway sign noting runway 15L/33R. He said I needed to call the city of iah. He did say they've had numerous incidents in the last several months at that exact location with both civilian and air carriers. He said the city was aware of the signage problems; but nothing had been done yet. All incidents included the aircraft either taxiing onto the active runway or stopping just short when they realized they were in the wrong place.
Original NASA ASRS Text
Title: A B737-300 PLT INADVERTENTLY TAXIED OFF THE ASSIGNED ROUTING BUT HELD SHORT OF AN ACTIVE RWY.
Narrative: CURRENT ATIS SHOWED RWYS 15L AND 15R BEING USED FOR TKOF. TAXI INSTRUCTIONS GIVEN TO US DIRECTED US TO RWY 33R DUE TO A RWY CHANGE. INSTRUCTIONS WERE NR; WF; WA. ON RAMP S OF WF; THERE WAS A LOT OF CONSTRUCTION; WHICH WAS NOT ON ATIS. AT WF; CTLR TOLD US TO TURN R ON WF AND CONTINUE. WHEN I TURNED S OF WA; I MADE A COMMENT TO THE FO ABOUT THERE BEING NO SIGNAGE ON WA AND FEELING LIKE WE WERE ON SOME ROAD HEADING NOWHERE. (BOTH OF US HAD NEVER TAXIED TO RWY 33R BEFORE.) WITH NOTICING NO SIGNAGE; I MUST HAVE THOUGHT I WAS ON WB INSTEAD OF WA; THEN TURNED R ONTO WG. I THEN MADE ANOTHER COMMENT AS TO THE SIGNAGE ON WG LOOKING STRANGE. THE FO WAS HEADS DOWN MOST OF THE TIME TRYING TO TYPE INFO INTO ACARS TO OUR DISPATCHER; BECAUSE WE NEEDED REQUIRED INFO FOR TKOF; DUE TO OUR AUTO SPD BRAKES BEING INOP. OUR CURRENT SYSTEM DOESN'T ALLOW THE RWY WEIGHTS TO AUTOMATICALLY COME UP; SO WE NEED TO TAKE ALL THE TIME WITH ACARS ASKING OUR DISPATCHERS FOR EVERY RWY WE'LL POSSIBLY USE. I DON'T REMEMBER SEEING A HOLD SHORT; NOR DO I REMEMBER SEEING A RWY ENTRANCE SIGN FOR RWY 15L/33R. BY THE TIME I REALIZED WE WERE COMING UP ON THE ACTIVE RWY; I STOPPED THE ACFT SHORT. WE TOLD THE TWR WHERE WE WERE AND THAT WE HAD TAKEN A WRONG TURN. HE CLRED AN ACFT FOR TKOF; THEN CLRED US BACK ONTO WA. UPON ARRIVAL AT OUR DESTINATION; I CALLED IAH TWR. I WANTED TO KNOW IF THERE WAS IN FACT A RWY SIGN NOTING RWY 15L/33R. HE SAID I NEEDED TO CALL THE CITY OF IAH. HE DID SAY THEY'VE HAD NUMEROUS INCIDENTS IN THE LAST SEVERAL MONTHS AT THAT EXACT LOCATION WITH BOTH CIVILIAN AND AIR CARRIERS. HE SAID THE CITY WAS AWARE OF THE SIGNAGE PROBS; BUT NOTHING HAD BEEN DONE YET. ALL INCIDENTS INCLUDED THE ACFT EITHER TAXIING ONTO THE ACTIVE RWY OR STOPPING JUST SHORT WHEN THEY REALIZED THEY WERE IN THE WRONG PLACE.
Data retrieved from NASA's ASRS site as of January 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.