37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 371450 |
Time | |
Date | 199706 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : bae |
State Reference | WI |
Altitude | msl bound lower : 29000 msl bound upper : 29000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : zau |
Operator | common carrier : air carrier |
Make Model Name | Fokker 100 |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Route In Use | enroute airway : zau |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller non radar : 10 controller radar : 8 |
ASRS Report | 371450 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Air Traffic Incident | Pilot Deviation other |
Narrative:
Air carrier filed msp-bae J34 D5B aco pit. 20 mi east of bae VOR, I noticed he was off course. I inquired and he at first thought he was on course, then stated the aircraft was proceeding direct djb, uncommanded and unclred. Further conversation with crew indicated that they confirmed filed route as J34 djb in the computer prior to departure. Somewhere between msp and bae, the computer dropped J34 from the flight plan and aircraft proceeded direct djb. Sometimes it takes time to show a trend, things may appear to be a 1- time occurrence. Because flight crew and controllers may not be in the same place at the same time, it may take a while before an ongoing problem can be seen. This is the second time this has happened to me. The last time I worked this flight 2 weeks ago, the exact same thing happened. I am concerned there may be a problem with the FMS on this airplane.
Original NASA ASRS Text
Title: ACR FMC DROPS PORTION OF FLT PLAN RESULTING IN A NAV COURSE DEV. RPTR CLAIMS THE SAME THING OCCURRED ON THE SAME FLT 2 WKS PREVIOUS.
Narrative: ACR FILED MSP-BAE J34 D5B ACO PIT. 20 MI E OF BAE VOR, I NOTICED HE WAS OFF COURSE. I INQUIRED AND HE AT FIRST THOUGHT HE WAS ON COURSE, THEN STATED THE ACFT WAS PROCEEDING DIRECT DJB, UNCOMMANDED AND UNCLRED. FURTHER CONVERSATION WITH CREW INDICATED THAT THEY CONFIRMED FILED RTE AS J34 DJB IN THE COMPUTER PRIOR TO DEP. SOMEWHERE BTWN MSP AND BAE, THE COMPUTER DROPPED J34 FROM THE FLT PLAN AND ACFT PROCEEDED DIRECT DJB. SOMETIMES IT TAKES TIME TO SHOW A TREND, THINGS MAY APPEAR TO BE A 1- TIME OCCURRENCE. BECAUSE FLC AND CTLRS MAY NOT BE IN THE SAME PLACE AT THE SAME TIME, IT MAY TAKE A WHILE BEFORE AN ONGOING PROB CAN BE SEEN. THIS IS THE SECOND TIME THIS HAS HAPPENED TO ME. THE LAST TIME I WORKED THIS FLT 2 WKS AGO, THE EXACT SAME THING HAPPENED. I AM CONCERNED THERE MAY BE A PROB WITH THE FMS ON THIS AIRPLANE.
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.