|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1801 To 2400|
|Locale Reference||airport : egll.airport|
|Altitude||msl bound lower : 3000|
msl bound upper : 4000
|Operator||common carrier : air carrier|
|Make Model Name||B777-200|
|Operating Under FAR Part||Part 121|
|Navigation In Use||ils localizer & glide slope : 27r|
|Flight Phase||descent : approach|
|Route In Use||approach : instrument precision|
|Affiliation||company : air carrier|
|Function||flight crew : first officer|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Anomaly||non adherence : clearance|
non adherence : company policies
non adherence : published procedure
other spatial deviation
|Independent Detector||other flight crewa|
|Resolutory Action||controller : issued alert|
flight crew : returned to original clearance
flight crew : returned to intended or assigned course
|Problem Areas||ATC Human Performance|
Flight Crew Human Performance
|Primary Problem||Flight Crew Human Performance|
Initially; we set up for the ILS runway 27L egll. When I selected the approach from the database at the time we received erroneous ILS lock on so I decided to manually select the ILS course and frequency on the navigation radial page. We were subsequently given the ILS approach to runway 27R as they were using the left side for departures. I reselected the ILS for the right side and we were given an intercept heading to the localizer. Simply put; I forgot to delete the manually tuned ILS frequency for the left side so the aircraft did not intercept the runway 27R localizer and we went through the final approach course. Passing through the course tower informed us that we had gone through the localizer and gave us a heading back to intercept. There was no traffic conflict and we intercepted the runway 27R localizer and completed the landing uneventfully. It was my mistake and mine alone as I should have deleted the manually input localizer frequency and also should have realized that the wrong localizer frequency was displayed on my pfd. The short amount of time given the approach change and trying to accomplish the before landing checklist distraction me from properly tuning and identing the proper localizer frequency. I also realize that manually tuning a localizer frequency at an airport where runway and approach changes occur often is not a good idea.
Original NASA ASRS Text
Title: AN ACR PILOT APCHING EGLL FAILED TO REMOVE A MANUALLY SELECTED ILS FREQ AND ACQUIRED THE ILS LOC TO THE WRONG RWY.
Narrative: INITIALLY; WE SET UP FOR THE ILS RWY 27L EGLL. WHEN I SELECTED THE APCH FROM THE DATABASE AT THE TIME WE RECEIVED ERRONEOUS ILS LOCK ON SO I DECIDED TO MANUALLY SELECT THE ILS COURSE AND FREQ ON THE NAV RADIAL PAGE. WE WERE SUBSEQUENTLY GIVEN THE ILS APCH TO RWY 27R AS THEY WERE USING THE L SIDE FOR DEPS. I RESELECTED THE ILS FOR THE R SIDE AND WE WERE GIVEN AN INTERCEPT HDG TO THE LOC. SIMPLY PUT; I FORGOT TO DELETE THE MANUALLY TUNED ILS FREQ FOR THE L SIDE SO THE ACFT DID NOT INTERCEPT THE RWY 27R LOC AND WE WENT THROUGH THE FINAL APCH COURSE. PASSING THROUGH THE COURSE TWR INFORMED US THAT WE HAD GONE THROUGH THE LOC AND GAVE US A HDG BACK TO INTERCEPT. THERE WAS NO TFC CONFLICT AND WE INTERCEPTED THE RWY 27R LOC AND COMPLETED THE LNDG UNEVENTFULLY. IT WAS MY MISTAKE AND MINE ALONE AS I SHOULD HAVE DELETED THE MANUALLY INPUT LOC FREQ AND ALSO SHOULD HAVE REALIZED THAT THE WRONG LOC FREQ WAS DISPLAYED ON MY PFD. THE SHORT AMOUNT OF TIME GIVEN THE APCH CHANGE AND TRYING TO ACCOMPLISH THE BEFORE LNDG CHKLIST DISTR ME FROM PROPERLY TUNING AND IDENTING THE PROPER LOC FREQ. I ALSO REALIZE THAT MANUALLY TUNING A LOC FREQ AT AN ARPT WHERE RWY AND APCH CHANGES OCCUR OFTEN IS NOT A GOOD IDEA.
Data retrieved from NASA's ASRS site as of January 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.