37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 630441 |
Time | |
Date | 200409 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : bgm.airport |
State Reference | NY |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | EMB ERJ 145 ER&LR |
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 : atp |
Experience | flight time last 90 days : 180 flight time total : 500 flight time type : 400 |
ASRS Report | 630441 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : instrument pilot : cfi pilot : commercial |
Experience | flight time last 90 days : 100 flight time total : 1080 flight time type : 80 |
ASRS Report | 630443 |
Events | |
Anomaly | incursion : runway non adherence : far non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airport |
Primary Problem | Flight Crew Human Performance |
Narrative:
Instructed to taxi to runway 34 from main terminal using taxiway G, I had my mind set on having to cross runway 10/28 and did not realize that I continued on taxiway H, which intersects runway 34. We were advised from bgm ground that we were entering runway 34 and stopped before entering the pavement of runway 34. There was no conflict but I believe I might have entered the runway environment even if we did not see a runway hold short line or runway identifier signs. I think they are not present at that location. Supplemental information from acn 630443: we were called by ground shortly after and immediately stopped. Neither of us saw any runway signs designating the runway. Visibility was about 4 miles. I personally was unfamiliar with the airport. We continued the taxi down to runway 34 on the runway. Callback conversation with reporter acn 630441 revealed the following information: the reporter revealed that they did see the hold short line. However, they never did see the red runway sign for runway 16/34. Reporter admits that they turned on the wrong runway, but it would have helped if there was a runway sign for this runway.
Original NASA ASRS Text
Title: AN E145 FLT CREW TURNS ONTO THE WRONG TXWY AND CROSSES THE HOLD LINE OF RWY 16/34 INSTEAD OF RWY 10/28 AT BGM.
Narrative: INSTRUCTED TO TAXI TO RWY 34 FROM MAIN TERMINAL USING TXWY G, I HAD MY MIND SET ON HAVING TO CROSS RWY 10/28 AND DID NOT REALIZE THAT I CONTINUED ON TXWY H, WHICH INTERSECTS RWY 34. WE WERE ADVISED FROM BGM GND THAT WE WERE ENTERING RWY 34 AND STOPPED BEFORE ENTERING THE PAVEMENT OF RWY 34. THERE WAS NO CONFLICT BUT I BELIEVE I MIGHT HAVE ENTERED THE RWY ENVIRONMENT EVEN IF WE DID NOT SEE A RWY HOLD SHORT LINE OR RWY IDENTIFIER SIGNS. I THINK THEY ARE NOT PRESENT AT THAT LOCATION. SUPPLEMENTAL INFO FROM ACN 630443: WE WERE CALLED BY GND SHORTLY AFTER AND IMMEDIATELY STOPPED. NEITHER OF US SAW ANY RWY SIGNS DESIGNATING THE RWY. VISIBILITY WAS ABOUT 4 MILES. I PERSONALLY WAS UNFAMILIAR WITH THE ARPT. WE CONTINUED THE TAXI DOWN TO RWY 34 ON THE RWY. CALLBACK CONVERSATION WITH RPTR ACN 630441 REVEALED THE FOLLOWING INFO: THE RPTR REVEALED THAT THEY DID SEE THE HOLD SHORT LINE. HOWEVER, THEY NEVER DID SEE THE RED RWY SIGN FOR RWY 16/34. RPTR ADMITS THAT THEY TURNED ON THE WRONG RWY, BUT IT WOULD HAVE HELPED IF THERE WAS A RWY SIGN FOR THIS RWY.
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.