B767 flight crew reports that their FMC data base which was checked and current prior to departure; contained no arrivals or approaches for LFPG. The crew also could not find a segment of the arrival procedure which was on a separate chart; necessitating a request for vectors to the ILS.

Date: 2011-02 · Aircraft: B767-200 · Phase: descent

Anomalies: aircraft-equipment-problem-less-severe|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance

Synopsis

B767 flight crew reports that their FMC data base which was checked and current prior to departure; contained no arrivals or approaches for LFPG. The crew also could not find a segment of the arrival procedure which was on a separate chart; necessitating a request for vectors to the ILS.

Narrative

On arrival into LFPG; approximately 5 miles prior to flying the last section of DIEPPE 4W to 27R via MERUE Intersection; ATC cleared us for the 'MERUE ILS 27R' approach. The arrival ends at MERUE with no further instructions. Looked through the entire LFPG arrival and approaches for 27R appendix and were unable to find any 27R approaches (ILS's) with a MERUE transition. As we got closer to the MERUE fix; I decided to call ATC to get a clarification. The frequency was very busy at the time and couldn't get through after several tries. Arrival over MERUE we finally got through and asked ATC for clarification and next fix after MERUE. They said it was CRL so we started a turn towards that and at that time ATC gave us a heading. I then asked them if they had time for a question and they said 'go ahead'. [I] asked them if they could clarify 'MERUE ILS 27R'. ATC said it was a published standard approach. We continued on the assigned heading with vectors for the ILS 27R approach without further incident.

Second reporter narrative

Prior to departure current FMC database was confirmed. On arrival descent to LFPG; clearance limit was DPE VOR on western coast of France. When ATC was queried for further clearance; it was discovered by crew that assigned arrival DIEPPE 4W was not in FMC database. Arrival waypoints and altitude restrictions were manually entered and flown to MERUE waypoint after which; ATC cleared us for the MERUE ILS 27R arrival (which we later discovered is on a different chart) which was also not in the FMC database. In fact; NO arrivals or approaches for the destination airport existed in FMC database. Due to limited experience with this airport and time constraints we were unable to locate the appropriate chart. That fact; combined with lack of procedures in FMC database; led us to request vectors to ILS 27R final approach course; which we received. ILS was flown uneventfully to visual conditions and landing was normal. French ATC was very responsive and professional.Aircraft should not be dispatched with incomplete database information installed. Crews should be more thoroughly informed of chart format which requires multiple charts for arrival procedure. As of our return flight the FMC database information was still missing for LFPG.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.