Part 125 air carrier lands bos runway 4L with a B757 still obstructing the landing runway.

Attributes
ACN	438088
Time
Date	199905
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bos.airport
State Reference	MA
Altitude	agl single value : 200
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : bos.tower tracon : cyvr.tracon
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Operating Under FAR Part	Part 125
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : visual
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : bos.tower
Operator	common carrier : air carrier
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : cfi pilot : multi engine
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial
Events
Anomaly	conflict : ground critical incursion : runway non adherence : far non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Miss Distance	horizontal : 100 vertical : 50
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While on a visual approach to runway 4L, the tower controller crossed a B757. The first officer and I both thought that this was going to cause a problem. The B757 was still not moving, so the tower controller told the B757 to cross without hesitation. The controller should have told the B757 to cancel clearance and hold position. At about this point, I was thinking a go around was in order. We continued the approach and passed very, very close to the B757's tail. The controller should not have crossed the aircraft. When B757 sat and didn't move, the controller should have canceled clearance. The controller should have told us to go around. The B757 crew shouldn't have accepted the clearance when they saw us on short final and could not move quickly across runway. And we should not have pushed a bad situation and went around, even though we were cleared to land. I wondered if we had gone around, if the controller would have to explain why there was a go around (if this is why the controller never called for us to go around). The B757 waited because they wanted us to go around (some union dual?).

Original NASA ASRS Text

Title: PART 125 ACR LANDS BOS RWY 4L WITH A B757 STILL OBSTRUCTING THE LNDG RWY.

Narrative: WHILE ON A VISUAL APCH TO RWY 4L, THE TWR CTLR CROSSED A B757. THE FO AND I BOTH THOUGHT THAT THIS WAS GOING TO CAUSE A PROB. THE B757 WAS STILL NOT MOVING, SO THE TWR CTLR TOLD THE B757 TO CROSS WITHOUT HESITATION. THE CTLR SHOULD HAVE TOLD THE B757 TO CANCEL CLRNC AND HOLD POS. AT ABOUT THIS POINT, I WAS THINKING A GAR WAS IN ORDER. WE CONTINUED THE APCH AND PASSED VERY, VERY CLOSE TO THE B757'S TAIL. THE CTLR SHOULD NOT HAVE CROSSED THE ACFT. WHEN B757 SAT AND DIDN'T MOVE, THE CTLR SHOULD HAVE CANCELED CLRNC. THE CTLR SHOULD HAVE TOLD US TO GO AROUND. THE B757 CREW SHOULDN'T HAVE ACCEPTED THE CLRNC WHEN THEY SAW US ON SHORT FINAL AND COULD NOT MOVE QUICKLY ACROSS RWY. AND WE SHOULD NOT HAVE PUSHED A BAD SIT AND WENT AROUND, EVEN THOUGH WE WERE CLRED TO LAND. I WONDERED IF WE HAD GONE AROUND, IF THE CTLR WOULD HAVE TO EXPLAIN WHY THERE WAS A GO AROUND (IF THIS IS WHY THE CTLR NEVER CALLED FOR US TO GO AROUND). THE B757 WAITED BECAUSE THEY WANTED US TO GO AROUND (SOME UNION DUAL?).

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.