Runway incursion at bos, ma.

Attributes
ACN	470084
Time
Date	200004
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : bos.airport
State Reference	MA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Beech 1900
Operating Under FAR Part	Part 135
Flight Phase	ground : taxi ground : holding
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : bos.tower
Operator	common carrier : air carrier
Make Model Name	Super King Air 200 HDC
Operating Under FAR Part	Part 135
Flight Phase	landing : roll
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 240 flight time total : 3400 flight time type : 950
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera other flight crewa other flight crewb other other : 3
Resolutory Action	controller : issued advisory
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Visual approach to runway 27 bos. After normal landing, we cleared runway 27 on taxiway east. Tower advised to hold short of runway 22L. I acknowledged. The captain called for after landing checklist. When checklist completed, I looked out and we had crossed the hold short. Tower advised original instructions were to hold short of runway 22L. I acknowledged with our call sign. This situation can be prevented by creation of a procedure that requires pilots to read back hold short instructions to each other. Also, no checklists until aircraft is stopped at hold short or clear of runway. Supplemental information from acn 470542: I was first officer on aircraft Y. We had been cleared to land on runway 22L to hold short of runway 27. We were on the rollout on runway 22L, when tower spoke 'aircraft X you were supposed to hold short of runway 22L.' this was the runway we were on. We saw the aircraft crossing over runway 1500 ft ahead of us. We continued to turn on our planned exit taxiway which was well short of the point where aircraft X crossed runway 22L. We both continued to taxi in under normal circumstances.

Original NASA ASRS Text

Title: RWY INCURSION AT BOS, MA.

Narrative: VISUAL APCH TO RWY 27 BOS. AFTER NORMAL LNDG, WE CLRED RWY 27 ON TXWY E. TWR ADVISED TO HOLD SHORT OF RWY 22L. I ACKNOWLEDGED. THE CAPT CALLED FOR AFTER LNDG CHKLIST. WHEN CHKLIST COMPLETED, I LOOKED OUT AND WE HAD CROSSED THE HOLD SHORT. TWR ADVISED ORIGINAL INSTRUCTIONS WERE TO HOLD SHORT OF RWY 22L. I ACKNOWLEDGED WITH OUR CALL SIGN. THIS SIT CAN BE PREVENTED BY CREATION OF A PROC THAT REQUIRES PLTS TO READ BACK HOLD SHORT INSTRUCTIONS TO EACH OTHER. ALSO, NO CHKLISTS UNTIL ACFT IS STOPPED AT HOLD SHORT OR CLR OF RWY. SUPPLEMENTAL INFO FROM ACN 470542: I WAS FO ON ACFT Y. WE HAD BEEN CLRED TO LAND ON RWY 22L TO HOLD SHORT OF RWY 27. WE WERE ON THE ROLLOUT ON RWY 22L, WHEN TWR SPOKE 'ACFT X YOU WERE SUPPOSED TO HOLD SHORT OF RWY 22L.' THIS WAS THE RWY WE WERE ON. WE SAW THE ACFT XING OVER RWY 1500 FT AHEAD OF US. WE CONTINUED TO TURN ON OUR PLANNED EXIT TXWY WHICH WAS WELL SHORT OF THE POINT WHERE ACFT X CROSSED RWY 22L. WE BOTH CONTINUED TO TAXI IN UNDER NORMAL CIRCUMSTANCES.

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.