Cpr light transport unauthorized runway entry caused small aircraft go around.

Attributes
ACN	159045
Time
Date	199010
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : hpn
State Reference	NY
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Light Transport, Low Wing, 2 Turbojet Eng
Flight Phase	ground : holding ground other : taxi
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Fixed Gear
Flight Phase	descent other landing : go around
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 110 flight time total : 6500 flight time type : 1900
ASRS Report	159045
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 3600 flight time type : 250
ASRS Report	159490
Events
Anomaly	conflict : ground critical incursion : runway non adherence : clearance
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Miss Distance	horizontal : 6000 vertical : 1000
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were #1 for primary active runway (2 runways active). A small turbo jet had just departed that runway. Tower transmitted a clearance that was partially blocked/covered by another aircraft transmission. We believe that the clearance was for us to position and hold on the active (familiar call signs in distorted transmission). The copilot acknowledged this was a transmission to the tower with the runway identify and the aircraft identify. I taxied past the hold lines to the threshold. I saw an aircraft approximately 2 mi on final. This is not uncommon at this airport. Anticipating a clearance for an immediate takeoff, I positioned the aircraft on the runway centerline. I asked the copilot to question the tower about this situation. He was unable to call because of the heavy radio traffic. The aircraft on final questioned the tower for his landing clearance. Evidently the tower saw us on the active and advised the landing aircraft to go around. Landing aircraft completed the go around west/O incident. Tower advised us that we were not cleared onto the active. We advised the tower that we believe a transmission to that effect was made and that we acknowledged that via a readback. The tower said our readback must have been blocked. We were then cleared for takeoff. This is a high traffic airport mixing light/propeller aircraft with medium jets. It is a common practice at the airport to issue a landing clearance and then position an aircraft on the same runway for departure. Therefore, seeing another aircraft on final as you take the active is not unusual, in anticipation of an immediate takeoff clearance. The high traffic load, both IFR and VFR, created many blocked/smeared/garbled xmissions. The clearance in question was a landing clearance for the aircraft on final. This aircraft had a similar call sign to ours. We heard some of the call sign as the transmission was being blocked. As a result the landing aircraft didn't receive his clearance. Our readback was blocked so that the tower and the landing aircraft were unaware of our movement. Conclusion: wait for a readable, unquestionable clearance and response to readbacks. Don't assume and don't hurry.

Original NASA ASRS Text

Title: CPR LTT UNAUTH RWY ENTRY CAUSED SMA GO AROUND.

Narrative: WE WERE #1 FOR PRIMARY ACTIVE RWY (2 RWYS ACTIVE). A SMALL TURBO JET HAD JUST DEPARTED THAT RWY. TWR XMITTED A CLRNC THAT WAS PARTIALLY BLOCKED/COVERED BY ANOTHER ACFT XMISSION. WE BELIEVE THAT THE CLRNC WAS FOR US TO POS AND HOLD ON THE ACTIVE (FAMILIAR CALL SIGNS IN DISTORTED XMISSION). THE COPLT ACKNOWLEDGED THIS WAS A XMISSION TO THE TWR WITH THE RWY IDENT AND THE ACFT IDENT. I TAXIED PAST THE HOLD LINES TO THE THRESHOLD. I SAW AN ACFT APPROX 2 MI ON FINAL. THIS IS NOT UNCOMMON AT THIS ARPT. ANTICIPATING A CLRNC FOR AN IMMEDIATE TKOF, I POSITIONED THE ACFT ON THE RWY CENTERLINE. I ASKED THE COPLT TO QUESTION THE TWR ABOUT THIS SITUATION. HE WAS UNABLE TO CALL BECAUSE OF THE HEAVY RADIO TFC. THE ACFT ON FINAL QUESTIONED THE TWR FOR HIS LNDG CLRNC. EVIDENTLY THE TWR SAW US ON THE ACTIVE AND ADVISED THE LNDG ACFT TO GO AROUND. LNDG ACFT COMPLETED THE GAR W/O INCIDENT. TWR ADVISED US THAT WE WERE NOT CLRED ONTO THE ACTIVE. WE ADVISED THE TWR THAT WE BELIEVE A XMISSION TO THAT EFFECT WAS MADE AND THAT WE ACKNOWLEDGED THAT VIA A READBACK. THE TWR SAID OUR READBACK MUST HAVE BEEN BLOCKED. WE WERE THEN CLRED FOR TKOF. THIS IS A HIGH TFC ARPT MIXING LIGHT/PROP ACFT WITH MEDIUM JETS. IT IS A COMMON PRACTICE AT THE ARPT TO ISSUE A LNDG CLRNC AND THEN POS AN ACFT ON THE SAME RWY FOR DEP. THEREFORE, SEEING ANOTHER ACFT ON FINAL AS YOU TAKE THE ACTIVE IS NOT UNUSUAL, IN ANTICIPATION OF AN IMMEDIATE TKOF CLRNC. THE HIGH TFC LOAD, BOTH IFR AND VFR, CREATED MANY BLOCKED/SMEARED/GARBLED XMISSIONS. THE CLRNC IN QUESTION WAS A LNDG CLRNC FOR THE ACFT ON FINAL. THIS ACFT HAD A SIMILAR CALL SIGN TO OURS. WE HEARD SOME OF THE CALL SIGN AS THE XMISSION WAS BEING BLOCKED. AS A RESULT THE LNDG ACFT DIDN'T RECEIVE HIS CLRNC. OUR READBACK WAS BLOCKED SO THAT THE TWR AND THE LNDG ACFT WERE UNAWARE OF OUR MOVEMENT. CONCLUSION: WAIT FOR A READABLE, UNQUESTIONABLE CLRNC AND RESPONSE TO READBACKS. DON'T ASSUME AND DON'T HURRY.

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.