Narrative:

Upon approaching the takeoff end of runway 19 the copilot switched frequency from ground control to tower and called 'identify ready for takeoff.' immediately from tower the instruction was heard 'identify position and hold.' the copilot acknowledged the transmission 'identify position and hold.' as we crossed the hold short line the copilot saw an aircraft on approach, approximately 3-4 mi out on final. The sep is not unusual in our fast paced environment. As we stopped in position we heard the tower clear an aircraft for takeoff on runway 9. At that time the tower asked us if we were on the runway to which we acknowledge. The flight on final was instructed to go around. Incident was caused by communication breakdown between the tower and the aircraft. I'm not sure whether the xmissions were blocked or misunderstood or not heard at all. Possible cure for the problem: split tower frequencys when utilizing more than 1 runway for takeoffs and lndgs. Also have ground control switch you to tower and wait for the tower's instruction for takeoff. Supplemental information from acn 101526: the cause of this incident was the tower clearing a divergent aircraft into position on a different runway (9) west/O using a call sign. The controller then missed my readback, which may have been blocked by the other aircraft's readback, and we assumed that all was well and taxied onto the runway. A contributing factor could be that the approach end of runway 9 is not visible from the approach end of runway 19 so we were unable to see any other aircraft waiting for takeoff.

Google
 

Original NASA ASRS Text

Title: GO AROUND OCCURRED ACCOUNT ACR ON RWY.

Narrative: UPON APCHING THE TKOF END OF RWY 19 THE COPLT SWITCHED FREQ FROM GND CTL TO TWR AND CALLED 'IDENT READY FOR TKOF.' IMMEDIATELY FROM TWR THE INSTRUCTION WAS HEARD 'IDENT POS AND HOLD.' THE COPLT ACKNOWLEDGED THE XMISSION 'IDENT POS AND HOLD.' AS WE CROSSED THE HOLD SHORT LINE THE COPLT SAW AN ACFT ON APCH, APPROX 3-4 MI OUT ON FINAL. THE SEP IS NOT UNUSUAL IN OUR FAST PACED ENVIRONMENT. AS WE STOPPED IN POS WE HEARD THE TWR CLR AN ACFT FOR TKOF ON RWY 9. AT THAT TIME THE TWR ASKED US IF WE WERE ON THE RWY TO WHICH WE ACKNOWLEDGE. THE FLT ON FINAL WAS INSTRUCTED TO GO AROUND. INCIDENT WAS CAUSED BY COM BREAKDOWN BTWN THE TWR AND THE ACFT. I'M NOT SURE WHETHER THE XMISSIONS WERE BLOCKED OR MISUNDERSTOOD OR NOT HEARD AT ALL. POSSIBLE CURE FOR THE PROB: SPLIT TWR FREQS WHEN UTILIZING MORE THAN 1 RWY FOR TKOFS AND LNDGS. ALSO HAVE GND CTL SWITCH YOU TO TWR AND WAIT FOR THE TWR'S INSTRUCTION FOR TKOF. SUPPLEMENTAL INFO FROM ACN 101526: THE CAUSE OF THIS INCIDENT WAS THE TWR CLRING A DIVERGENT ACFT INTO POS ON A DIFFERENT RWY (9) W/O USING A CALL SIGN. THE CTLR THEN MISSED MY READBACK, WHICH MAY HAVE BEEN BLOCKED BY THE OTHER ACFT'S READBACK, AND WE ASSUMED THAT ALL WAS WELL AND TAXIED ONTO THE RWY. A CONTRIBUTING FACTOR COULD BE THAT THE APCH END OF RWY 9 IS NOT VISIBLE FROM THE APCH END OF RWY 19 SO WE WERE UNABLE TO SEE ANY OTHER ACFT WAITING FOR TKOF.

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