37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 432452 |
Time | |
Date | 199903 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
State Reference | KY |
Altitude | msl single value : 24000 |
Environment | |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | artcc : zid.artcc |
Operator | common carrier : air carrier |
Make Model Name | B727-200 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | cruise : level |
Route In Use | enroute airway : j6.airway |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 432452 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument pilot : multi engine |
Events | |
Anomaly | aircraft equipment problem : critical other anomaly other other spatial deviation |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | controller : issued alert flight crew : returned to intended course |
Consequence | other |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Aircraft |
Narrative:
During en route phase of flight at FL240 in the vicinity of the lajug intersection (first officer flying) we experienced a gfms anomaly. The gfms, while still connected to the autoplt, started a subtle heading drift, which displaced us off course. To our embarrassment, ATC brought the drift to our attention. The autoplt was still in auxiliary mode, connected to the gfms which appeared to just stop giving course guidance. There was no discontinuities or dr light. It is the strangest gfms anomaly I have seen in 4 yrs with the gfms on the B727. I surmise that some type of operator error must have been involved on our part, but I don't know what. It certainly was a pwrful lesson in automation complacency. Callback conversation with reporter revealed the following information: the reporter stated the gfms system is a global positioning system that can be coupled to the autoplt in the auxiliary mode. The reporter said neither the warning system on the autoplt nor the GPS warning system alerted the crew to the heading drift. The reporter said the system worked ok prior to this event and after the event. The reporter said the item was written up for maintenance but the corrective action is unknown.
Original NASA ASRS Text
Title: A B727-200 IN CRUISE AT FL240 WITH AUTOPLT COUPLED TO THE GPS SYS HAD THE ACFT START A SUBTLE HDG DRIFT OFF COURSE. ALERTED BY ATC OF COURSE DEV.
Narrative: DURING ENRTE PHASE OF FLT AT FL240 IN THE VICINITY OF THE LAJUG INTXN (FO FLYING) WE EXPERIENCED A GFMS ANOMALY. THE GFMS, WHILE STILL CONNECTED TO THE AUTOPLT, STARTED A SUBTLE HDG DRIFT, WHICH DISPLACED US OFF COURSE. TO OUR EMBARRASSMENT, ATC BROUGHT THE DRIFT TO OUR ATTN. THE AUTOPLT WAS STILL IN AUX MODE, CONNECTED TO THE GFMS WHICH APPEARED TO JUST STOP GIVING COURSE GUIDANCE. THERE WAS NO DISCONTINUITIES OR DR LIGHT. IT IS THE STRANGEST GFMS ANOMALY I HAVE SEEN IN 4 YRS WITH THE GFMS ON THE B727. I SURMISE THAT SOME TYPE OF OPERATOR ERROR MUST HAVE BEEN INVOLVED ON OUR PART, BUT I DON'T KNOW WHAT. IT CERTAINLY WAS A PWRFUL LESSON IN AUTOMATION COMPLACENCY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THE GFMS SYS IS A GLOBAL POSITIONING SYS THAT CAN BE COUPLED TO THE AUTOPLT IN THE AUX MODE. THE RPTR SAID NEITHER THE WARNING SYS ON THE AUTOPLT NOR THE GPS WARNING SYS ALERTED THE CREW TO THE HDG DRIFT. THE RPTR SAID THE SYS WORKED OK PRIOR TO THIS EVENT AND AFTER THE EVENT. THE RPTR SAID THE ITEM WAS WRITTEN UP FOR MAINT BUT THE CORRECTIVE ACTION IS UNKNOWN.
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.