Expecting ILS 28 at atl; B757 first officer discovers during vectors that the approach is ILS prm to runway 27L and course and monitor frequency has not been set causing overshoot.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	775704
Time
Date	200802
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : atl.airport
State Reference	GA
Altitude	msl single value : 3500
Environment
Flight Conditions	Mixed
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : a80.tracon
Operator	common carrier : air carrier
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 28 other
Flight Phase	descent : approach
Route In Use	approach : instrument precision arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 180 flight time total : 8000 flight time type : 1200
ASRS Report	775704
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : returned to intended or assigned course
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We were on vectors for atl runway 28 ILS. We had been set up for ILS runway 27L. I; as the PF and co-pilot; made the changes in set-up but failed to notice I hadn't set the proper front-course for runway 27L and didn't reset it for runway 28. When we were given a heading to intercept the localizer runway 28; I also noticed for the first time we were cleared for an ILS prm approach. We hadn't set in the monitor frequency. As I start to put in the frequency we flew through the runway 28 localizer. I noticed this in fairly short order and immediately and aggressively turned back to centerline but by then we had come to the attention of the controller who gave us instructions to descend and back to centerline. We continued the approach for an uneventful landing.

Original NASA ASRS Text

Title: EXPECTING ILS 28 AT ATL; B757 FO DISCOVERS DURING VECTORS THAT THE APPROACH IS ILS PRM TO RWY 27L AND COURSE AND MONITOR FREQUENCY HAS NOT BEEN SET CAUSING OVERSHOOT.

Narrative: WE WERE ON VECTORS FOR ATL RWY 28 ILS. WE HAD BEEN SET UP FOR ILS RWY 27L. I; AS THE PF AND CO-PLT; MADE THE CHANGES IN SET-UP BUT FAILED TO NOTICE I HADN'T SET THE PROPER FRONT-COURSE FOR RWY 27L AND DIDN'T RESET IT FOR RWY 28. WHEN WE WERE GIVEN A HDG TO INTERCEPT THE LOC RWY 28; I ALSO NOTICED FOR THE FIRST TIME WE WERE CLRED FOR AN ILS PRM APCH. WE HADN'T SET IN THE MONITOR FREQ. AS I START TO PUT IN THE FREQUENCY WE FLEW THROUGH THE RWY 28 LOC. I NOTICED THIS IN FAIRLY SHORT ORDER AND IMMEDIATELY AND AGGRESSIVELY TURNED BACK TO CTRLINE BUT BY THEN WE HAD COME TO THE ATTENTION OF THE CTLR WHO GAVE US INSTRUCTIONS TO DESCEND AND BACK TO CTRLINE. WE CONTINUED THE APCH FOR AN UNEVENTFUL LNDG.

Data retrieved from NASA's ASRS site as of May 2009 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.