B767 crew departing lpfg tunes wrong VOR frequency and deviates from SID track.

Attributes
ACN	710232
Time
Date	200609
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : lfpg.airport
State Reference	FO
Altitude	msl bound lower : 1700 msl bound upper : 2500
Environment
Weather Elements	Fog
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : lfpg.tracon
Operator	common carrier : air carrier
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Navigation In Use	other vortac
Flight Phase	climbout : initial
Route In Use	departure sid : amoga
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	710232
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
ASRS Report	710231
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued advisory flight crew : returned to original clearance
Supplementary
Problem Areas	Company Chart Or Publication Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We departed lfpg runway 27L on the amoga departure; with the first officer flying. As instructed in the company special procedures; the first officer and I were in raw data. I had my VOR tuned to bt (108.8) and a course of 329 degrees set in and the first officer had cgn (115.35) and a course of 266 degrees. On the takeoff checklist when the navigation radios were called; I checked my VOR and looked at the first officer's noting the 266 degree course set on his. Some time after gear retraction and 1900 ft; the first officer started a turn to intercept the 329 degree radial off bt (108.8) and I was surprised to see the deviation bar on my HSI still on the peg and this time I checked the RMI and DME's noticing the radials did not look right and I doublechked the chart. Looking at my VOR setup and the first officer's; I noted his VOR was tuned to pgs (117.05); I immediately reached over and retuned his to the correct VOR cgn (115.35); but we had already deviated off the track and moments later departure called to tell us we were 3 mi east of course. We returned to track as quickly as we could at this time. It appears to me the primary cause of this deviation was a failure to pay attention to detail; and a contributing factor was the depiction of the pgs (117.05) which is not used for any of the departures depicted on the chart. The only place where the pgs VOR is referenced is the MSA which also references the cdg VOR. The depiction of the pgs VOR only introduces an element of possible confusion. Callback conversation with reporter revealed the following information: the captain states that the company's reason for using raw data is to improve navigation accuracy in the early phase of flight. The FMC was loaded with this SID and it was depicted on the navigation display. The aircraft position was accurately displayed on the end of runway 27L as they started their takeoff roll. The first officer got confused when the CDI did not center after takeoff and started his turn early.

Original NASA ASRS Text

Title: B767 CREW DEPARTING LPFG TUNES WRONG VOR FREQ AND DEVIATES FROM SID TRACK.

Narrative: WE DEPARTED LFPG RWY 27L ON THE AMOGA DEP; WITH THE FO FLYING. AS INSTRUCTED IN THE COMPANY SPECIAL PROCS; THE FO AND I WERE IN RAW DATA. I HAD MY VOR TUNED TO BT (108.8) AND A COURSE OF 329 DEGS SET IN AND THE FO HAD CGN (115.35) AND A COURSE OF 266 DEGS. ON THE TKOF CHKLIST WHEN THE NAV RADIOS WERE CALLED; I CHKED MY VOR AND LOOKED AT THE FO'S NOTING THE 266 DEG COURSE SET ON HIS. SOME TIME AFTER GEAR RETRACTION AND 1900 FT; THE FO STARTED A TURN TO INTERCEPT THE 329 DEG RADIAL OFF BT (108.8) AND I WAS SURPRISED TO SEE THE DEV BAR ON MY HSI STILL ON THE PEG AND THIS TIME I CHKED THE RMI AND DME'S NOTICING THE RADIALS DID NOT LOOK RIGHT AND I DOUBLECHKED THE CHART. LOOKING AT MY VOR SETUP AND THE FO'S; I NOTED HIS VOR WAS TUNED TO PGS (117.05); I IMMEDIATELY REACHED OVER AND RETUNED HIS TO THE CORRECT VOR CGN (115.35); BUT WE HAD ALREADY DEVIATED OFF THE TRACK AND MOMENTS LATER DEP CALLED TO TELL US WE WERE 3 MI E OF COURSE. WE RETURNED TO TRACK AS QUICKLY AS WE COULD AT THIS TIME. IT APPEARS TO ME THE PRIMARY CAUSE OF THIS DEV WAS A FAILURE TO PAY ATTN TO DETAIL; AND A CONTRIBUTING FACTOR WAS THE DEPICTION OF THE PGS (117.05) WHICH IS NOT USED FOR ANY OF THE DEPS DEPICTED ON THE CHART. THE ONLY PLACE WHERE THE PGS VOR IS REFED IS THE MSA WHICH ALSO REFS THE CDG VOR. THE DEPICTION OF THE PGS VOR ONLY INTRODUCES AN ELEMENT OF POSSIBLE CONFUSION. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE CAPT STATES THAT THE COMPANY'S REASON FOR USING RAW DATA IS TO IMPROVE NAV ACCURACY IN THE EARLY PHASE OF FLT. THE FMC WAS LOADED WITH THIS SID AND IT WAS DEPICTED ON THE NAV DISPLAY. THE ACFT POS WAS ACCURATELY DISPLAYED ON THE END OF RWY 27L AS THEY STARTED THEIR TKOF ROLL. THE FO GOT CONFUSED WHEN THE CDI DID NOT CENTER AFTER TKOF AND STARTED HIS TURN EARLY.

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.