Narrative:

Aircraft X was cleared for takeoff by lax tower after being in position and hold on the runway. Immediately as we began the takeoff roll, we heard the tower clear a flight, which had just landed on runway 24R, to cross runway 24L (our runway) at taxiway aa. The jet did not answer the tower. After the second tower call I aborted our takeoff (below 60 KIAS) because I did not think it was safe to continue under these confusing conditions -- another airplane being cleared to cross a runway after a plane has started its takeoff roll and without positive communication between the parties involved. After the slow speed abort, we cleared the runway and returned to takeoff again. Anyone reviewing the tapes of this incident can clearly see that this tower controller was getting behind the extreme volume of inbound and outbound traffic. Before he cleared us into position to hold, he started to clear us for takeoff about 15 seconds (very close) to another air carrier flight which just started its takeoff roll on runway 24L. He did this without visual confirmation of the Z plane. Anyway, he realized this and just cleared us into position and hold. Meanwhile planes were getting within 3 mi of landing on runway 24L and runway 24R making this a very congested time. Another factor contributing to all this is the missed radio calls and poor radio discipline exhibited throughout the airport. In hindsight, I do believe (I have no way of knowing) that the plane cleared to cross runway 24L at taxiway aa might have seen this conflict also, thus the reason he never answered the tower. He might have been taking the time to analyze a bad clearance -- I hope so.

Related reports:

Google
 

Original NASA ASRS Text

Title: MD80 FLC INITIATES TKOF ABORT WHEN HEARING LAX GND CTL TWICE CLR ANOTHER ACR DOWNFIELD TO CROSS THE RWY ON WHICH THE MD80 WAS CLRED FOR TKOF.

Narrative: ACFT X WAS CLRED FOR TKOF BY LAX TWR AFTER BEING IN POS AND HOLD ON THE RWY. IMMEDIATELY AS WE BEGAN THE TKOF ROLL, WE HEARD THE TWR CLR A FLT, WHICH HAD JUST LANDED ON RWY 24R, TO CROSS RWY 24L (OUR RWY) AT TXWY AA. THE JET DID NOT ANSWER THE TWR. AFTER THE SECOND TWR CALL I ABORTED OUR TKOF (BELOW 60 KIAS) BECAUSE I DID NOT THINK IT WAS SAFE TO CONTINUE UNDER THESE CONFUSING CONDITIONS -- ANOTHER AIRPLANE BEING CLRED TO CROSS A RWY AFTER A PLANE HAS STARTED ITS TKOF ROLL AND WITHOUT POSITIVE COM BTWN THE PARTIES INVOLVED. AFTER THE SLOW SPD ABORT, WE CLRED THE RWY AND RETURNED TO TKOF AGAIN. ANYONE REVIEWING THE TAPES OF THIS INCIDENT CAN CLRLY SEE THAT THIS TWR CTLR WAS GETTING BEHIND THE EXTREME VOLUME OF INBOUND AND OUTBOUND TFC. BEFORE HE CLRED US INTO POS TO HOLD, HE STARTED TO CLR US FOR TKOF ABOUT 15 SECONDS (VERY CLOSE) TO ANOTHER ACR FLT WHICH JUST STARTED ITS TKOF ROLL ON RWY 24L. HE DID THIS WITHOUT VISUAL CONFIRMATION OF THE Z PLANE. ANYWAY, HE REALIZED THIS AND JUST CLRED US INTO POS AND HOLD. MEANWHILE PLANES WERE GETTING WITHIN 3 MI OF LNDG ON RWY 24L AND RWY 24R MAKING THIS A VERY CONGESTED TIME. ANOTHER FACTOR CONTRIBUTING TO ALL THIS IS THE MISSED RADIO CALLS AND POOR RADIO DISCIPLINE EXHIBITED THROUGHOUT THE ARPT. IN HINDSIGHT, I DO BELIEVE (I HAVE NO WAY OF KNOWING) THAT THE PLANE CLRED TO CROSS RWY 24L AT TXWY AA MIGHT HAVE SEEN THIS CONFLICT ALSO, THUS THE REASON HE NEVER ANSWERED THE TWR. HE MIGHT HAVE BEEN TAKING THE TIME TO ANALYZE A BAD CLRNC -- I HOPE SO.

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.