Medium large transport flight crew flew through final due to being tuned to the wrong ILS frequency.

Attributes
ACN	502930
Time
Date	200103
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : atl.airport
State Reference	GA
Altitude	msl single value : 5000
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : atl.tracon
Operator	common carrier : air carrier
Make Model Name	MD-88
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 26r
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 8000 flight time type : 1200
ASRS Report	502930
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	controller : issued alert flight crew : returned to intended or assigned course
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On the final leg of a 12 1/2 hour duty day, we were on vectors to intercept final approach to runway 26R (north runway). The runway 27L approach was mistakenly programmed in our FMS along with its ILS frequency. So our vector to join runway 26R actually joined us to runway 27L. Approach saw us going through final and gave us a vector to join thinking we just overshot. We thought we were right on course. When he said it appeared we were on runway 27L, we quickly turned right to join runway 26R and switched frequencys. Fortunately, there was no conflict and no traffic on TCASII. We called approach on the ground and they said there was no problem. Complacency and fatigue were factors in this problem. We were flying an approach we have done hundreds of times. You push the button for the approach to be flown, the frequency pops up, you set it and everything is done. The first officer briefed the correct approach, but I didn't xchk the loaded FMS or frequency.

Original NASA ASRS Text

Title: MLG FLC FLEW THROUGH FINAL DUE TO BEING TUNED TO THE WRONG ILS FREQ.

Narrative: ON THE FINAL LEG OF A 12 1/2 HR DUTY DAY, WE WERE ON VECTORS TO INTERCEPT FINAL APCH TO RWY 26R (N RWY). THE RWY 27L APCH WAS MISTAKENLY PROGRAMMED IN OUR FMS ALONG WITH ITS ILS FREQ. SO OUR VECTOR TO JOIN RWY 26R ACTUALLY JOINED US TO RWY 27L. APCH SAW US GOING THROUGH FINAL AND GAVE US A VECTOR TO JOIN THINKING WE JUST OVERSHOT. WE THOUGHT WE WERE RIGHT ON COURSE. WHEN HE SAID IT APPEARED WE WERE ON RWY 27L, WE QUICKLY TURNED R TO JOIN RWY 26R AND SWITCHED FREQS. FORTUNATELY, THERE WAS NO CONFLICT AND NO TFC ON TCASII. WE CALLED APCH ON THE GND AND THEY SAID THERE WAS NO PROB. COMPLACENCY AND FATIGUE WERE FACTORS IN THIS PROB. WE WERE FLYING AN APCH WE HAVE DONE HUNDREDS OF TIMES. YOU PUSH THE BUTTON FOR THE APCH TO BE FLOWN, THE FREQ POPS UP, YOU SET IT AND EVERYTHING IS DONE. THE FO BRIEFED THE CORRECT APCH, BUT I DIDN'T XCHK THE LOADED FMS OR FREQ.

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.