Air carrier crosses hold short line and causes a go around.

Attributes
ACN	451384
Time
Date	199909
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : rdu.airport
State Reference	NC
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : rdu.tower tower : teb.tower
Operator	common carrier : air carrier
Make Model Name	Jetstream 41
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : taxi ground : position and hold
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : rdu.tower
Operator	Other
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	other : unknown
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 240 flight time total : 7000 flight time type : 3500
ASRS Report	450222
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial
Experience	flight time last 90 days : 260 flight time total : 1250 flight time type : 650
ASRS Report	451384
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : clearance
Resolutory Action	controller : issued new clearance controller : separated traffic flight crew : executed go around
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While taxiing for takeoff at the rdu airport, we were performing our usual taxi and takeoff checks. It was nighttime, around XA00, with runways 5L&right in use under single tower control, single ground control. My captain was off frequency, talking to the company, while I was monitoring ground control to switch over to tower. I did so, switching over to the tower frequency, my captain still off frequency with the company, and heard what I thought to be a position and hold command from the tower controller for runway 5R. I read back the clearance for a position and hold on runway 5R,, heard no feedback from the tower, which is typical, and told the captain we were position and hold, just as he came back on frequency. We proceeded to do so, and just as we got to the hold line for the runway, we were told to hold short by the tower, causing us to straddle the hold short line. Tower asked if we had in fact crossed the line, which we announced we had. He then proceeded to tell the aircraft on a 2 mi final to go around. He then cleared us into position on runway 5R, and eventually for takeoff. Contributing factors for this occurrence were: 1) single tower for similar sounding parallel runways with aircraft with similar sounding call signs, at night with static on the frequency. We also didn't get a readback confirmation on the position and hold command we mistakenly heard from the tower. He could have easily told us to hold short well before the incident occurred when we read back the misheard clearance if he wasn't preoccupied with 2 runways.

Original NASA ASRS Text

Title: ACR CROSSES HOLD SHORT LINE AND CAUSES A GAR.

Narrative: WHILE TAXIING FOR TKOF AT THE RDU ARPT, WE WERE PERFORMING OUR USUAL TAXI AND TKOF CHKS. IT WAS NIGHTTIME, AROUND XA00, WITH RWYS 5L&R IN USE UNDER SINGLE TWR CTL, SINGLE GND CTL. MY CAPT WAS OFF FREQ, TALKING TO THE COMPANY, WHILE I WAS MONITORING GND CTL TO SWITCH OVER TO TWR. I DID SO, SWITCHING OVER TO THE TWR FREQ, MY CAPT STILL OFF FREQ WITH THE COMPANY, AND HEARD WHAT I THOUGHT TO BE A POS AND HOLD COMMAND FROM THE TWR CTLR FOR RWY 5R. I READ BACK THE CLRNC FOR A POS AND HOLD ON RWY 5R,, HEARD NO FEEDBACK FROM THE TWR, WHICH IS TYPICAL, AND TOLD THE CAPT WE WERE POS AND HOLD, JUST AS HE CAME BACK ON FREQ. WE PROCEEDED TO DO SO, AND JUST AS WE GOT TO THE HOLD LINE FOR THE RWY, WE WERE TOLD TO HOLD SHORT BY THE TWR, CAUSING US TO STRADDLE THE HOLD SHORT LINE. TWR ASKED IF WE HAD IN FACT CROSSED THE LINE, WHICH WE ANNOUNCED WE HAD. HE THEN PROCEEDED TO TELL THE ACFT ON A 2 MI FINAL TO GO AROUND. HE THEN CLRED US INTO POS ON RWY 5R, AND EVENTUALLY FOR TKOF. CONTRIBUTING FACTORS FOR THIS OCCURRENCE WERE: 1) SINGLE TWR FOR SIMILAR SOUNDING PARALLEL RWYS WITH ACFT WITH SIMILAR SOUNDING CALL SIGNS, AT NIGHT WITH STATIC ON THE FREQ. WE ALSO DIDN'T GET A READBACK CONFIRMATION ON THE POS AND HOLD COMMAND WE MISTAKENLY HEARD FROM THE TWR. HE COULD HAVE EASILY TOLD US TO HOLD SHORT WELL BEFORE THE INCIDENT OCCURRED WHEN WE READ BACK THE MISHEARD CLRNC IF HE WASN'T PREOCCUPIED WITH 2 RWYS.

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.