Bos local controller described a less than required separation runway crossing event; alleging that ...

Attributes
ACN	874735
Time
Date	201002
Local Time Of Day	1201-1800
Place
Locale Reference	BOS.Airport
State Reference	MA
Aircraft 1
Make Model Name	SF 340B
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Other Instrument Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Person 1
Function	Flight Data / Clearance Delivery Local
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy Ground Incursion Runway

Narrative:

Runway 33L arrival landing while traffic was crossing down field. Aircraft Y was crossing runway 33L at taxiway north intersection; approximately 8;000 ft down the runway. Aircraft Y was issued crossing clearance 'without delay; traffic short final.' aircraft Y was slow to start moving so I reiterated 'cross without delay.' at the point I realized the operation was not going to work; aircraft Y was on the runway as the aircraft X SF34 was about to touch down. I felt that allowing the aircraft to land was safer at that point rather than issuing a go-around instruction with the arrival in a flare to touchdown. Recommendation; I should have considered the calm wind which made the arrival traffic fast. Also; aircraft Y had waited for a couple of arrivals before crossing so I didn't want to delay aircraft Y any further.

Original NASA ASRS Text

Title: BOS Local Controller described a less than required separation runway crossing event; alleging that when recognized; landing traffic was about to touch down and go-around instructions may have compromised safety.

Narrative: Runway 33L arrival landing while traffic was crossing down field. Aircraft Y was crossing Runway 33L at Taxiway N intersection; approximately 8;000 FT down the runway. Aircraft Y was issued crossing clearance 'without delay; traffic short final.' Aircraft Y was slow to start moving so I reiterated 'cross without delay.' At the point I realized the operation was not going to work; Aircraft Y was on the runway as the Aircraft X SF34 was about to touch down. I felt that allowing the aircraft to land was safer at that point rather than issuing a go-around instruction with the arrival in a flare to touchdown. Recommendation; I should have considered the calm wind which made the arrival traffic fast. Also; Aircraft Y had waited for a couple of arrivals before crossing so I didn't want to delay Aircraft Y any further.

Data retrieved from NASA's ASRS site as of April 2012 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.

Bos local controller described a less than required separation runway crossing event; alleging that when recognized; landing traffic was about to touch down and go-around instructions may have compromised safety.