37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 269328 |
Time | |
Date | 199404 |
Day | Thu |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : eni |
State Reference | CA |
Altitude | msl bound lower : 37000 msl bound upper : 37000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zoa |
Operator | common carrier : air carrier |
Make Model Name | B747-100 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | cruise other |
Route In Use | enroute : other oceanic enroute : direct enroute : pacific |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 150 flight time total : 4000 |
ASRS Report | 269328 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 15000 flight time type : 1900 |
ASRS Report | 269337 |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | flight crew : returned to intended course or assigned course other |
Consequence | faa : reviewed incident with flight crew faa : investigated |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation other |
Narrative:
A military charter from yokota airfield, japan, to lax. We contacted ZOA at trevr intersection, they said we were 12 mi northeast of trevr and cleared us direct avenal. En route to avenal they called again and said we were cleared direct avenal, we said we were proceeding direct and they said again that we had been 12 northeast of trevr. At that time we started picking up avenal on our VOR's and made a 5 degree correction and nothing else was said about it. When we landed in lax and flushed our INS's, their errors were 20, 13, 8. Callback conversation with reporter revealed the following information: the reporting first officer says that the FAA started to 'look into' this incident, then dropped it. The flight plan in this incident agreed with the chart coordinates and always does. The INS tolerances are 3 NM plus 3 NM per hour of flight time, about 33 NM for this flight. There is no way to update the INS approaching trevr. The reporter does not think that this aircraft was the same one that is discussed in acn 269411, but it may be his air carrier is changing these old INS for newer, more precise ones. INS tolerance equals 3 NM plus (3 NM/hour) (10 hour) equals 33 NM. A call to ZOA oceanic control found that an aircraft is considered to be on course if it is no further than 20 mi off of the centerline of the course. It can be anywhere along the course line and still be on course. Many of the aircraft coming in over trevr are in the flexible track system and appear to be off course when they are actually on course. Many 'oners' (oceanic navigation error reports) are filed in this area and are later dismissed. The ZOA respondent does not think that there is distortion in its radar presentation at trevr. He agrees that there may be a 'crusade' by controllers in this sector to improve navigation. Supplemental information from acn 269337: upon landing at lax the INS units indicated within tolerance, so we did not write up the INS units. This navigation error was reported to our chief pilot.
Original NASA ASRS Text
Title: A B-747-250 MAY HAVE BEEN OFF COURSE AT TREVR.
Narrative: A MIL CHARTER FROM YOKOTA AIRFIELD, JAPAN, TO LAX. WE CONTACTED ZOA AT TREVR INTXN, THEY SAID WE WERE 12 MI NE OF TREVR AND CLRED US DIRECT AVENAL. ENRTE TO AVENAL THEY CALLED AGAIN AND SAID WE WERE CLRED DIRECT AVENAL, WE SAID WE WERE PROCEEDING DIRECT AND THEY SAID AGAIN THAT WE HAD BEEN 12 NE OF TREVR. AT THAT TIME WE STARTED PICKING UP AVENAL ON OUR VOR'S AND MADE A 5 DEG CORRECTION AND NOTHING ELSE WAS SAID ABOUT IT. WHEN WE LANDED IN LAX AND FLUSHED OUR INS'S, THEIR ERRORS WERE 20, 13, 8. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTING FO SAYS THAT THE FAA STARTED TO 'LOOK INTO' THIS INCIDENT, THEN DROPPED IT. THE FLT PLAN IN THIS INCIDENT AGREED WITH THE CHART COORDINATES AND ALWAYS DOES. THE INS TOLERANCES ARE 3 NM PLUS 3 NM PER HR OF FLT TIME, ABOUT 33 NM FOR THIS FLT. THERE IS NO WAY TO UPDATE THE INS APCHING TREVR. THE RPTR DOES NOT THINK THAT THIS ACFT WAS THE SAME ONE THAT IS DISCUSSED IN ACN 269411, BUT IT MAY BE HIS ACR IS CHANGING THESE OLD INS FOR NEWER, MORE PRECISE ONES. INS TOLERANCE EQUALS 3 NM PLUS (3 NM/HR) (10 HR) EQUALS 33 NM. A CALL TO ZOA OCEANIC CTL FOUND THAT AN ACFT IS CONSIDERED TO BE ON COURSE IF IT IS NO FURTHER THAN 20 MI OFF OF THE CTRLINE OF THE COURSE. IT CAN BE ANYWHERE ALONG THE COURSE LINE AND STILL BE ON COURSE. MANY OF THE ACFT COMING IN OVER TREVR ARE IN THE FLEXIBLE TRACK SYS AND APPEAR TO BE OFF COURSE WHEN THEY ARE ACTUALLY ON COURSE. MANY 'ONERS' (OCEANIC NAV ERROR RPTS) ARE FILED IN THIS AREA AND ARE LATER DISMISSED. THE ZOA RESPONDENT DOES NOT THINK THAT THERE IS DISTORTION IN ITS RADAR PRESENTATION AT TREVR. HE AGREES THAT THERE MAY BE A 'CRUSADE' BY CTLRS IN THIS SECTOR TO IMPROVE NAV. SUPPLEMENTAL INFO FROM ACN 269337: UPON LNDG AT LAX THE INS UNITS INDICATED WITHIN TOLERANCE, SO WE DID NOT WRITE UP THE INS UNITS. THIS NAV ERROR WAS RPTED TO OUR CHIEF PLT.
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.