37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 315206 |
Time | |
Date | 199509 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : lax |
State Reference | CA |
Altitude | msl bound lower : 37000 msl bound upper : 37000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zla |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 270 flight time total : 11000 flight time type : 6000 |
ASRS Report | 315206 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | Navigational Facility |
Air Traffic Incident | other |
Situations | |
Navigational Aid | Unspecified |
Narrative:
Backgnd data: the lax VOR scallops and loses signal increasingly with altitude. At FL370, depending on the receiver confign, the signal will be lost 15 DME from the station in any direction. Sometimes the DME will continue with no azimuth and sometimes the DME signal will be lost. This condition is well documented by previous reports. To my knowledge no corrective action has ever been taken. On this day we were descending from FL370 into san diego on the cardi 2 arrival over the lax VOR. We lost the signal shortly after the VOR began to scallop. Azimuth incorrectly going from side to side with subsequent loss of signal. ZLA advised us we were 5 mi east of the lax VOR and asked us what our heading was. We said our heading was 120 degrees. We looked visually down on the lax airport and appeared to be just slightly east of the airport. Our DME continued to function with no DME loss. The DME counted down to 7.8 mi and began to increase which would have had us no further than 2 mi east of the VOR. I asked the center if there was a problem, meaning conflicting traffic. Center replied, 'I don't know, is there a problem?' I stated basically what I have told you in the backgnd data. This happens all the time. Why should center be so surprised when it happens? This will happen even more as winter time approachs with the resulting high velocity high altitude winds. We have received correspondence from the center stating almost no one else seems to have this problem but this particular carrier. Most other carriers are operating with INS or RNAV. Since we don't use anything but VOR receivers and probably compose the vast majority of traffic overflying the lax VOR, I think this is probably correct as it should be considering the difference in operating navigation components. Callback conversation with reporter revealed the following information: ZLA procedures specialist stated they have no reports of a problem with reliability of the lax VOR.
Original NASA ASRS Text
Title: NAVAID PROB LAX VOR UNRELIABLE DIRECTLY OVER VOR USING VOR-DME RECEIVER FOR NAV.
Narrative: BACKGND DATA: THE LAX VOR SCALLOPS AND LOSES SIGNAL INCREASINGLY WITH ALT. AT FL370, DEPENDING ON THE RECEIVER CONFIGN, THE SIGNAL WILL BE LOST 15 DME FROM THE STATION IN ANY DIRECTION. SOMETIMES THE DME WILL CONTINUE WITH NO AZIMUTH AND SOMETIMES THE DME SIGNAL WILL BE LOST. THIS CONDITION IS WELL DOCUMENTED BY PREVIOUS RPTS. TO MY KNOWLEDGE NO CORRECTIVE ACTION HAS EVER BEEN TAKEN. ON THIS DAY WE WERE DSNDING FROM FL370 INTO SAN DIEGO ON THE CARDI 2 ARR OVER THE LAX VOR. WE LOST THE SIGNAL SHORTLY AFTER THE VOR BEGAN TO SCALLOP. AZIMUTH INCORRECTLY GOING FROM SIDE TO SIDE WITH SUBSEQUENT LOSS OF SIGNAL. ZLA ADVISED US WE WERE 5 MI E OF THE LAX VOR AND ASKED US WHAT OUR HDG WAS. WE SAID OUR HDG WAS 120 DEGS. WE LOOKED VISUALLY DOWN ON THE LAX ARPT AND APPEARED TO BE JUST SLIGHTLY E OF THE ARPT. OUR DME CONTINUED TO FUNCTION WITH NO DME LOSS. THE DME COUNTED DOWN TO 7.8 MI AND BEGAN TO INCREASE WHICH WOULD HAVE HAD US NO FURTHER THAN 2 MI E OF THE VOR. I ASKED THE CTR IF THERE WAS A PROB, MEANING CONFLICTING TFC. CTR REPLIED, 'I DON'T KNOW, IS THERE A PROB?' I STATED BASICALLY WHAT I HAVE TOLD YOU IN THE BACKGND DATA. THIS HAPPENS ALL THE TIME. WHY SHOULD CTR BE SO SURPRISED WHEN IT HAPPENS? THIS WILL HAPPEN EVEN MORE AS WINTER TIME APCHS WITH THE RESULTING HIGH VELOCITY HIGH ALT WINDS. WE HAVE RECEIVED CORRESPONDENCE FROM THE CTR STATING ALMOST NO ONE ELSE SEEMS TO HAVE THIS PROB BUT THIS PARTICULAR CARRIER. MOST OTHER CARRIERS ARE OPERATING WITH INS OR RNAV. SINCE WE DON'T USE ANYTHING BUT VOR RECEIVERS AND PROBABLY COMPOSE THE VAST MAJORITY OF TFC OVERFLYING THE LAX VOR, I THINK THIS IS PROBABLY CORRECT AS IT SHOULD BE CONSIDERING THE DIFFERENCE IN OPERATING NAV COMPONENTS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: ZLA PROCS SPECIALIST STATED THEY HAVE NO RPTS OF A PROB WITH RELIABILITY OF THE LAX VOR.
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.