Narrative:

We were issued a clearance thru ACARS 'runway 27L via opale 3A...' as PF I loaded runway 27L and the opale 3A departure into the FMS. I verified the waypoints in the FMS comparing the data to the opale 3A SID chart. I also verified the waypoints against the dispatch release just as an additional back-up. I then briefed the ACARS clnc with the first officer and finally did a complete briefing of the departure procedure reading from the FMS while the first officer verified all fixes and data looking at the chart. At no time was any error noted at all. After engine start I engaged navigation and verified the fcp was still in navigation mode in conjunction with the before takeoff checklist once cleared onto the runway for takeoff. When lfpg tower cleared us for takeoff on 27L they asked to verify that we had loaded the opale 3A departure. I looked at the FMS and saw - again - that the opale 3A was in fact loaded in the FMS and the first officer acknowledged this fact. Takeoff was normal - nadp 1 using navigation mode from the start of takeoff. As I approached PG270 (the first fix) I selected IAS hold so as to achieve a better turn radius for the turn at that fix; staying around 180 KIAS. After switching to departure control; the controller told us to climb to FL140 (I think) and asked us to expedite thru FL120. Once past PG270 and as we were approaching PG276 (the next waypoint) the controller asked us again to verify the departure we were flying. I again looked at the FMS and verified that we were still on the opale 3A and re-verified that I was in navigation. At this point the controller told us that we were 1.5 miles from our course! He quoted a radial that we weren't tracking and we advised him of the waypoints we were using for the RNAV departure (again exactly what the opale 3A called for). At no time were we more that .2 miles from the magenta line according to our data tag on the navigation display and at no time were we not in navigation during the entire departure phase. The controller did not seem upset but he was adamant that we were well off course and suggested that perhaps we were not properly navigating and/or that our speed was too fast. This discrepancy is really a mystery. My first officer and I reviewed everything again once we were in cruise and just simply can't come up with an explanation other that the controller was wrong or;(much less likely) that the chart and FMS database are not correct.

Google
 

Original NASA ASRS Text

Title: MD11 flight crew departing LFPG on the Oaple 3A RNAV departure is informed by ATC that they are off course. The crew can detect no errors and their map display shows they are on course.

Narrative: We were issued a clearance thru ACARS 'RWY 27L VIA OPALE 3A...' As PF I loaded Runway 27L and the OPALE 3A departure into the FMS. I verified the waypoints in the FMS comparing the data to the OPALE 3A SID chart. I also verified the waypoints against the Dispatch Release just as an additional back-up. I then briefed the ACARS CLNC with the First Officer and finally did a complete briefing of the departure procedure reading from the FMS while the First Officer verified all fixes and data looking at the chart. At no time was any error noted at all. After engine start I engaged NAV and verified the FCP was still in NAV Mode in conjunction with the Before Takeoff Checklist once cleared onto the runway for takeoff. When LFPG Tower cleared us for takeoff on 27L they asked to verify that we had loaded the OPALE 3A departure. I looked at the FMS and saw - again - that the OPALE 3A was in fact loaded in the FMS and the First Officer acknowledged this fact. Takeoff was normal - NADP 1 using NAV MODE from the start of takeoff. As I approached PG270 (the first fix) I selected IAS HOLD so as to achieve a better turn radius for the turn at that fix; staying around 180 KIAS. After switching to Departure Control; the Controller told us to climb to FL140 (I think) and asked us to expedite thru FL120. Once past PG270 and as we were approaching PG276 (the next waypoint) the Controller asked us again to verify the departure we were flying. I again looked at the FMS and verified that we were still on the OPALE 3A and re-verified that I was in NAV. At this point the Controller told us that we were 1.5 miles from our course! He quoted a radial that we weren't tracking and we advised him of the waypoints we were using for the RNAV departure (again exactly what the OPALE 3A called for). At NO TIME were we more that .2 miles from the magenta line according to our data tag on the NAV Display and at no time were we not in NAV during the entire departure phase. The Controller did not seem upset but he was adamant that we were well off course and suggested that perhaps we were not properly navigating and/or that our speed was too fast. This discrepancy is really a mystery. My First Officer and I reviewed everything again once we were in cruise and just simply can't come up with an explanation other that the Controller was wrong or;(much less likely) that the chart and FMS database are not correct.

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.