37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 86794 |
Time | |
Date | 198805 |
Day | Fri |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | atc facility : lax |
State Reference | CA |
Altitude | msl bound lower : 34000 msl bound upper : 34000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zla |
Operator | common carrier : air carrier |
Make Model Name | Widebody, Low Wing, 3 Turbojet Eng |
Navigation In Use | Other |
Flight Phase | cruise other |
Route In Use | enroute : pacific enroute : other oceanic enroute airway : r577 |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 200 flight time total : 15600 flight time type : 750 |
ASRS Report | 86794 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 200 flight time total : 6000 |
ASRS Report | 86957 |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : published procedure non adherence : clearance other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation |
Narrative:
My crew and I had just made the crossing from los angeles to honolulu in this aircraft earlier that same day. It was my leg (captain). The #1 autoplt was still placarded inoperative and we were using the #2 autoplt connected to the #2 INS for the crossing as we had done on the previous flight. We were assigned track R577 for the crossing. The flight was routine until some point after our position report at escro intersection. Upon crossing ektas intersection (nonreporting) a difference in plotted position and DME to the next intersection was noted. At this point the difference was minor. The true heading being flown by the autoplt matched that of the flight plan and with only 2 INS units on board we were unable to determine which unit was in error. As the flight progressed we noticed opp direction traffic approaching (estimate 10 mi sep north of our position and at a higher altitude). At this point I became obvious that we were not on track. At this point one INS showed us 35 mi north of course when compared to the other. I assumed the traffic we spotted was on the wbound track R576 (it's a one way track) and we immediately made a 45 degree correction towards the south. Shortly thereafter we were in radio and radar contact with ATC. They informed us that we were in fact north of course and correcting. They then cleared us direct to lax and we requested radar vectors and reported our navigation system as unreliable. Flight was routine from that point on. An INS check was performed at the gate and #2 INS was found to have a 65.8 mi error and was indicating a 17 KT ground speed with the brakes set at the gate. A logbook entry was made to report the problem. It is operationally approved to operate with only 2 INS units installed. If one starts to drift it leaves you in a quandary as to which unit is correct. The best you can do is split the difference. (Note: rumor has it that air carrier is replacing all of our dual INS units with 3 of the greatly improved units.) our computer generated flight plans give a true heading for each leg that we check to assure that after crossing a fix, the INS has pointed us in the right direction, however this true heading is an average midpoint heading based on the winds at midpoint on that leg. In my opinion it would be better if it were based on the heading required after crossing the fix. After all, that's when you make the xchk. We are so used to seeing several degrees of difference at this point that we were unable to spot the deviation that placed us 35 mi off course. At the time the error was discovered and a correction was made this cockpit crew had been on duty for more than 16 hours!! This crew was just supposed to fly a round trip from lax to hnl and back to lax, but the return flight was delayed due to a high speed rejected takeoff from hnl because of an engine failure indication requiring an abort. It took maintenance more that 4 hours to repair the aircraft and change the blown tires. This situation not only extended our scheduled duty day, but it also subjected the crew to an additional amount of fatigue due to the stress related to this situation. It is my opinion that a 17 1/2 hour duty day (international flag operation) is asking too much from a nonsupplemented crew. I wonder if I would have noticed our excessive course deviation sooner if I had not been so exhausted.
Original NASA ASRS Text
Title: ACR WDB TRACK DEVIATION DUE TO INS FAILURE.
Narrative: MY CREW AND I HAD JUST MADE THE XING FROM LOS ANGELES TO HONOLULU IN THIS ACFT EARLIER THAT SAME DAY. IT WAS MY LEG (CAPT). THE #1 AUTOPLT WAS STILL PLACARDED INOP AND WE WERE USING THE #2 AUTOPLT CONNECTED TO THE #2 INS FOR THE XING AS WE HAD DONE ON THE PREVIOUS FLT. WE WERE ASSIGNED TRACK R577 FOR THE XING. THE FLT WAS ROUTINE UNTIL SOME POINT AFTER OUR POS RPT AT ESCRO INTXN. UPON XING EKTAS INTXN (NONREPORTING) A DIFFERENCE IN PLOTTED POS AND DME TO THE NEXT INTXN WAS NOTED. AT THIS POINT THE DIFFERENCE WAS MINOR. THE TRUE HDG BEING FLOWN BY THE AUTOPLT MATCHED THAT OF THE FLT PLAN AND WITH ONLY 2 INS UNITS ON BOARD WE WERE UNABLE TO DETERMINE WHICH UNIT WAS IN ERROR. AS THE FLT PROGRESSED WE NOTICED OPP DIRECTION TFC APCHING (ESTIMATE 10 MI SEP N OF OUR POS AND AT A HIGHER ALT). AT THIS POINT I BECAME OBVIOUS THAT WE WERE NOT ON TRACK. AT THIS POINT ONE INS SHOWED US 35 MI N OF COURSE WHEN COMPARED TO THE OTHER. I ASSUMED THE TFC WE SPOTTED WAS ON THE WBOUND TRACK R576 (IT'S A ONE WAY TRACK) AND WE IMMEDIATELY MADE A 45 DEG CORRECTION TOWARDS THE S. SHORTLY THEREAFTER WE WERE IN RADIO AND RADAR CONTACT WITH ATC. THEY INFORMED US THAT WE WERE IN FACT N OF COURSE AND CORRECTING. THEY THEN CLRED US DIRECT TO LAX AND WE REQUESTED RADAR VECTORS AND RPTED OUR NAV SYS AS UNRELIABLE. FLT WAS ROUTINE FROM THAT POINT ON. AN INS CHK WAS PERFORMED AT THE GATE AND #2 INS WAS FOUND TO HAVE A 65.8 MI ERROR AND WAS INDICATING A 17 KT GND SPD WITH THE BRAKES SET AT THE GATE. A LOGBOOK ENTRY WAS MADE TO RPT THE PROB. IT IS OPERATIONALLY APPROVED TO OPERATE WITH ONLY 2 INS UNITS INSTALLED. IF ONE STARTS TO DRIFT IT LEAVES YOU IN A QUANDARY AS TO WHICH UNIT IS CORRECT. THE BEST YOU CAN DO IS SPLIT THE DIFFERENCE. (NOTE: RUMOR HAS IT THAT ACR IS REPLACING ALL OF OUR DUAL INS UNITS WITH 3 OF THE GREATLY IMPROVED UNITS.) OUR COMPUTER GENERATED FLT PLANS GIVE A TRUE HDG FOR EACH LEG THAT WE CHK TO ASSURE THAT AFTER XING A FIX, THE INS HAS POINTED US IN THE RIGHT DIRECTION, HOWEVER THIS TRUE HDG IS AN AVERAGE MIDPOINT HDG BASED ON THE WINDS AT MIDPOINT ON THAT LEG. IN MY OPINION IT WOULD BE BETTER IF IT WERE BASED ON THE HDG REQUIRED AFTER XING THE FIX. AFTER ALL, THAT'S WHEN YOU MAKE THE XCHK. WE ARE SO USED TO SEEING SEVERAL DEGS OF DIFFERENCE AT THIS POINT THAT WE WERE UNABLE TO SPOT THE DEVIATION THAT PLACED US 35 MI OFF COURSE. AT THE TIME THE ERROR WAS DISCOVERED AND A CORRECTION WAS MADE THIS COCKPIT CREW HAD BEEN ON DUTY FOR MORE THAN 16 HRS!! THIS CREW WAS JUST SUPPOSED TO FLY A ROUND TRIP FROM LAX TO HNL AND BACK TO LAX, BUT THE RETURN FLT WAS DELAYED DUE TO A HIGH SPD REJECTED TKOF FROM HNL BECAUSE OF AN ENG FAILURE INDICATION REQUIRING AN ABORT. IT TOOK MAINT MORE THAT 4 HRS TO REPAIR THE ACFT AND CHANGE THE BLOWN TIRES. THIS SITUATION NOT ONLY EXTENDED OUR SCHEDULED DUTY DAY, BUT IT ALSO SUBJECTED THE CREW TO AN ADDITIONAL AMOUNT OF FATIGUE DUE TO THE STRESS RELATED TO THIS SITUATION. IT IS MY OPINION THAT A 17 1/2 HR DUTY DAY (INTL FLAG OPERATION) IS ASKING TOO MUCH FROM A NONSUPPLEMENTED CREW. I WONDER IF I WOULD HAVE NOTICED OUR EXCESSIVE COURSE DEVIATION SOONER IF I HAD NOT BEEN SO EXHAUSTED.
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.