B767 first officer reports problems with the bt VOR departing lfpg on the left'aigle 1Y from runway ...

Narrative:

Given the left'aigle runway 27L 1Y departure; after passing CGN266R 1.5 DME; the bt 329R would not intercept (or at least 'come alive') continued on more westerly heading to intercept; since the 329R radial was still showing ahead of the aircraft (full scale). Returned bt 108.6 and 329R in the VOR panel when I realized that this was very unusual. No sooner had I reselected 108.8; when the VOR needle went full scale deflection down; indicating we had passed the bt 329R. Captain immediately turned to a northerly heading (about 340) to re-intercept the bt 329R. No sooner had he rolled out onto intercept heading when ATC gave us radar vectors back to a 270 degree heading. Correct bt frequency was confirmed at gate and before taking the runway; so why the full scale deflections in the time it took to rotate the VOR frequency knob 2 clicks clockwise; and 2 clicks counterclockwise? As a side note; we were informed that the 'le bourget air show performance' was occurring at our expected departure; (although that should have nothing to do with navigation performance). No mention of this was made by ATC just our own critique regarding navigation performance and noise abatement adherence.

Original NASA ASRS Text

Title: B767 First Officer reports problems with the BT VOR departing LFPG on the L'AIGLE 1Y from Runway 27L. A track deviation to the west occured before correcting to the north.

Narrative: Given the L'Aigle Runway 27L 1Y departure; after passing CGN266R 1.5 DME; the BT 329R would not intercept (or at least 'come alive') continued on more westerly heading to intercept; since the 329R radial was still showing ahead of the aircraft (full scale). Returned BT 108.6 and 329R in the VOR panel when I realized that this was very unusual. No sooner had I reselected 108.8; when the VOR needle went full scale deflection down; indicating we had passed the BT 329R. Captain immediately turned to a northerly heading (about 340) to re-intercept the BT 329R. No sooner had he rolled out onto intercept heading when ATC gave us radar vectors back to a 270 degree heading. Correct BT frequency was confirmed at gate and before taking the runway; so why the full scale deflections in the time it took to rotate the VOR frequency knob 2 clicks clockwise; and 2 clicks counterclockwise? As a side note; we were informed that the 'Le Bourget Air show Performance' was occurring at our expected departure; (although that should have nothing to do with navigation performance). No mention of this was made by ATC just our own critique regarding navigation performance and noise abatement adherence.

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.

Attributes
ACN	841665
Time
Date	200906
Local Time Of Day	0001-0600
Place
Locale Reference	LFPG.Airport
State Reference	FO
Environment
Light	Daylight
Aircraft 1
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	SID L'AIGLE RWY 27L 1Y
Flight Plan	IFR
Component
Aircraft Component	ILS/VOR
Person 1
Function	First Officer Pilot Not Flying
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

B767 first officer reports problems with the bt VOR departing lfpg on the left'aigle 1Y from runway 27L. A track deviation to the west occured before correcting to the north.