AN MD80 CREW AT BOS FAILED TO HOLD AT THE RWY 4L 'B' HOLD SHORT LINE CAUSING A GAR. BOS TWR NOTIFIED CREW.

2006-05 · NASA ASRS report 698204

Date: 2006-05 · Aircraft: MD-88 · Phase: taxi

Anomalies: deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy|ground-incursion-runway

Synopsis

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.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.