Narrative:

I was issued a taxi into position and hold clearance from hou tower for runway 30R. At the time tower was also working ground control. I was told to position and hold and expect a wake turbulence delay. After waiting 1 min, I decided it was safe to waive the remainder of the wake delay. I keyed the transmitter and said 'aircraft X will waive the remainder of wake delay.' as I unkeyed the transmitter I heard 'cleared for takeoff, fly runway heading.' not hearing my number, I keyed the microphone and said 'cleared for takeoff runway 30R, fly runway heading aircraft X.' after unkeying the microphone, I heard silence, which normally indicated that my readback was correct. At that point, I instructed my student to begin the takeoff roll. We had traveled approximately 1000 ft down the runway when I looked to my right and saw an air carrier B737 rolling on runway 22 and heard 'aircraft X abort takeoff, abort, abort.' I took control of the airplane and began braking. We stopped approximately 500 ft short of the intersection of runway 30R and runway 22. The B737 also initiated an aborted takeoff on his own. I cleared the runway and was told that I did not have a takeoff clearance. The B737 returned to his gate to have his brakes inspected by maintenance and then continued his flight. Upon returning from the flight, I contacted the tower supervisor to discuss the incident. He told me that my takeoff clearance had probably been perfectly blocked by the B737's transmission for whom the takeoff clearance was intended. I took away a great deal of information from this incident and learned a lot from it. In hindsight, I could have done a better job in clarifying my takeoff clearance, and been more diligent in clearing the crossing runway. And I suppose that the tower controller could have caught my takeoff roll earlier if he was not working the ground frequency at the same time.

Google
 

Original NASA ASRS Text

Title: BLOCKED XMISSIONS AT HOU RESULT IN 2 ACFT STARTING TKOF ROLL FROM INTERSECTING RWYS FOLLOWED BY A REJECTED TKOF BY BOTH ACFT.

Narrative: I WAS ISSUED A TAXI INTO POS AND HOLD CLRNC FROM HOU TWR FOR RWY 30R. AT THE TIME TWR WAS ALSO WORKING GND CTL. I WAS TOLD TO POS AND HOLD AND EXPECT A WAKE TURB DELAY. AFTER WAITING 1 MIN, I DECIDED IT WAS SAFE TO WAIVE THE REMAINDER OF THE WAKE DELAY. I KEYED THE XMITTER AND SAID 'ACFT X WILL WAIVE THE REMAINDER OF WAKE DELAY.' AS I UNKEYED THE XMITTER I HEARD 'CLRED FOR TKOF, FLY RWY HDG.' NOT HEARING MY NUMBER, I KEYED THE MIKE AND SAID 'CLRED FOR TKOF RWY 30R, FLY RWY HDG ACFT X.' AFTER UNKEYING THE MIKE, I HEARD SILENCE, WHICH NORMALLY INDICATED THAT MY READBACK WAS CORRECT. AT THAT POINT, I INSTRUCTED MY STUDENT TO BEGIN THE TKOF ROLL. WE HAD TRAVELED APPROX 1000 FT DOWN THE RWY WHEN I LOOKED TO MY R AND SAW AN ACR B737 ROLLING ON RWY 22 AND HEARD 'ACFT X ABORT TKOF, ABORT, ABORT.' I TOOK CTL OF THE AIRPLANE AND BEGAN BRAKING. WE STOPPED APPROX 500 FT SHORT OF THE INTXN OF RWY 30R AND RWY 22. THE B737 ALSO INITIATED AN ABORTED TKOF ON HIS OWN. I CLRED THE RWY AND WAS TOLD THAT I DID NOT HAVE A TKOF CLRNC. THE B737 RETURNED TO HIS GATE TO HAVE HIS BRAKES INSPECTED BY MAINT AND THEN CONTINUED HIS FLT. UPON RETURNING FROM THE FLT, I CONTACTED THE TWR SUPVR TO DISCUSS THE INCIDENT. HE TOLD ME THAT MY TKOF CLRNC HAD PROBABLY BEEN PERFECTLY BLOCKED BY THE B737'S XMISSION FOR WHOM THE TKOF CLRNC WAS INTENDED. I TOOK AWAY A GREAT DEAL OF INFO FROM THIS INCIDENT AND LEARNED A LOT FROM IT. IN HINDSIGHT, I COULD HAVE DONE A BETTER JOB IN CLARIFYING MY TKOF CLRNC, AND BEEN MORE DILIGENT IN CLRING THE XING RWY. AND I SUPPOSE THAT THE TWR CTLR COULD HAVE CAUGHT MY TKOF ROLL EARLIER IF HE WAS NOT WORKING THE GND FREQ AT THE SAME TIME.

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.