Narrative:

ILS runway 26R cdg. On letdown into cdg the entire crew was concerned about reported high xwinds at cdg and we did not catch that we misset the inbound course in the ILS window. Turning final and leveling from FL050 to 4000 ft the aircraft did not capture the localizer. We realized it immediately and asked for a vector to reintercept and had just leveled off at 4000 ft. Approach control asked if we had 993 set and asked if we were at 4000 ft. We said yes. He asked again if he had set our altimeters and slowly we realized something was not right. It took a few moments to figure out that we had 2993 and not 993. The non-capturing localizer was adding to the confusion. We made a few small south's across the localizer with no capture as we reset the altimeters and climbed approximately 500 ft to 4000 ft. I; the relief pilot shortly realized the inbound course was misset and corrected it just as the field was coming into view through the clouds. As we were calling field in sight; the controller asked us to fly a go around and began to set us up for a 2ND approach. This one was uneventful. Degaulle approach was very helpful in catching our altitude error almost immediately; even though we kept insisting that we had it right. The 2993 versus 0993 is a written gotcha in our commercial chart pages but we all missed it. If the controller had added zero in front of 993 it would have helped; but that is an option not a requirement in ICAO areas. We all spent a lot of time prior to descent and on descent looking at the wind charts worrying if we would be legal to land and got out of our normal habit patterns and failed to catch the misset inbound course which ended up being very confusing at a critical time in flight. I was actually sitting with the wind chart open waiting for the tower winds to confirm our landing legality and calculate a final approach speed as this all unfolded. This incident was a great reminder of how getting distraction and getting out of your normal routine can lead to problems.

Related reports:

Google
 

Original NASA ASRS Text

Title: B767 CREW MAKES ERRORS SETTING INBOUND COURSE AND QNH ON APCH TO LFPG.

Narrative: ILS RWY 26R CDG. ON LETDOWN INTO CDG THE ENTIRE CREW WAS CONCERNED ABOUT RPTED HIGH XWINDS AT CDG AND WE DID NOT CATCH THAT WE MISSET THE INBOUND COURSE IN THE ILS WINDOW. TURNING FINAL AND LEVELING FROM FL050 TO 4000 FT THE ACFT DID NOT CAPTURE THE LOC. WE REALIZED IT IMMEDIATELY AND ASKED FOR A VECTOR TO REINTERCEPT AND HAD JUST LEVELED OFF AT 4000 FT. APCH CTL ASKED IF WE HAD 993 SET AND ASKED IF WE WERE AT 4000 FT. WE SAID YES. HE ASKED AGAIN IF HE HAD SET OUR ALTIMETERS AND SLOWLY WE REALIZED SOMETHING WAS NOT RIGHT. IT TOOK A FEW MOMENTS TO FIGURE OUT THAT WE HAD 2993 AND NOT 993. THE NON-CAPTURING LOC WAS ADDING TO THE CONFUSION. WE MADE A FEW SMALL S'S ACROSS THE LOC WITH NO CAPTURE AS WE RESET THE ALTIMETERS AND CLBED APPROX 500 FT TO 4000 FT. I; THE RELIEF PLT SHORTLY REALIZED THE INBOUND COURSE WAS MISSET AND CORRECTED IT JUST AS THE FIELD WAS COMING INTO VIEW THROUGH THE CLOUDS. AS WE WERE CALLING FIELD IN SIGHT; THE CTLR ASKED US TO FLY A GAR AND BEGAN TO SET US UP FOR A 2ND APCH. THIS ONE WAS UNEVENTFUL. DEGAULLE APCH WAS VERY HELPFUL IN CATCHING OUR ALT ERROR ALMOST IMMEDIATELY; EVEN THOUGH WE KEPT INSISTING THAT WE HAD IT RIGHT. THE 2993 VERSUS 0993 IS A WRITTEN GOTCHA IN OUR COMMERCIAL CHART PAGES BUT WE ALL MISSED IT. IF THE CTLR HAD ADDED ZERO IN FRONT OF 993 IT WOULD HAVE HELPED; BUT THAT IS AN OPTION NOT A REQUIREMENT IN ICAO AREAS. WE ALL SPENT A LOT OF TIME PRIOR TO DSCNT AND ON DSCNT LOOKING AT THE WIND CHARTS WORRYING IF WE WOULD BE LEGAL TO LAND AND GOT OUT OF OUR NORMAL HABIT PATTERNS AND FAILED TO CATCH THE MISSET INBOUND COURSE WHICH ENDED UP BEING VERY CONFUSING AT A CRITICAL TIME IN FLT. I WAS ACTUALLY SITTING WITH THE WIND CHART OPEN WAITING FOR THE TWR WINDS TO CONFIRM OUR LNDG LEGALITY AND CALCULATE A FINAL APCH SPD AS THIS ALL UNFOLDED. THIS INCIDENT WAS A GREAT REMINDER OF HOW GETTING DISTR AND GETTING OUT OF YOUR NORMAL ROUTINE CAN LEAD TO PROBS.

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.