A md-11 crew discovered on approach that they had set the lfpg ILS 27L frequency in the ILS instead ...

Narrative:

Arriving into lfpg; we were being vectored to the ILS 27R. The captain had briefed the approach (normally the flying pilot briefs; but we decided to; at least; brief the CAT ii information just in case the weather would happen to take a drastic turn for the worse) but we noticed during the brief our minimums differed by 10 ft. He realized he was looking at the chart for [runway] 27L. So we reloaded and briefed; double checking our navigation display. Everything showed [runway] 27R. We were cleared to intercept the localizer beyond where the FMS auto-tunes the frequency; so the captain manually inserted it on the ILS page. Once we intercepted and started tracking the localizer; approach asked us to confirm our runway. When we told him [runway] 27R; he said we were lined up and tracking on [runway] 27L. We all three (we had an international relief officer) checked again and our information on the navigation display still showed the right. The international relief officer finally noticed that on of the ids didn't read 'pnw' (the identification for ILS 27R). I disconnected the autopilot and steered back to the right while the captain reinserted the ILS another time. It tuned; and we landed without any further problem. [Neither] approach nor tower ever mentioned anything else about it. After we blocked it; we spent several minutes de-briefing trying to figure out what happened. We really don't know. All our navigation displays indicated [runway] 27R. The only thing we could think of is that initially; when we were so far out and had to manually tune the ILS; he may have put in [runway] 27L. Our navigation display showing [runway] 27R; since that was what we'd loaded into the FMS. About the only thing I can think of is that on our approach checklist; we didn't notice the three letter identification not matching up. (Not unheard of; but more the exception than the rule; though; is that in the corner of that chart; there are two ids. One for the ILS and one for the VOR that can be a bit confusing.) we should be very careful to verify each letter; not just checking to see if an identification is there.

Original NASA ASRS Text

Title: A MD-11 crew discovered on approach that they had set the LFPG ILS 27L frequency in the ILS instead of the Runway 27R but the IRO caught the error before ATC and not track deviation resulted.

Narrative: Arriving into LFPG; we were being vectored to the ILS 27R. The Captain had briefed the approach (normally the flying pilot briefs; but we decided to; at least; brief the CAT II information just in case the weather would happen to take a drastic turn for the worse) but we noticed during the brief our minimums differed by 10 FT. He realized he was looking at the chart for [Runway] 27L. So we reloaded and briefed; double checking our NAV display. Everything showed [Runway] 27R. We were cleared to intercept the LOC beyond where the FMS auto-tunes the frequency; so the Captain manually inserted it on the ILS page. Once we intercepted and started tracking the localizer; Approach asked us to confirm our runway. When we told him [Runway] 27R; he said we were lined up and tracking on [Runway] 27L. We all three (we had an IRO) checked again and our information on the NAV display still showed the right. The IRO finally noticed that on of the IDs didn't read 'PNW' (the ID for ILS 27R). I disconnected the autopilot and steered back to the right while the Captain reinserted the ILS another time. It tuned; and we landed without any further problem. [Neither] Approach nor Tower ever mentioned anything else about it. After we blocked it; we spent several minutes de-briefing trying to figure out what happened. We really don't know. All our NAV displays indicated [Runway] 27R. The only thing we could think of is that initially; when we were so far out and had to manually tune the ILS; he may have put in [Runway] 27L. Our NAV display showing [Runway] 27R; since that was what we'd loaded into the FMS. About the only thing I can think of is that on our approach checklist; we didn't notice the three letter ID not matching up. (Not unheard of; but more the exception than the rule; though; is that in the corner of that chart; there are two IDs. One for the ILS and one for the VOR that can be a bit confusing.) We should be very careful to verify each letter; not just checking to see if an ID is there.

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

Attributes
ACN	1067787
Time
Date	201302
Place
Locale Reference	LFPG.Airport
State Reference	FO
Environment
Light	Daylight
Aircraft 1
Make Model Name	MD-11
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Flight Plan	IFR
Component
Aircraft Component	ILS/VOR
Person 1
Function	Pilot Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

A md-11 crew discovered on approach that they had set the lfpg ILS 27L frequency in the ILS instead of the runway 27R but the international relief officer caught the error before ATC and not track deviation resulted.