Narrative:

Departing runway 27L at lfpg. Flying atrex 1A departure SID. Used LNAV for departure with manual VOR on cgn for backup of initial course and turn distance. Took off and had LNAV capture. Began right turn at 1.5 DME on 266R off cgn as directed by flight director and verified with manual backup. Departure instructions on SID say 'intercept cgn R-266; at cgn 1.5 DME outbound turn right; intercept bt R329 to D10.1 bt' (no rollout heading to intercept the bt 329R is specified).rolled out of turn on 310 degree heading to intercept bt 329R using 20 degree intercept angle to prevent overshoot; due to close proximity of bt vor. Departure control advised we were departing noise corridor and gave us a 300 degree heading for intercept of bt 329R. No traffic or terrain conflicts were encountered. After intercepting 329R; the rest of departure was uneventful. The main thing I feel would help prevent this problem would be to specify on the SID; a rollout heading to intercept the bt 329R. This would then give a more specific intercept angle and hence a more specific ground track which would keep the aircraft in the corridor.

Google
 

Original NASA ASRS Text

Title: A B767ER departing LFPG on the ATREX 1A SID turned prematurely after takeoff and exited the Minimum Noise Routing airspace.

Narrative: Departing Runway 27L at LFPG. Flying ATREX 1A departure SID. Used LNAV for departure with manual VOR on CGN for backup of initial course and turn distance. Took off and had LNAV capture. Began right turn at 1.5 DME on 266R off CGN as directed by flight director and verified with manual backup. Departure instructions on SID say 'Intercept CGN R-266; at CGN 1.5 DME outbound turn right; intercept BT R329 to D10.1 BT' (no rollout heading to intercept the BT 329R is specified).Rolled out of turn on 310 degree heading to intercept BT 329R using 20 degree intercept angle to prevent overshoot; due to close proximity of BT Vor. Departure Control advised we were departing noise corridor and gave us a 300 degree heading for intercept of BT 329R. No traffic or terrain conflicts were encountered. After intercepting 329R; the rest of departure was uneventful. The main thing I feel would help prevent this problem would be to specify on the SID; a rollout heading to intercept the BT 329R. This would then give a more specific intercept angle and hence a more specific ground track which would keep the aircraft in the corridor.

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