Air carrier X claims navigation deviation due to unreliable navaids.

Attributes
ACN	304558
Time
Date	199504
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : pxt
State Reference	MD
Altitude	msl bound lower : 20000 msl bound upper : 20000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zdc
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	cruise other
Route In Use	arrival other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 8000 flight time type : 4000
ASRS Report	304558
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Flight plan was orf-hpw-hpw 025-tappa-J14-pxt-warrd 4-EWR- FL200. The warrd 4 arrival uses pxt, eno and robbinsville VOR's, none of which seem to be suitable for precise navigation. 1 controller commented we were 14 mi off track and the airways were too close together for that type error. At the time pxt was varying plus or minus 8 degrees and eno was varying plus or minus 5 degrees. A xchk with ott showed 5 NM left of track. Pxt and end switched back and forth showed anywhere from 1 NM right to 8 NM left of track -- if navigation is that crucial someone needs to check the navaids in that area -- they are not precise. Callback conversation with reporter revealed the following information: ZDC airspace and procedures specialist stated the center controllers have not observed ongoing navigation deviation's because of unreliable navaids at pxt, eno and rbv. He stated the navaids have been flight checked recently and were reliable.

Original NASA ASRS Text

Title: ACR X CLAIMS NAV DEV DUE TO UNRELIABLE NAVAIDS.

Narrative: FLT PLAN WAS ORF-HPW-HPW 025-TAPPA-J14-PXT-WARRD 4-EWR- FL200. THE WARRD 4 ARR USES PXT, ENO AND ROBBINSVILLE VOR'S, NONE OF WHICH SEEM TO BE SUITABLE FOR PRECISE NAV. 1 CTLR COMMENTED WE WERE 14 MI OFF TRACK AND THE AIRWAYS WERE TOO CLOSE TOGETHER FOR THAT TYPE ERROR. AT THE TIME PXT WAS VARYING PLUS OR MINUS 8 DEGS AND ENO WAS VARYING PLUS OR MINUS 5 DEGS. A XCHK WITH OTT SHOWED 5 NM L OF TRACK. PXT AND END SWITCHED BACK AND FORTH SHOWED ANYWHERE FROM 1 NM R TO 8 NM L OF TRACK -- IF NAV IS THAT CRUCIAL SOMEONE NEEDS TO CHK THE NAVAIDS IN THAT AREA -- THEY ARE NOT PRECISE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: ZDC AIRSPACE AND PROCS SPECIALIST STATED THE CTR CTLRS HAVE NOT OBSERVED ONGOING NAV DEV'S BECAUSE OF UNRELIABLE NAVAIDS AT PXT, ENO AND RBV. HE STATED THE NAVAIDS HAVE BEEN FLT CHKED RECENTLY AND WERE RELIABLE.

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.