Narrative:

Background: intersecting runways, runways 10 and 14 with aircraft in position both runways. Aircraft on runway 14 given takeoff clearance and both aircraft began takeoff roll. The aircraft on runway 10 aborted his takeoff when he saw us rotate and became airborne in front of him. Two factors contributed to the chain of events that caused this occurrence. First, the aircraft on runway 10 probably did not know that both runways were in use for takeoff. And second, the tower controllers failure to use the phraseology identifying the aircraft on different runways. If the controller had said, 'flight xyz cleared for takeoff runway 14,' it may have cued the pilot on the other runway that a takeoff was about to occur on the other runway. Or, if he had said, 'flight xyz aircraft holding in position runway 10, cleared for takeoff runway 14,' this would have been completely descriptive commentary and would most probably have called attention to the fact that both runways were in use. ATC should develop and implement as standard procedure this type of commentary. I strongly recommend ATC training facs begin this implementation as soon as possible. Supplemental information from acn 96764: the airport bldg kept us from seeing each other. Supplemental information from acn 96406: after arriving at the departure end of runway 10 we called ready for takeoff to tower. We were told to taxi into position and hold. No aircraft in front, we were #1. Holding in position we heard cleared for takeoff and my copilot confirmed our trip number 'rolling.' I proceeded with takeoff thrust and started my takeoff roll. My attention was of course mainly outside and I almost immediately saw another aircraft lifting off from runway 14. I immediately initiated a rejected takeoff and called the abort to tower. I received no call to abort from tower up to that point. We now understand that the takeoff clearance was for the other aircraft on runway 14.

Google
 

Original NASA ASRS Text

Title: LESS THAN STANDARD SEPARATION AND POTENTIAL CLOSE PROX AS 2 ACR STARTED TKOF ROLL SIMULTANEOUSLY ON INTERSECTING RWYS. ACR Y SAW X AND ABORTED TKOF WELL SHORT OF INTERSECTION. PLT DEVIATION AND OPERATIONAL ERROR.

Narrative: BACKGROUND: INTERSECTING RWYS, RWYS 10 AND 14 WITH ACFT IN POS BOTH RWYS. ACFT ON RWY 14 GIVEN TKOF CLRNC AND BOTH ACFT BEGAN TKOF ROLL. THE ACFT ON RWY 10 ABORTED HIS TKOF WHEN HE SAW US ROTATE AND BECAME AIRBORNE IN FRONT OF HIM. TWO FACTORS CONTRIBUTED TO THE CHAIN OF EVENTS THAT CAUSED THIS OCCURRENCE. FIRST, THE ACFT ON RWY 10 PROBABLY DID NOT KNOW THAT BOTH RWYS WERE IN USE FOR TKOF. AND SECOND, THE TWR CTLRS FAILURE TO USE THE PHRASEOLOGY IDENTIFYING THE ACFT ON DIFFERENT RWYS. IF THE CTLR HAD SAID, 'FLT XYZ CLRED FOR TKOF RWY 14,' IT MAY HAVE CUED THE PLT ON THE OTHER RWY THAT A TKOF WAS ABOUT TO OCCUR ON THE OTHER RWY. OR, IF HE HAD SAID, 'FLT XYZ ACFT HOLDING IN POS RWY 10, CLRED FOR TKOF RWY 14,' THIS WOULD HAVE BEEN COMPLETELY DESCRIPTIVE COMMENTARY AND WOULD MOST PROBABLY HAVE CALLED ATTN TO THE FACT THAT BOTH RWYS WERE IN USE. ATC SHOULD DEVELOP AND IMPLEMENT AS STANDARD PROC THIS TYPE OF COMMENTARY. I STRONGLY RECOMMEND ATC TRNING FACS BEGIN THIS IMPLEMENTATION AS SOON AS POSSIBLE. SUPPLEMENTAL INFO FROM ACN 96764: THE ARPT BLDG KEPT US FROM SEEING EACH OTHER. SUPPLEMENTAL INFO FROM ACN 96406: AFTER ARRIVING AT THE DEP END OF RWY 10 WE CALLED READY FOR TKOF TO TWR. WE WERE TOLD TO TAXI INTO POS AND HOLD. NO ACFT IN FRONT, WE WERE #1. HOLDING IN POS WE HEARD CLRED FOR TKOF AND MY COPLT CONFIRMED OUR TRIP NUMBER 'ROLLING.' I PROCEEDED WITH TKOF THRUST AND STARTED MY TKOF ROLL. MY ATTN WAS OF COURSE MAINLY OUTSIDE AND I ALMOST IMMEDIATELY SAW ANOTHER ACFT LIFTING OFF FROM RWY 14. I IMMEDIATELY INITIATED A REJECTED TKOF AND CALLED THE ABORT TO TWR. I RECEIVED NO CALL TO ABORT FROM TWR UP TO THAT POINT. WE NOW UNDERSTAND THAT THE TKOF CLRNC WAS FOR THE OTHER ACFT ON RWY 14.

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.