37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 223579 |
Time | |
Date | 199210 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : dca |
State Reference | DC |
Altitude | msl bound lower : 10000 msl bound upper : 10000 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | artcc : zny |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | arrival other enroute airway : dca |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 250 flight time total : 15000 |
ASRS Report | 223579 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | aircraft equipment problem : less severe altitude deviation : excursion from assigned altitude non adherence : clearance other spatial deviation |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other controllera |
Resolutory Action | controller : issued new clearance |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On our third leg of our daily trip we were approaching bilit intersection (bos to dca) en route to dca. Just prior to bilit intersection both our FMC's blanked and finally recovered. Our routing/clearance was to go from bilit to dca. On top of our FMC's going inoperative, the aircraft began to slowly descend uncommanded out of our selected altitude. I was flying the aircraft and had to disconnect the aircraft from the autoplt and manually fly the aircraft until we could get the computers back up. At the same time the dca/washington controller asked us what our routing was and I asked him what he wanted and he stated that we were supposed to be going to dca directly. Both the captain and I felt that we were headed to dca directly, but following the FMC failure, the computer was commanding the autoplt to steer slightly off course to an unknown point. We again selected dca direct and there was a slight turn. The controller stated that this area between bilit and dca has many route deviations from all airlines on this segment. Our TCASII had no aircraft in the local area at any altitude at the time of this event. It did not appear that we were off course that much if any, but the controller acted concerned. Throughout this leg we had been requested by bos, ny, and washington controllers to carry out many heading, altitude and airspeed changes throughout this 1:39 hour flight which demanded an abnormal amount of attention. Callback conversation with reporter revealed the following information. Reporter states that they were about 30 mi east of airport when incident occurred. Reporter is new to this aircraft, has only been flying it for about 4 weeks. However, he has a lot of experience in glass cockpit aircraft. He said that FMC problems are not new these aircraft. Does not know what the problems are. He mentioned that around this time their maintenance people were having a labor dispute and allegedly, some had emptied all information from the FMC. This lasted for about 1 week. The controller mentioned to them that there have been many aircraft off course apparently referring to either FMC problems of flcs not paying attention.
Original NASA ASRS Text
Title: ACR INBOUND TO DCA EXPERIENCES LOSS OF FMC'S AND DEVIATES OFF COURSE. CTLR CATCHES ERROR.
Narrative: ON OUR THIRD LEG OF OUR DAILY TRIP WE WERE APCHING BILIT INTXN (BOS TO DCA) ENRTE TO DCA. JUST PRIOR TO BILIT INTXN BOTH OUR FMC'S BLANKED AND FINALLY RECOVERED. OUR ROUTING/CLRNC WAS TO GO FROM BILIT TO DCA. ON TOP OF OUR FMC'S GOING INOP, THE ACFT BEGAN TO SLOWLY DSND UNCOMMANDED OUT OF OUR SELECTED ALT. I WAS FLYING THE ACFT AND HAD TO DISCONNECT THE ACFT FROM THE AUTOPLT AND MANUALLY FLY THE ACFT UNTIL WE COULD GET THE COMPUTERS BACK UP. AT THE SAME TIME THE DCA/WASHINGTON CTLR ASKED US WHAT OUR ROUTING WAS AND I ASKED HIM WHAT HE WANTED AND HE STATED THAT WE WERE SUPPOSED TO BE GOING TO DCA DIRECTLY. BOTH THE CAPT AND I FELT THAT WE WERE HEADED TO DCA DIRECTLY, BUT FOLLOWING THE FMC FAILURE, THE COMPUTER WAS COMMANDING THE AUTOPLT TO STEER SLIGHTLY OFF COURSE TO AN UNKNOWN POINT. WE AGAIN SELECTED DCA DIRECT AND THERE WAS A SLIGHT TURN. THE CTLR STATED THAT THIS AREA BTWN BILIT AND DCA HAS MANY RTE DEVS FROM ALL AIRLINES ON THIS SEGMENT. OUR TCASII HAD NO ACFT IN THE LCL AREA AT ANY ALT AT THE TIME OF THIS EVENT. IT DID NOT APPEAR THAT WE WERE OFF COURSE THAT MUCH IF ANY, BUT THE CTLR ACTED CONCERNED. THROUGHOUT THIS LEG WE HAD BEEN REQUESTED BY BOS, NY, AND WASHINGTON CTLRS TO CARRY OUT MANY HDG, ALT AND AIRSPD CHANGES THROUGHOUT THIS 1:39 HR FLT WHICH DEMANDED AN ABNORMAL AMOUNT OF ATTN. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO. RPTR STATES THAT THEY WERE ABOUT 30 MI E OF ARPT WHEN INCIDENT OCCURRED. RPTR IS NEW TO THIS ACFT, HAS ONLY BEEN FLYING IT FOR ABOUT 4 WKS. HOWEVER, HE HAS A LOT OF EXPERIENCE IN GLASS COCKPIT ACFT. HE SAID THAT FMC PROBLEMS ARE NOT NEW THESE ACFT. DOES NOT KNOW WHAT THE PROBLEMS ARE. HE MENTIONED THAT AROUND THIS TIME THEIR MAINT PEOPLE WERE HAVING A LABOR DISPUTE AND ALLEGEDLY, SOME HAD EMPTIED ALL INFO FROM THE FMC. THIS LASTED FOR ABOUT 1 WK. THE CTLR MENTIONED TO THEM THAT THERE HAVE BEEN MANY ACFT OFF COURSE APPARENTLY REFERRING TO EITHER FMC PROBLEMS OF FLCS NOT PAYING ATTN.
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.