DH8 initiates rejected takeoff when observing another aircraft landing on an intersecting runway.

Attributes
ACN	457778
Time
Date	199912
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ttn.airport
State Reference	NJ
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Dash 8-300
Operating Under FAR Part	Part 121
Flight Phase	ground : takeoff roll ground : position and hold
Route In Use	departure other
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : ttn.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Navigation In Use	other vortac
Flight Phase	landing : roll
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 50 flight time total : 3200 flight time type : 45
ASRS Report	457778
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : ground critical non adherence : published procedure non adherence : required legal separation
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance flight crew : rejected takeoff
Consequence	faa : investigated faa : reviewed incident with flight crew
Miss Distance	horizontal : 2000 vertical : 0
Supplementary
Problem Areas	Airport ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

We, air carrier X, were told 'position and hold.' we taxied into position and hold on runway 5. Approximately 1 min later, tower called, but in the transmission, they were stepped on. The call went 'air carrier X, takeoff cleared direct rbv VOR.' I, the first officer, responded by saying 'roger, air carrier X cleared for takeoff, going direct robbinsville.' tower did not respond. We proceeded to take off. After about 20 KTS, the captain noticed a light twin Y landing on the crossing runway, and we immediately aborted our takeoff. After we came to almost a complete stop, tower noticed we had tried to take off and demanded we exit the runway. They proceeded to review the tapes and after about 5 mins, they said that they were not going to pursue this matter any further. I feel that the tower should not have given us any new instructions until they were clearing us for takeoff. Also, the tower did not respond to my readback when I clearly stated 'roger, air carrier X cleared for takeoff, going direct robbinsville.' it was another chance for the checks and balance system to work, but ATC did not catch it!

Original NASA ASRS Text

Title: DH8 INITIATES REJECTED TKOF WHEN OBSERVING ANOTHER ACFT LNDG ON AN INTERSECTING RWY.

Narrative: WE, ACR X, WERE TOLD 'POS AND HOLD.' WE TAXIED INTO POS AND HOLD ON RWY 5. APPROX 1 MIN LATER, TWR CALLED, BUT IN THE XMISSION, THEY WERE STEPPED ON. THE CALL WENT 'ACR X, TKOF CLRED DIRECT RBV VOR.' I, THE FO, RESPONDED BY SAYING 'ROGER, ACR X CLRED FOR TKOF, GOING DIRECT ROBBINSVILLE.' TWR DID NOT RESPOND. WE PROCEEDED TO TAKE OFF. AFTER ABOUT 20 KTS, THE CAPT NOTICED A LIGHT TWIN Y LNDG ON THE XING RWY, AND WE IMMEDIATELY ABORTED OUR TKOF. AFTER WE CAME TO ALMOST A COMPLETE STOP, TWR NOTICED WE HAD TRIED TO TAKE OFF AND DEMANDED WE EXIT THE RWY. THEY PROCEEDED TO REVIEW THE TAPES AND AFTER ABOUT 5 MINS, THEY SAID THAT THEY WERE NOT GOING TO PURSUE THIS MATTER ANY FURTHER. I FEEL THAT THE TWR SHOULD NOT HAVE GIVEN US ANY NEW INSTRUCTIONS UNTIL THEY WERE CLRING US FOR TKOF. ALSO, THE TWR DID NOT RESPOND TO MY READBACK WHEN I CLRLY STATED 'ROGER, ACR X CLRED FOR TKOF, GOING DIRECT ROBBINSVILLE.' IT WAS ANOTHER CHANCE FOR THE CHKS AND BAL SYS TO WORK, BUT ATC DID NOT CATCH IT!

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.