Narrative:

We were on radar vectors runway 27L, atl, conflicting traffic runway 26R. We were given 330 degrees radar vectors along with controller's request for maximum descent rate. We got a TCASII advisory descending through 3500 ft for 2500 ft. Aircraft was in sight. Approximately same time, controller gave us 250 degree heading to intercept localizer (obviously knowing we were going through localizer). Requested good rate of turn and also advised us of the traffic. Maximum bank angle with full speed brake maximum descent. Late vector to intercept caused localizer overshoot even with maximum bank. Note: conflicting traffic always in sight. Controller's attempts (repeatedly) to contact another flight could have led to other duties being delayed a bit.

Google
 

Original NASA ASRS Text

Title: ATC VECTORS CAUSE WDB TO OVERSHOOT LOC.

Narrative: WE WERE ON RADAR VECTORS RWY 27L, ATL, CONFLICTING TFC RWY 26R. WE WERE GIVEN 330 DEGS RADAR VECTORS ALONG WITH CTLR'S REQUEST FOR MAX DSCNT RATE. WE GOT A TCASII ADVISORY DSNDING THROUGH 3500 FT FOR 2500 FT. ACFT WAS IN SIGHT. APPROX SAME TIME, CTLR GAVE US 250 DEG HDG TO INTERCEPT LOC (OBVIOUSLY KNOWING WE WERE GOING THROUGH LOC). REQUESTED GOOD RATE OF TURN AND ALSO ADVISED US OF THE TFC. MAX BANK ANGLE WITH FULL SPD BRAKE MAX DSCNT. LATE VECTOR TO INTERCEPT CAUSED LOC OVERSHOOT EVEN WITH MAX BANK. NOTE: CONFLICTING TFC ALWAYS IN SIGHT. CTLR'S ATTEMPTS (REPEATEDLY) TO CONTACT ANOTHER FLT COULD HAVE LED TO OTHER DUTIES BEING DELAYED A BIT.

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.