37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 698204 |
Time | |
Date | 200605 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bos.airport |
State Reference | MA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : bos.tower |
Operator | common carrier : air carrier |
Make Model Name | MD-88 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : bos.tower |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | descent : approach landing : go around |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 160 flight time total : 13300 flight time type : 2810 |
ASRS Report | 698204 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | incursion : runway non adherence : clearance non adherence : far non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : assigned or threatened penalties |
Supplementary | |
Problem Areas | Airport Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Upon approaching spot X on the boston ramp; the first officer contacted bos ground control for taxi clearance. It took several attempts to make contact due to radio congestion. Ground instructed us to taxi to runway 9 via taxiway K; taxiway west; taxiway south. I (captain) did not copy the hold short clearance. Upon given clearance; I typed into the FMS scratch pad 'kws.' this was a short taxi and the first officer was busy completing taxi and delayed start checklists. Upon approaching the runway 4L hold short line; I began to slow and asked the first officer if we were to hold short 'here.' the first officer responded 'no; hold short runway 4' and pointed toward runway 9. The first officer did not state left or right. We crossed the approach end of runway 4L and held short of runway 9 on taxiway south. Once we were at cruise altitude; ATC told us to contact bos tower upon landing. Up to this point we had no idea that we had a runway incursion. Once the flight was over I contacted bos tower; tower advised me that we did indeed have a runway incursion that caused an aircraft to be sent around. Tower also advised me that they would file a pilot deviation. Contributing factors: 1) poor communication between captain and first officer. We should have used better terminology regarding runway 4L and runway 4R. Also; captain should have verified if any hold short clearance was given since I did not hear one. 2) captain was ZZZ based flying an XXX rotation. Captain not as familiar with these operations and airport ground operations. 3) experienced first officer. Captain relied too much on first officer's knowledge of ground operations in boston. 4) short taxi. First officer very busy with checklists which affected his situational awareness. 5) radio congestion. 6) confusing runway layout and txwys. 7) poor airport situational awareness. In conclusion; poor communication between myself and the first officer was the primary culprit to this deviation. I failed to live by the axiom -- 'when in doubt; ask.' the problem was that I relied on the first officer's experience in boston and his situational awareness though he was busy with checklists. I take full responsibility for this unfortunate event.
Original NASA ASRS Text
Title: AN MD80 CREW AT BOS FAILED TO HOLD AT THE RWY 4L 'B' HOLD SHORT LINE CAUSING A GAR. BOS TWR NOTIFIED CREW.
Narrative: UPON APCHING SPOT X ON THE BOSTON RAMP; THE FO CONTACTED BOS GND CTL FOR TAXI CLRNC. IT TOOK SEVERAL ATTEMPTS TO MAKE CONTACT DUE TO RADIO CONGESTION. GND INSTRUCTED US TO TAXI TO RWY 9 VIA TXWY K; TXWY W; TXWY S. I (CAPT) DID NOT COPY THE HOLD SHORT CLRNC. UPON GIVEN CLRNC; I TYPED INTO THE FMS SCRATCH PAD 'KWS.' THIS WAS A SHORT TAXI AND THE FO WAS BUSY COMPLETING TAXI AND DELAYED START CHKLISTS. UPON APCHING THE RWY 4L HOLD SHORT LINE; I BEGAN TO SLOW AND ASKED THE FO IF WE WERE TO HOLD SHORT 'HERE.' THE FO RESPONDED 'NO; HOLD SHORT RWY 4' AND POINTED TOWARD RWY 9. THE FO DID NOT STATE L OR R. WE CROSSED THE APCH END OF RWY 4L AND HELD SHORT OF RWY 9 ON TXWY S. ONCE WE WERE AT CRUISE ALT; ATC TOLD US TO CONTACT BOS TWR UPON LNDG. UP TO THIS POINT WE HAD NO IDEA THAT WE HAD A RWY INCURSION. ONCE THE FLT WAS OVER I CONTACTED BOS TWR; TWR ADVISED ME THAT WE DID INDEED HAVE A RWY INCURSION THAT CAUSED AN ACFT TO BE SENT AROUND. TWR ALSO ADVISED ME THAT THEY WOULD FILE A PLTDEV. CONTRIBUTING FACTORS: 1) POOR COM BTWN CAPT AND FO. WE SHOULD HAVE USED BETTER TERMINOLOGY REGARDING RWY 4L AND RWY 4R. ALSO; CAPT SHOULD HAVE VERIFIED IF ANY HOLD SHORT CLRNC WAS GIVEN SINCE I DID NOT HEAR ONE. 2) CAPT WAS ZZZ BASED FLYING AN XXX ROTATION. CAPT NOT AS FAMILIAR WITH THESE OPS AND ARPT GND OPS. 3) EXPERIENCED FO. CAPT RELIED TOO MUCH ON FO'S KNOWLEDGE OF GND OPS IN BOSTON. 4) SHORT TAXI. FO VERY BUSY WITH CHKLISTS WHICH AFFECTED HIS SITUATIONAL AWARENESS. 5) RADIO CONGESTION. 6) CONFUSING RWY LAYOUT AND TXWYS. 7) POOR ARPT SITUATIONAL AWARENESS. IN CONCLUSION; POOR COM BTWN MYSELF AND THE FO WAS THE PRIMARY CULPRIT TO THIS DEV. I FAILED TO LIVE BY THE AXIOM -- 'WHEN IN DOUBT; ASK.' THE PROB WAS THAT I RELIED ON THE FO'S EXPERIENCE IN BOSTON AND HIS SITUATIONAL AWARENESS THOUGH HE WAS BUSY WITH CHKLISTS. I TAKE FULL RESPONSIBILITY FOR THIS UNFORTUNATE EVENT.
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.