Narrative:

At approximately XA00, my B737 was cleared into position to hold on runway 27L. After several mins, the tower issued a clearance for an immediate takeoff. I immediately turned on the landing lights and the before takeoff checklist was called complete. It was the first officer's takeoff, so he advanced the throttles to 40 percent and after momentary stabilization, in accordance with the OM, he pressed the toga button and the throttles began advancing to the takeoff position. Just prior to reaching takeoff power, the tower cancelled our takeoff clearance and I immediately took the throttles and aborted the takeoff. I estimated the speed to be less than 50 KTS IAS, but did not note the exact speed due to the suddenness of the abort. The aircraft stopped approximately 100 feet short of the intersecting runway 30. I then observed an aircraft cross the intersection of my runway and runway 30 for landing, approximately 50 feet in the air. It is quite possible that if we did not abort, my aircraft would have been directly beneath or just past the landing aircraft. We were then issued another takeoff clearance and proceeded from the position at which we had stopped, since we still had over 12000 ft of runway available and brake heating was not a factor. Supplemental information from acn 539812: this writer was in an airbus 300 holding short of runway 27L with a B737 in position and holding for take off on runway 27L. An airbus 300 was on short final to runway 30 when tower controller cleared to take off runway 27L. I estimate that he accelerated to about 40-50 KTS when tower called for him to abort his take off due to landing traffic on runway 30. If the B737 were to have continued, the airbus would have most likely overflown the B737. This is a classic runway incursion. Callback conversation with reporter revealed the following information: company advised reporter that they would take the matter up with mia, but had heard nothing recently. Reporter believes that mia is running their traffic 'way too tight', which contributed to 'these type of incidents.'

Google
 

Original NASA ASRS Text

Title: MIA TWR ISSUES TKOF ABORT TO A DEPARTING B737 ON RWY 27L AS AN A300 LANDS ON INTERSECTION RWY 30.

Narrative: AT APPROX XA00, MY B737 WAS CLRED INTO POS TO HOLD ON RWY 27L. AFTER SEVERAL MINS, THE TWR ISSUED A CLRNC FOR AN IMMEDIATE TKOF. I IMMEDIATELY TURNED ON THE LNDG LIGHTS AND THE BEFORE TKOF CHKLIST WAS CALLED COMPLETE. IT WAS THE FO'S TKOF, SO HE ADVANCED THE THROTTLES TO 40 PERCENT AND AFTER MOMENTARY STABILIZATION, IAW THE OM, HE PRESSED THE TOGA BUTTON AND THE THROTTLES BEGAN ADVANCING TO THE TKOF POS. JUST PRIOR TO REACHING TKOF PWR, THE TWR CANCELLED OUR TKOF CLRNC AND I IMMEDIATELY TOOK THE THROTTLES AND ABORTED THE TKOF. I ESTIMATED THE SPEED TO BE LESS THAN 50 KTS IAS, BUT DID NOT NOTE THE EXACT SPEED DUE TO THE SUDDENNESS OF THE ABORT. THE ACFT STOPPED APPROX 100 FEET SHORT OF THE INTERSECTING RWY 30. I THEN OBSERVED AN ACFT CROSS THE INTERSECTION OF MY RWY AND RWY 30 FOR LNDG, APPROX 50 FEET IN THE AIR. IT IS QUITE POSSIBLE THAT IF WE DID NOT ABORT, MY ACFT WOULD HAVE BEEN DIRECTLY BENEATH OR JUST PAST THE LNDG ACFT. WE WERE THEN ISSUED ANOTHER TKOF CLRNC AND PROCEEDED FROM THE POS AT WHICH WE HAD STOPPED, SINCE WE STILL HAD OVER 12000 FT OF RWY AVAILABLE AND BRAKE HEATING WAS NOT A FACTOR. SUPPLEMENTAL INFO FROM ACN 539812: THIS WRITER WAS IN AN AIRBUS 300 HOLDING SHORT OF RWY 27L WITH A B737 IN POS AND HOLDING FOR TAKE OFF ON RWY 27L. AN AIRBUS 300 WAS ON SHORT FINAL TO RWY 30 WHEN TWR CONTROLLER CLRED TO TAKE OFF RWY 27L. I ESTIMATE THAT HE ACCELERATED TO ABOUT 40-50 KTS WHEN TWR CALLED FOR HIM TO ABORT HIS TAKE OFF DUE TO LNDG TFC ON RWY 30. IF THE B737 WERE TO HAVE CONTINUED, THE AIRBUS WOULD HAVE MOST LIKELY OVERFLOWN THE B737. THIS IS A CLASSIC RWY INCURSION. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: COMPANY ADVISED RPTR THAT THEY WOULD TAKE THE MATTER UP WITH MIA, BUT HAD HEARD NOTHING RECENTLY. RPTR BELIEVES THAT MIA IS RUNNING THEIR TFC 'WAY TOO TIGHT', WHICH CONTRIBUTED TO 'THESE TYPE OF INCIDENTS.'

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.