Widebody; Low Wing; 2 Turbojet Eng
Air Traffic Control Fully Certified
Communication Breakdown; Time Pressure
ATC Issue All Types; Conflict Airborne Conflict; Conflict NMAC; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Air Traffic Control Issued Advisory / Alert
Airport; Procedure
I was working Local 4 in a west bound configuration. We were advertising visuals to Runway 26R; ILS to 27L; and visual approach to Runway 28. An Embraer was joining the Runway 28 final at the final approach fix at the same altitude as a Widebody; flew through his final and approached my final for Runway 27L. The collision alert went off. I immediately issued traffic to the Widebody. If it wasn't for the immediate response of [the other local controller]; I would have had to send the Widebody around on a missed approach. It happened so fast; we had mere seconds to correct a potential collision.This was as close to a near miss as you can come. This happens all day; everyday at Atlanta tower. Arrival A joins the Runway 28 final at the same altitude as an aircraft established on the final for Runway 27L. The aircraft for Runway 28 flies through the final; the collision alert goes off; and we issue traffic. We then hold our breath and hope the Runway 28 aircraft turns tighter to get established on their final. If an aircraft joins the Runway 28 final at a 30 degree intercept; with the traffic in sight for Runway 27L; how can the Runway 28 aircraft keep their traffic in sight?  This is a catastrophic event waiting to happen.  Why are we joining two finals at the same altitude?  Stop joining the Runway 28 final at the same altitude as the Runway 27L traffic.  Stop taking short cuts; and join the Runway 28 final at 10 miles instead of 5 miles.
ATL Local Controller described a conflict between two air carrier aircraft when an Embraer cleared to fly a visual to Runway 28 failed to turn in a timely fashion and threatened a widebody aircraft established on final for Runway 27L.