 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
HS125-700 flight crew en route to mdw received bad information from FMS; leading to a course deviation.
| Attributes | |
| ACN | 684547 |
| Time | |
| Date | 200601 |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | intersection : napol |
| State Reference | OH |
| Altitude | msl bound lower : 29000 msl bound upper : 32000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zob.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | HS 125 Series 700 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | descent : vacating altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 161 flight time total : 5454 flight time type : 173 |
| ASRS Report | 684547 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | non adherence : clearance other spatial deviation |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | controller : issued advisory flight crew : returned to original clearance |
| Supplementary | |
| Problem Areas | Aircraft Flight Crew Human Performance |
| Primary Problem | Aircraft |
Narrative:
While cruising on J60 en route to mdw airport; in between napol intersection and ashen intersection; our #1 GNS box started to give us bad information. The 2 GNS boxes had been xfilled for all flight plan data at the beginning of the flight. This meaning one GNS gets its flight plan from the other. Upon reaching roughly napol intersection; both pilots commented on the turn the aircraft made to the next fix. We noticed the primary GNS had an unusual display and went back to normal -- we thought. A few mins later; I looked down and saw that the #1 GNS said it was navigating to napol; which was behind us; and the #2 GNS said we are en route to ashen intersection. The aircraft appeared to be holding a random heading about 40 degrees off course. At this time; center called and asked where we were going; and to go to goshen. That was the end of the event; but we both still wonder what happened. This is a prime example of today's world of technology; why we should all still follow along our route with an old fashioned chart. I wish we would have had ours out of the binder.
Original NASA ASRS Text
Title: HS125-700 FLT CREW ENRTE TO MDW RECEIVED BAD INFO FROM FMS; LEADING TO A COURSE DEV.
Narrative: WHILE CRUISING ON J60 ENRTE TO MDW ARPT; IN BTWN NAPOL INTXN AND ASHEN INTXN; OUR #1 GNS BOX STARTED TO GIVE US BAD INFO. THE 2 GNS BOXES HAD BEEN XFILLED FOR ALL FLT PLAN DATA AT THE BEGINNING OF THE FLT. THIS MEANING ONE GNS GETS ITS FLT PLAN FROM THE OTHER. UPON REACHING ROUGHLY NAPOL INTXN; BOTH PLTS COMMENTED ON THE TURN THE ACFT MADE TO THE NEXT FIX. WE NOTICED THE PRIMARY GNS HAD AN UNUSUAL DISPLAY AND WENT BACK TO NORMAL -- WE THOUGHT. A FEW MINS LATER; I LOOKED DOWN AND SAW THAT THE #1 GNS SAID IT WAS NAVING TO NAPOL; WHICH WAS BEHIND US; AND THE #2 GNS SAID WE ARE ENRTE TO ASHEN INTXN. THE ACFT APPEARED TO BE HOLDING A RANDOM HDG ABOUT 40 DEGS OFF COURSE. AT THIS TIME; CTR CALLED AND ASKED WHERE WE WERE GOING; AND TO GO TO GOSHEN. THAT WAS THE END OF THE EVENT; BUT WE BOTH STILL WONDER WHAT HAPPENED. THIS IS A PRIME EXAMPLE OF TODAY'S WORLD OF TECHNOLOGY; WHY WE SHOULD ALL STILL FOLLOW ALONG OUR RTE WITH AN OLD FASHIONED CHART. I WISH WE WOULD HAVE HAD OURS OUT OF THE BINDER.
Data retrieved from NASA's ASRS site as of January 2009 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.