Narrative:

About a mi inside the marker for runway 27L at mia, the captain asked if we had been turned over to tower by approach control. The first officer said no. Captain said go to tower. The first officer was very new in the seat coming from widebody transport engineer (his prior backgnd military). He had trouble finding tower frequency. In the meantime, there was traffic on our runway, so the captain began to s-turn. The first officer took an exceptionally long time locating the frequency and it was now becoming evident that we were going to have to go around. Captain said 'tell tower we're going around' and the first officer had dialed in ground control, not tower. In the go around, he switched back to approach, who gave us go around instructions and said go to tower. The first officer finally got tower and they were upset (understandably). Tower vectored us for another approach. On downwind the flight engineer called the field and captain and first officer responded 'in sight.' tower asked if we had field and traffic on final in sight. The first officer responded 'affirmative' although the captain did not have the traffic. On base, our TCASII alerted 'traffic, traffic' to the first officer and the flight engineer. It was obvious this was parallel traffic to runway 27R. We saw the traffic at 1-2 O'clock, but the captain was concentrating on the TCASII alert, and overshot runway 27L. Well, now the traffic is at 12:30 - 1 O'clock position and less than 1 mi and the TCASII gave an RA, so the captain immediately executed a hard right turn to break off the approach. He told the first officer to 'tell the tower we're doing a right 360 degree turn. Request vectors for the approach.'

Google
 

Original NASA ASRS Text

Title: AN ACR LGT FOULED UP ITS COMS IN THE LNDG PATTERN. WHEN THEY GOT THAT STRAIGHTENED OUT, THEY HAD A TCASII ADVENTURE.

Narrative: ABOUT A MI INSIDE THE MARKER FOR RWY 27L AT MIA, THE CAPT ASKED IF WE HAD BEEN TURNED OVER TO TWR BY APCH CTL. THE FO SAID NO. CAPT SAID GO TO TWR. THE FO WAS VERY NEW IN THE SEAT COMING FROM WDB ENGINEER (HIS PRIOR BACKGND MIL). HE HAD TROUBLE FINDING TWR FREQ. IN THE MEANTIME, THERE WAS TFC ON OUR RWY, SO THE CAPT BEGAN TO S-TURN. THE FO TOOK AN EXCEPTIONALLY LONG TIME LOCATING THE FREQ AND IT WAS NOW BECOMING EVIDENT THAT WE WERE GOING TO HAVE TO GAR. CAPT SAID 'TELL TWR WE'RE GOING AROUND' AND THE FO HAD DIALED IN GND CTL, NOT TWR. IN THE GAR, HE SWITCHED BACK TO APCH, WHO GAVE US GAR INSTRUCTIONS AND SAID GO TO TWR. THE FO FINALLY GOT TWR AND THEY WERE UPSET (UNDERSTANDABLY). TWR VECTORED US FOR ANOTHER APCH. ON DOWNWIND THE FE CALLED THE FIELD AND CAPT AND FO RESPONDED 'IN SIGHT.' TWR ASKED IF WE HAD FIELD AND TFC ON FINAL IN SIGHT. THE FO RESPONDED 'AFFIRMATIVE' ALTHOUGH THE CAPT DID NOT HAVE THE TFC. ON BASE, OUR TCASII ALERTED 'TFC, TFC' TO THE FO AND THE FE. IT WAS OBVIOUS THIS WAS PARALLEL TFC TO RWY 27R. WE SAW THE TFC AT 1-2 O'CLOCK, BUT THE CAPT WAS CONCENTRATING ON THE TCASII ALERT, AND OVERSHOT RWY 27L. WELL, NOW THE TFC IS AT 12:30 - 1 O'CLOCK POS AND LESS THAN 1 MI AND THE TCASII GAVE AN RA, SO THE CAPT IMMEDIATELY EXECUTED A HARD R TURN TO BREAK OFF THE APCH. HE TOLD THE FO TO 'TELL THE TWR WE'RE DOING A R 360 DEG TURN. REQUEST VECTORS FOR THE APCH.'

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.