37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 512097 |
Time | |
Date | 200105 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : ric.airport |
State Reference | VA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : ric.tower |
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 : ric.tower |
Operator | common carrier : air taxi |
Make Model Name | Beech 1900 |
Operating Under FAR Part | Part 135 |
Flight Phase | descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : commercial pilot : atp |
Experience | flight time last 90 days : 65 flight time total : 5800 flight time type : 1020 |
ASRS Report | 512097 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | incursion : runway non adherence : clearance |
Independent Detector | other controllera other flight crewa other flight crewb other other : 3 |
Resolutory Action | controller : issued new clearance flight crew : executed go around |
Miss Distance | horizontal : 75 vertical : 200 |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Richmond landing runway 16 and 20. After landing runway 16, tower directs 'abc right turn off and remain with me.' first officer replies 'abc right off, we're clear, with you.' tower instructs 'abc right on lima, left on charlie, hold short runway 26.' first officer replies as abc is already turning on lima and ground taxi conflict evident with outbound flight on taxiway echo at lima, 'abc we'll go left on charlie, hold short runway 20, and are you also holding air carrier X for us? 'No reply from tower, as conflict resolves, I think tower must be on ground frequency to air carrier X. As we continue to taxiway charlie, first officer does after landing checks and as abc turns on to charlie, first officer states 'no 2. Engine to go on after landing checklist.' captain replies' clear on 2' first officer pauses, thinking normally we would keep two engines running until clearing active runway after holding short. APU is not running per this captain's desires. Captain says 'go ahead on 2' first officer shuts down #2 and configures bleeds. Overheard: tower transmits 'air carrier X cleared to land runway 20.' we (abc) are half way to runway 20 on charlie, taxing at good speed. I think captain is aware of hold short but is trying to time clearance to continue without stopping. First officer transmits on base frequency 'inbound.' base requests 'APU run at gate.' (only called base as I considered no other intersections to monitor and no tower contact until landing traffic on runway 20 had rolled by.) first officer starts APU and is transferring power then bleeds as aircraft approachs runway 20 hold point on 'charlie' as gate is just beyond runway 20. First officer realizes aircraft speed indicates we are not stopping to hold and calls loudly 'hold short' and gets on brakes (as captain does so too) with aircraft on SH0RT final. Tower transmits at same time 'abc hold short 20!' as aircraft abruptly stops short of runway, first officer replies 'abc holding short,' but missed button to push radio #1 transmit. Tower directs air carrier X to go around. Captain's comments indicate he was unaware of requirement to hold short of runway 20 and did not see aircraft on final. First officer distracted by APU bleed configuration and relative new experience in new model, base, with different procedures. First officer should have voiced concern about engine #2 shutdown as 'do we want to shut it down with the hold short at 20 to go?' would have reminded captain of requirement. New first officer still in training mindset that captain is aware of everything. Also, complacency about relative low level of ground operations at small airport. Alertness and communication. Passenger comments indicate awareness of quick stop and other aircraft go around. Callback conversation with reporter revealed the following information: reporter was the first officer and stated the controller instructed the flight to hold short of runway 20. He did not expect the captain to command a shutdown of number 2 engine since the controller had instructed them to hold short of runway 20. The captain had also called for the shutdown of the APU, but on check in with company, the first officer was told to keep the APU running. The first officer said near the runway he looked up and stepped on the brakes as the controller instructed a stop. He estimated the aircraft was approximately 40 ft past the hold line.
Original NASA ASRS Text
Title: B737 CREW TAXIING TO TERMINAL AFTER LNDG RIC FAIL TO STOP AT HOLD SHORT LINES WITH TFC ON APCH NEAR THE THRESHOLD.
Narrative: RICHMOND LNDG RWY 16 AND 20. AFTER LNDG RWY 16, TWR DIRECTS 'ABC R TURN OFF AND REMAIN WITH ME.' FO REPLIES 'ABC R OFF, WE'RE CLEAR, WITH YOU.' TWR INSTRUCTS 'ABC R ON LIMA, L ON CHARLIE, HOLD SHORT RWY 26.' FO REPLIES AS ABC IS ALREADY TURNING ON LIMA AND GND TAXI CONFLICT EVIDENT WITH OUTBOUND FLT ON TXWY ECHO AT LIMA, 'ABC WE'LL GO L ON CHARLIE, HOLD SHORT RWY 20, AND ARE YOU ALSO HOLDING ACR X FOR US? 'NO REPLY FROM TWR, AS CONFLICT RESOLVES, I THINK TWR MUST BE ON GND FREQ TO ACR X. AS WE CONTINUE TO TXWY CHARLIE, FO DOES AFTER LNDG CHECKS AND AS ABC TURNS ON TO CHARLIE, FO STATES 'NO 2. ENGINE TO GO ON AFTER LNDG CHKLIST.' CAPT REPLIES' CLEAR ON 2' FO PAUSES, THINKING NORMALLY WE WOULD KEEP TWO ENGINES RUNNING UNTIL CLRING ACTIVE RWY AFTER HOLDING SHORT. APU IS NOT RUNNING PER THIS CAPT'S DESIRES. CAPT SAYS 'GO AHEAD ON 2' FO SHUTS DOWN #2 AND CONFIGURES BLEEDS. OVERHEARD: TWR TRANSMITS 'ACR X CLRED TO LAND RWY 20.' WE (ABC) ARE HALF WAY TO RWY 20 ON CHARLIE, TAXING AT GOOD SPEED. I THINK CAPT IS AWARE OF HOLD SHORT BUT IS TRYING TO TIME CLRNC TO CONTINUE WITHOUT STOPPING. FO TRANSMITS ON BASE FREQ 'INBOUND.' BASE REQUESTS 'APU RUN AT GATE.' (ONLY CALLED BASE AS I CONSIDERED NO OTHER INTERSECTIONS TO MONITOR AND NO TWR CONTACT UNTIL LNDG TFC ON RWY 20 HAD ROLLED BY.) FO STARTS APU AND IS TRANSFERRING PWR THEN BLEEDS AS ACFT APCHS RWY 20 HOLD POINT ON 'CHARLIE' AS GATE IS JUST BEYOND RWY 20. FO REALIZES ACFT SPEED INDICATES WE ARE NOT STOPPING TO HOLD AND CALLS LOUDLY 'HOLD SHORT' AND GETS ON BRAKES (AS CAPT DOES SO TOO) WITH ACFT ON SH0RT FINAL. TWR TRANSMITS AT SAME TIME 'ABC HOLD SHORT 20!' AS ACFT ABRUPTLY STOPS SHORT OF RWY, FO REPLIES 'ABC HOLDING SHORT,' BUT MISSED BUTTON TO PUSH RADIO #1 TRANSMIT. TWR DIRECTS ACR X TO GAR. CAPT'S COMMENTS INDICATE HE WAS UNAWARE OF REQUIREMENT TO HOLD SHORT OF RWY 20 AND DID NOT SEE ACFT ON FINAL. FO DISTRACTED BY APU BLEED CONFIGURATION AND RELATIVE NEW EXPERIENCE IN NEW MODEL, BASE, WITH DIFFERENT PROCS. FO SHOULD HAVE VOICED CONCERN ABOUT ENGINE #2 SHUTDOWN AS 'DO WE WANT TO SHUT IT DOWN WITH THE HOLD SHORT AT 20 TO GO?' WOULD HAVE REMINDED CAPT OF REQUIREMENT. NEW FO STILL IN TRAINING MINDSET THAT CAPT IS AWARE OF EVERYTHING. ALSO, COMPLACENCY ABOUT RELATIVE LOW LEVEL OF GND OPS AT SMALL ARPT. ALERTNESS AND COM. PAX COMMENTS INDICATE AWARENESS OF QUICK STOP AND OTHER ACFT GAR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR WAS THE FO AND STATED THE CTLR INSTRUCTED THE FLT TO HOLD SHORT OF RWY 20. HE DID NOT EXPECT THE CAPT TO COMMAND A SHUTDOWN OF NUMBER 2 ENGINE SINCE THE CTLR HAD INSTRUCTED THEM TO HOLD SHORT OF RWY 20. THE CAPT HAD ALSO CALLED FOR THE SHUTDOWN OF THE APU, BUT ON CHECK IN WITH COMPANY, THE FO WAS TOLD TO KEEP THE APU RUNNING. THE FO SAID NEAR THE RWY HE LOOKED UP AND STEPPED ON THE BRAKES AS THE CTLR INSTRUCTED A STOP. HE ESTIMATED THE ACFT WAS APPROX 40 FT PAST THE HOLD LINE.
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.