Date: 201309
Local time of day: 1201-1800
Location: MIA.Airport, FL
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class B MIA
ATC / advisory: TRACON MIA
Second aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Distraction; Confusion; Communication Breakdown
Second reporter function: Pilot Flying; First Officer
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Automation Aircraft TA; Automation Aircraft RA; Person Flight Crew; Person Observer
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Environment - Non Weather Related; Airport; Procedure; Human Factors
Primary problem: Ambiguous

Narrative: We received clearance from Miami Approach Control to proceed direct to SARCO Intersection; maintain 3;000 FT until established on the localizer; and cleared ILS Runway 27 approach. Approximately 1-2 NM outside of SARCO; Miami Approach reported that we had traffic from the north; turning base to final for Runway 26L into MIA. The pilot not flying; acknowledged the Approach Controller that we were 'looking' for traffic and the traffic was visible on TCAS. Shortly after this transmission; the additional pilot sitting in the observers seat made visual contact with the traffic and cautioned me that it looks like the traffic (an A320) is overshooting and turning late for Runway 26L. I made visual contact with the traffic and agreed the traffic was converging on our course. At this time it appeared the A320 was flying a 200 heading and was way beyond (south) of the extended centerline for 26L and probably going to penetrate/extend through the extended centerline for our runway; 27. During this time we received a 'TRAFFIC; TRAFFIC' TA Advisory followed shortly by a RA to 'DESCEND; DESCEND.' The autopilot was already disconnected for the approach; so I maneuvered the aircraft outside the recommended red vertical guidance bars on the PFD. The pilot not flying transmitted to Miami Approach we were complying with an RA to descend. At this time; the workload in the flight deck was high; and the Approach Controller along with the pilot not flying stepped on responding transmissions resulting in us not hearing the Miami Approach Controller tell us to turn to a 210 degree heading. The pilot not flying reminded the Approach Controller we were complying with an RA and asked to repeat the heading. We complied with the requested heading of 210 degrees and descended to almost 2;300 FT before receiving the TCAS advisory 'CLEAR OF CONFLICT.' During the descending RA maneuver the TCAS also produced a 'MONITOR VERTICAL SPEED' RA and 'ADJUST VERTICAL SPEED' RA commanding us to increase our rate of descent due to the apparent lack of climb from the A320. At our closest separation point; I recall seeing a plus 400 indication on the TCAS traffic block. The A320 was slightly forward of our flight deck window at roughly 400 FT above our aircraft's position just passing south of the extended centerline for Runway 27 before climbing and turning northbound. After our turn to a heading of 210; and descending clear of the conflict; Miami approach told us to discontinue approach and climb to 4;000 FT. The pilot not flying notified we had the field in sight from our current position and we were then cleared a visual approach to Runway 27. The flight landed and completed without any further incident.


Second narrative: [Report narrative contained no additional information.]


Synopsis: An air carrier crew on approach to MIA Runway 27 took evasive action to a TCAS RA during a near miss with an air carrier aircraft which over shot Runway 26L final while descending into the Runway 27 final.