Narrative:

Flight dispatched with profile mode deferred for both FMC's. Initial part of flight uneventful. About 2/3 of the way through the flight I noticed green light on the MCP navigation pb switch to the heading pb. This action was confirmed on the FMA; our lateral mode was now heading. I mentioned it to the captain and reselected navigation. About 15 minutes later we both noticed it happen again. As the flight progressed this occurred more and more frequently. The captain communicated our problem with ATC. Later in the flight while experiencing other problems in the descent it also switched from heading sel to navigation on its own. During the descent I noticed the red 'FD2' warning flash on my pfd. It only lasted about a 1/2 second. This happened several times and seemed to increase in frequency as the descent progressed. Sometimes the 'FD2' flash was accompanied by the loss of AP2 and sometimes it wasn't. Sometimes the FD didn't even disappear when the 'FD2' flash appeared. Captain suggested switching to AP1. We did but AP1 still kicked off with the next 'FD2' failure. We tried this one more time with the same result. In my mind I kept thinking I was experiencing an FD2 failure and thought that the info on the captain's pfd should be good since that is using FD1. I suggested to the captain that he should fly the aircraft if he was getting good info on his pfd. He said I was doing a good job and switching controls would not help since he was experiencing the same problems. I was also remembering from a training event long ago that if FD2 fails I could simply select the captain's sys 1 on the first officer switching panel in order to have FD1 displayed on my pfd. I did not take this action since it appeared FD1 was also bad and this was re-reinforced by AP1 kicking off. My thinking was that if AP1 was engaged it would be responding to FD1 data. Therefore if it was kicking off; FD1 must be failing as well. I recall that at about 6;000 ft in the descent as we were being vectored for downwind the autothrottles failed and the ats lever on the overhead panel kicked off. Captain placed the ats lever back to on and re-selected a/thr on the MCP. Autothrottles kicked off again. We may have tried one more reset. This is about the time while using heading sel for vectors that we were turning to an assigned heading and the aircraft reversed its turn as heading sel switched back to navigation (a variation of the problem discussed in first paragraph). At this point I decided to stick with the basics; fly the airplane with what I knew worked; and stop troubleshooting. I disconnected the autopilot for the final time; switched to the flight path vector (fpv); and used manual throttles. The A300 autoflight system (afs) consists of two autopilots; two flight directors; and an autothrottle system. None of these components were working. The captain told me he was going to declare an emergency and I agreed with him. Using the fpv and with good raw data displayed on the pfd; I was able to successfully follow ATC vectors and descent instructions to intercept the localizer and fly the ILS 35L approach. On final we completed our configuration for landing and slowed to final approach speed which we computed to be 138 kts. Captain dialed in 138 in the speed/mach window on the MCP. The blue line appeared accurately on the pfd. As with other problems we experienced on this flight the blue line began to randomly flash off. When it did it was replaced with a red 'speed sel' message at the top of the speed scale on the pfd. Again; the problem increased in frequency and duration as the approach progressed. I struggled with maintaining the localizer on final. Capt did a very good job of recognizing this and giving me small heading corrections to shoot for and hold ('on glideslope; come two degrees left' for example). I do not know what caused our system malfunctions. It appears something was wrong with both FCC 1 and FCC 2. Incorporating more raw data approaches in to annual training might help crews to be prepared for a similar situation.

Related reports:

Google
 

Original NASA ASRS Text

Title: A300 flight crew experiences Autoflight system malfunctions after being dispatched with the Profile Mode of the MCP deferred. An emergency is declared and all automation is switched off followed by a raw data ILS to landing.

Narrative: Flight dispatched with Profile Mode deferred for both FMC's. Initial part of flight uneventful. About 2/3 of the way through the flight I noticed green light on the MCP NAV PB switch to the HDG PB. This action was confirmed on the FMA; our Lateral mode was now HDG. I mentioned it to the Captain and reselected NAV. About 15 minutes later we both noticed it happen again. As the flight progressed this occurred more and more frequently. The Captain communicated our problem with ATC. Later in the flight while experiencing other problems in the descent it also switched from HDG SEL to NAV on its own. During the descent I noticed the red 'FD2' warning flash on my PFD. It only lasted about a 1/2 second. This happened several times and seemed to increase in frequency as the descent progressed. Sometimes the 'FD2' flash was accompanied by the loss of AP2 and sometimes it wasn't. Sometimes the FD didn't even disappear when the 'FD2' flash appeared. Captain suggested switching to AP1. We did but AP1 still kicked off with the next 'FD2' failure. We tried this one more time with the same result. In my mind I kept thinking I was experiencing an FD2 failure and thought that the info on the Captain's PFD should be good since that is using FD1. I suggested to the Captain that he should fly the aircraft if he was getting good info on his PFD. He said I was doing a good job and switching controls would not help since he was experiencing the same problems. I was also remembering from a training event long ago that if FD2 fails I could simply select the Captain's Sys 1 on the F/O Switching Panel in order to have FD1 displayed on my PFD. I did not take this action since it appeared FD1 was also bad and this was re-reinforced by AP1 kicking off. My thinking was that if AP1 was engaged it would be responding to FD1 data. Therefore if it was kicking off; FD1 must be failing as well. I recall that at about 6;000 ft in the descent as we were being vectored for downwind the autothrottles failed and the ATS lever on the overhead panel kicked off. Captain placed the ATS lever back to ON and re-selected A/THR on the MCP. Autothrottles kicked off again. We may have tried one more reset. This is about the time while using HDG SEL for vectors that we were turning to an assigned heading and the aircraft reversed its turn as HDG SEL switched back to NAV (a variation of the problem discussed in first paragraph). At this point I decided to stick with the basics; fly the airplane with what I knew worked; and stop troubleshooting. I disconnected the Autopilot for the final time; switched to the Flight Path Vector (FPV); and used manual throttles. The A300 Autoflight System (AFS) consists of two autopilots; two flight directors; and an autothrottle system. None of these components were working. The Captain told me he was going to declare an emergency and I agreed with him. Using the FPV and with good raw data displayed on the PFD; I was able to successfully follow ATC vectors and descent instructions to intercept the localizer and fly the ILS 35L approach. On final we completed our configuration for landing and slowed to final approach speed which we computed to be 138 kts. Captain dialed in 138 in the SPD/MACH window on the MCP. The blue line appeared accurately on the PFD. As with other problems we experienced on this flight the blue line began to randomly flash off. When it did it was replaced with a red 'SPD SEL' message at the top of the speed scale on the PFD. Again; the problem increased in frequency and duration as the approach progressed. I struggled with maintaining the localizer on final. Capt did a very good job of recognizing this and giving me small heading corrections to shoot for and hold ('on glideslope; come two degrees left' for example). I do not know what caused our system malfunctions. It appears something was wrong with both FCC 1 and FCC 2. Incorporating more raw data approaches in to annual training might help crews to be prepared for a similar situation.

Data retrieved from NASA's ASRS site as of April 2012 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.