Bdl controller described an unauthorized runway entry event by an air carrier taxiing past an aircra...

Narrative:

A B737 was instructed to taxi up to and hold short of runway 24 at bdl. The pilot read back the hold short clearly. This was confirmed by a tape review. The aircraft then taxied past the hold short line and on to the runway. I asked him what they were doing and reminded them they were told to hold short. There was no response. A dash 8 was on short final and was sent around. Prior to the event there had been a confusing situation involving a cessna parked in the 24 hold pad and the B737 aircraft in question. This confusion may have led to the lapse in concentration that led to the pilot deviation. Recommendation; the pilot in this event may have been confused by the prior instance when a cessna was parked in the 24 hold pad. Both aircraft believed that they were number one in sequence despite the fact that I had originally told the cessna that he would be number two. There is an LOA at bdl that does not allow aircraft to pass each other if one is parked in the hold pad and this LOA did nothing to remedy this situation. Aircraft routinely pull into the hold pad without advising ATC and the local controller has to divert his attention away from the runway in order to remedy the sequence issues caused by aircraft pulling over. A better LOA is required as soon as possible in order to minimize confusion.

Original NASA ASRS Text

Title: BDL Controller described an unauthorized runway entry event by an air carrier taxiing past an aircraft holding short of the runway; the reporter noting clearer LOA procedures are necessary.

Narrative: A B737 was instructed to taxi up to and hold short of Runway 24 at BDL. The pilot read back the hold short clearly. This was confirmed by a tape review. The aircraft then taxied past the hold short line and on to the runway. I asked him what they were doing and reminded them they were told to hold short. There was no response. A Dash 8 was on short final and was sent around. Prior to the event there had been a confusing situation involving a Cessna parked in the 24 hold pad and the B737 aircraft in question. This confusion may have led to the lapse in concentration that led to the pilot deviation. Recommendation; the pilot in this event may have been confused by the prior instance when a Cessna was parked in the 24 hold pad. Both aircraft believed that they were number one in sequence despite the fact that I had originally told the Cessna that he would be number two. There is an LOA at BDL that does not allow aircraft to pass each other if one is parked in the hold pad and this LOA did nothing to remedy this situation. Aircraft routinely pull into the hold pad without advising ATC and the Local Controller has to divert his attention away from the runway in order to remedy the sequence issues caused by aircraft pulling over. A better LOA is required ASAP in order to minimize confusion.

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.

Attributes
ACN	934301
Time
Date	201102
Local Time Of Day	1801-2400
Place
Locale Reference	BDL.Tower
State Reference	CT
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Taxi
Flight Plan	IFR
Aircraft 2
Make Model Name	Dash 8 Series Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Coordinator Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Critical Deviation - Procedural Clearance Ground Incursion Runway

Bdl controller described an unauthorized runway entry event by an air carrier taxiing past an aircraft holding short of the runway; the reporter noting clearer LOA procedures are necessary.