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

Date: 2002-02 · Aircraft: B737-800 · Phase: takeoff

Anomalies: atc-issue-all-types|conflict-ground-conflict|critical|deviation-discrepancy-procedural-published-material-policy

Synopsis

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.'

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.