VOR navigation became inoperative and flight crew unable to navigate to the VOR. TRACON gave vectors...

Attributes
ACN	106710
Time
Date	198903
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : ont
State Reference	CA
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : ont
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other other vortac
Flight Phase	climbout : initial climbout : intermediate altitude
Route In Use	departure other departure sid : sid enroute : on vectors enroute airway : ont
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : flight engineer pilot : commercial
Experience	flight time last 90 days : 170 flight time total : 3700 flight time type : 300
ASRS Report	106719
Person 2
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : cfi pilot : flight engineer
Experience	flight time last 90 days : 70 flight time total : 10950 flight time type : 70
ASRS Report	107165
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	atc equipment other atc equipment : unspecified other controllera other other : unspecified
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Navigational Facility
Air Traffic Incident	other
Situations
ATC Facility	other physical facility

Narrative:

While departing ont going to dfw flying the prado 2, after takeoff turned left to 110 degree to go direct pdz VOR. Departure asked if we were on the prado 2 at the same time we got off flags on both vors tuned to pdz. He gave us a vector 170 degree to intercept the 130 degree radial off pdz. We advised him once again that pdz was off the air. We were switched frequencys and advised the next controller that pdz was off the air. He told us to fly 130 degree and intercept the 263 off trm. We did that and were switched again. The next controller advised us that they had confirmed that pdz was off the air. Also: after losing the raw data from pdz we switched to map mode (FMS) and confirmed we were about 2 mi east of pdz before turning back. I conclude that departure does not have the capability to monitor the performance of pdz VOR which is absolutely necessary to fly the prado 2. This is not good.

Original NASA ASRS Text

Title: VOR NAV BECAME INOPERATIVE AND FLT CREW UNABLE TO NAVIGATE TO THE VOR. TRACON GAVE VECTORS.

Narrative: WHILE DEPARTING ONT GOING TO DFW FLYING THE PRADO 2, AFTER TKOF TURNED LEFT TO 110 DEG TO GO DIRECT PDZ VOR. DEP ASKED IF WE WERE ON THE PRADO 2 AT THE SAME TIME WE GOT OFF FLAGS ON BOTH VORS TUNED TO PDZ. HE GAVE US A VECTOR 170 DEG TO INTERCEPT THE 130 DEG RADIAL OFF PDZ. WE ADVISED HIM ONCE AGAIN THAT PDZ WAS OFF THE AIR. WE WERE SWITCHED FREQS AND ADVISED THE NEXT CTLR THAT PDZ WAS OFF THE AIR. HE TOLD US TO FLY 130 DEG AND INTERCEPT THE 263 OFF TRM. WE DID THAT AND WERE SWITCHED AGAIN. THE NEXT CTLR ADVISED US THAT THEY HAD CONFIRMED THAT PDZ WAS OFF THE AIR. ALSO: AFTER LOSING THE RAW DATA FROM PDZ WE SWITCHED TO MAP MODE (FMS) AND CONFIRMED WE WERE ABOUT 2 MI E OF PDZ BEFORE TURNING BACK. I CONCLUDE THAT DEP DOES NOT HAVE THE CAPABILITY TO MONITOR THE PERFORMANCE OF PDZ VOR WHICH IS ABSOLUTELY NECESSARY TO FLY THE PRADO 2. THIS IS NOT GOOD.

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