 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A BAE3200 flight crew in stl experiences an unauthorized runway entry while attempting to deal with the aftermath of an aborted takeoff.
| Attributes | |
| ACN | 403940 |
| Time | |
| Date | 199806 |
| Day | Tue |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : stl |
| State Reference | MO |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | Jetstream 41 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | climbout : takeoff ground other : taxi other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | other : unknown |
| Flight Phase | descent : approach landing : go around |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : flight engineer |
| Experience | flight time last 90 days : 185 flight time total : 7000 flight time type : 1500 |
| ASRS Report | 403940 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 200 flight time total : 2800 flight time type : 200 |
| ASRS Report | 403848 |
| Events | |
| Anomaly | aircraft equipment problem : critical incursion : runway non adherence : clearance non adherence : far |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | controller : issued new clearance other other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation other |
Narrative:
Takeoff roll was started on runway 31. Soon after power application, the right torque gauge failed. I aborted the takeoff. The first officer notified tower and we were given instructions to continue down the runway to taxiway B and hold short of runway 30R. We turned off on taxiway B and taxied across the hold short line for runway 30R. Tower called and told us again to hold short, which we did -- short of the runway, but across the hold short line. At this point an aircraft on final for runway 30R was instructed to go around. I believe this happened because my attention was split between the tower controller, torque gauge and instructing the first officer to call company. Also, many times when landing on runway 30R, we are told to exit the runway and hold short of runway 30L on taxiway B. I had short of runway 30L on my mind, not runway 30R. Plain and simple -- this happened because I was trying to do too much at once. In the future, I will clear all runways and txwys before beginning any duties that would divert my attention from the task at hand of controling a moving aircraft. Supplemental information from acn 403848: exiting runway 31, I was busy following the captain's instructions after aborting. I looked up and saw we were going to cross runway 30R so I started applying brakes. The tower instructed us to cross immediately, and for the landing aircraft to go around. To prevent this situation from happening again, I will be 'outside the aircraft' 50 yards prior to the hold short line to ensure the PIC is going to hold short, and xchk that the other pilot also heard the hold short instruction that I read back.
Original NASA ASRS Text
Title: A BAE3200 FLC IN STL EXPERIENCES AN UNAUTH RWY ENTRY WHILE ATTEMPTING TO DEAL WITH THE AFTERMATH OF AN ABORTED TKOF.
Narrative: TKOF ROLL WAS STARTED ON RWY 31. SOON AFTER PWR APPLICATION, THE R TORQUE GAUGE FAILED. I ABORTED THE TKOF. THE FO NOTIFIED TWR AND WE WERE GIVEN INSTRUCTIONS TO CONTINUE DOWN THE RWY TO TXWY B AND HOLD SHORT OF RWY 30R. WE TURNED OFF ON TXWY B AND TAXIED ACROSS THE HOLD SHORT LINE FOR RWY 30R. TWR CALLED AND TOLD US AGAIN TO HOLD SHORT, WHICH WE DID -- SHORT OF THE RWY, BUT ACROSS THE HOLD SHORT LINE. AT THIS POINT AN ACFT ON FINAL FOR RWY 30R WAS INSTRUCTED TO GAR. I BELIEVE THIS HAPPENED BECAUSE MY ATTN WAS SPLIT BTWN THE TWR CTLR, TORQUE GAUGE AND INSTRUCTING THE FO TO CALL COMPANY. ALSO, MANY TIMES WHEN LNDG ON RWY 30R, WE ARE TOLD TO EXIT THE RWY AND HOLD SHORT OF RWY 30L ON TXWY B. I HAD SHORT OF RWY 30L ON MY MIND, NOT RWY 30R. PLAIN AND SIMPLE -- THIS HAPPENED BECAUSE I WAS TRYING TO DO TOO MUCH AT ONCE. IN THE FUTURE, I WILL CLR ALL RWYS AND TXWYS BEFORE BEGINNING ANY DUTIES THAT WOULD DIVERT MY ATTN FROM THE TASK AT HAND OF CTLING A MOVING ACFT. SUPPLEMENTAL INFO FROM ACN 403848: EXITING RWY 31, I WAS BUSY FOLLOWING THE CAPT'S INSTRUCTIONS AFTER ABORTING. I LOOKED UP AND SAW WE WERE GOING TO CROSS RWY 30R SO I STARTED APPLYING BRAKES. THE TWR INSTRUCTED US TO CROSS IMMEDIATELY, AND FOR THE LNDG ACFT TO GAR. TO PREVENT THIS SIT FROM HAPPENING AGAIN, I WILL BE 'OUTSIDE THE ACFT' 50 YARDS PRIOR TO THE HOLD SHORT LINE TO ENSURE THE PIC IS GOING TO HOLD SHORT, AND XCHK THAT THE OTHER PLT ALSO HEARD THE HOLD SHORT INSTRUCTION THAT I READ BACK.
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.