Flight crew using wrong frequency for VOR for navigation, deviated from clearance.

Attributes
ACN	151124
Time
Date	199007
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : dll
State Reference	WI
Altitude	msl bound lower : 35000 msl bound upper : 35000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument pilot : atp pilot : commercial
Experience	flight time last 90 days : 210 flight time total : 18000 flight time type : 5000
ASRS Report	151124
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : atp
Events
Anomaly	other spatial deviation
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Chart Or Publication
Air Traffic Incident	other
Situations
Navigational Aid	Unspecified
Publication	Unspecified

Narrative:

Judas arrival to msp. Approaching obk VOR, center reclred us to fly heading 320 degree after obk VOR for vector to dll VOR. My copilot checked his us 7 and 8 high altitude chart and dialed in as a reference. My first officer still had a flag and I was about to question center why we were not receiving the dll VOR. I checked the judas arrival and noticed that the dll VOR has been changed to 117.0. My first officer had 115.1 dialed in. This is the old frequency but is still carried on the us (high) 7 and 8 chart dated june 22-90. It is also carried on the low altitude chart as 115.1. About the same time center advised us to dial in 117.0 and cleared direct dll. I was still on my assigned heading of 320 degree when center reclred us direct to dll. For some reason this NOTAM wasn't on our release concerning the frequency changes for both grb and dll VOR. The only thing that might have helped this situation would be to coincide the change with the revision on all charts at the same time. Center could also state the frequency in the clearance until all charts are updated. After all this we were subsequently cleared direct rst V411 msp. There was no apparent problem in all this, but there was some confusion until we realized that the dll VOR had changed frequencys.

Original NASA ASRS Text

Title: FLC USING WRONG FREQ FOR VOR FOR NAVIGATION, DEVIATED FROM CLRNC.

Narrative: JUDAS ARR TO MSP. APCHING OBK VOR, CTR RECLRED US TO FLY HDG 320 DEG AFTER OBK VOR FOR VECTOR TO DLL VOR. MY COPLT CHKED HIS US 7 AND 8 HIGH ALT CHART AND DIALED IN AS A REFERENCE. MY F/O STILL HAD A FLAG AND I WAS ABOUT TO QUESTION CTR WHY WE WERE NOT RECEIVING THE DLL VOR. I CHKED THE JUDAS ARR AND NOTICED THAT THE DLL VOR HAS BEEN CHANGED TO 117.0. MY F/O HAD 115.1 DIALED IN. THIS IS THE OLD FREQ BUT IS STILL CARRIED ON THE US (HIGH) 7 AND 8 CHART DATED JUNE 22-90. IT IS ALSO CARRIED ON THE LOW ALT CHART AS 115.1. ABOUT THE SAME TIME CTR ADVISED US TO DIAL IN 117.0 AND CLRED DIRECT DLL. I WAS STILL ON MY ASSIGNED HDG OF 320 DEG WHEN CTR RECLRED US DIRECT TO DLL. FOR SOME REASON THIS NOTAM WASN'T ON OUR RELEASE CONCERNING THE FREQ CHANGES FOR BOTH GRB AND DLL VOR. THE ONLY THING THAT MIGHT HAVE HELPED THIS SITUATION WOULD BE TO COINCIDE THE CHANGE WITH THE REVISION ON ALL CHARTS AT THE SAME TIME. CTR COULD ALSO STATE THE FREQ IN THE CLRNC UNTIL ALL CHARTS ARE UPDATED. AFTER ALL THIS WE WERE SUBSEQUENTLY CLRED DIRECT RST V411 MSP. THERE WAS NO APPARENT PROB IN ALL THIS, BUT THERE WAS SOME CONFUSION UNTIL WE REALIZED THAT THE DLL VOR HAD CHANGED FREQS.

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