Narrative:

During night time operations, mia tower issued us position and hold with a company airbus on 5 mi final. Expedited to position and hold on 9L expecting a takeoff clearance as soon as previous airplane that had taken off is clear of ground. A distraction occurs when tower is trying to reposition aircraft to runway 12 from runway 9L. The aircraft, an air carrier airbus I believe, was not sure if they could reposition to runway 12 and there were several xmissions back and forth. In the meantime we were forgotten. We finally were able to tell tower we were in position and hold. He realized the problem and told company airbus to go around. Not sure how close company airbus came but I would guess less than a thousand ft. Tower was working all three runways with takeoffs and lndgs going on with each of them and repositioning aircraft for min ground time. His work load was too high. There was a controller switch about 5 min before event happened. Supplemental information from acn 567778: maintaining radio situational awareness prevented a runway conflict. Callback conversation with reporter revealed the following information: this was early evening with good WX and visibility of 10 miles or so. Even though a foreign carrier was involved there appeared to be no difficulty with language differences or accents. After the reminder to the local controller of the approaching conflict the situation was handled in a professional manner almost as a non event.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ACR ON FINAL TO RWY 9L AT MIA HAS LNDG CLRNC CANCELLED WHEN THE ACFT IN POSITION AND HOLD REMINDS THE LOCAL CTLR OF THEIR POS AND LACK OF TKOF CLRNC.

Narrative: DURING NIGHT TIME OPS, MIA TWR ISSUED US POS AND HOLD WITH A COMPANY AIRBUS ON 5 MI FINAL. EXPEDITED TO POSITION AND HOLD ON 9L EXPECTING A TKOF CLRNC AS SOON AS PREVIOUS AIRPLANE THAT HAD TAKEN OFF IS CLEAR OF GND. A DISTRACTION OCCURS WHEN TWR IS TRYING TO REPOSITION ACFT TO RWY 12 FROM RWY 9L. THE ACFT, AN ACR AIRBUS I BELIEVE, WAS NOT SURE IF THEY COULD REPOSITION TO RWY 12 AND THERE WERE SEVERAL XMISSIONS BACK AND FORTH. IN THE MEANTIME WE WERE FORGOTTEN. WE FINALLY WERE ABLE TO TELL TWR WE WERE IN POS AND HOLD. HE REALIZED THE PROB AND TOLD COMPANY AIRBUS TO GO AROUND. NOT SURE HOW CLOSE COMPANY AIRBUS CAME BUT I WOULD GUESS LESS THAN A THOUSAND FT. TWR WAS WORKING ALL THREE RWYS WITH TKOFS AND LNDGS GOING ON WITH EACH OF THEM AND REPOSITIONING ACFT FOR MIN GND TIME. HIS WORK LOAD WAS TOO HIGH. THERE WAS A CTLR SWITCH ABOUT 5 MIN BEFORE EVENT HAPPENED. SUPPLEMENTAL INFO FROM ACN 567778: MAINTAINING RADIO SITUATIONAL AWARENESS PREVENTED A RWY CONFLICT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THIS WAS EARLY EVENING WITH GOOD WX AND VIS OF 10 MILES OR SO. EVEN THOUGH A FOREIGN CARRIER WAS INVOLVED THERE APPEARED TO BE NO DIFFICULTY WITH LANGUAGE DIFFERENCES OR ACCENTS. AFTER THE REMINDER TO THE LOCAL CTLR OF THE APCHING CONFLICT THE SIT WAS HANDLED IN A PROFESSIONAL MANNER ALMOST AS A NON EVENT.

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.