Narrative:

At cruise at FL290; about 2 hours into flight; got stick shaker; and level 1 'sel lsas rib off' and 'sel yaw upr B off.' stick shaker continued for about a minute and then stopped. Pitch; airspeed; and angle of attack were all normal and stable. Additionally level 1 alerts 'sel lsas lob off' and 'sel yaw upr a off' cycled on and off about every 15 seconds. Turned upper yaw b and right inbd lsas switches off; and they showed fail in the switch. Turned upper yaw a and left outbd switches off (fail light in switch went off) and then back on; and cycling alerts stopped. Also got autopilot single and single land. Autopilot 1 and flight director 1 only were available. First officer (first officer) switched flight director to number one. Once the situation seemed under control; called IRO2 (international relief officer) to the cockpit and briefed him on the situation. Communicated with [dispatch] and [maintenance] through satcom. Just as [operations manager; chief pilot; and flight engineer] were joining the call; satcom failed and remained inop for the remainder of flight. First officer and IRO2 researched problem while captain continued communication with [dispatch] through ACARS and HF phone patch. [Dispatch] advised nearest divert was ZZZZ; nearest [company] maintenance was ZZZ. Worked through decision making process and crew's assessment was a single channel failure of the number 2 FCC (flight control computer.) captain decided that it was safe; legal; and reliable to continue to destination. First officer and IRO2 were both comfortable with decision. [Dispatch] was advised of decision and sent [estimated time] information. About 6 hours into flight; got 'sel lsas lob off' and 'sel yaw upr a off' alerts. Turned switches off and fail light in switches went away. Left the switches off and continued to destination with no additional problems.this aircraft had a history of FCC problems; and has had FCC problems since. It appears more in depth troubleshooting is appropriate.

Related reports:

Google
 

Original NASA ASRS Text

Title: MD-11 Captain reported continuous aircraft flight control computer problems.

Narrative: At cruise at FL290; about 2 hours into flight; got stick shaker; and level 1 'SEL LSAS rib off' and 'SEL yaw UPR B off.' Stick shaker continued for about a minute and then stopped. Pitch; airspeed; and angle of attack were all normal and stable. Additionally level 1 alerts 'SEL LSAS lob off' and 'SEL yaw UPR A off' cycled on and off about every 15 seconds. Turned upper yaw b and right inbd LSAS switches off; and they showed fail in the switch. Turned upper yaw A and left outbd switches off (fail light in switch went off) and then back on; and cycling alerts stopped. Also got autopilot single and single land. Autopilot 1 and flight director 1 only were available. FO (First Officer) switched flight director to number one. Once the situation seemed under control; called IRO2 (International Relief Officer) to the cockpit and briefed him on the situation. Communicated with [Dispatch] and [Maintenance] through SATCOM. Just as [operations manager; Chief Pilot; and flight engineer] were joining the call; SATCOM failed and remained inop for the remainder of flight. FO and IRO2 researched problem while captain continued communication with [Dispatch] through ACARS and HF phone patch. [Dispatch] advised nearest divert was ZZZZ; nearest [company] maintenance was ZZZ. Worked through decision making process and crew's assessment was a single channel failure of the number 2 FCC (Flight Control Computer.) Captain decided that it was safe; legal; and reliable to continue to destination. FO and IRO2 were both comfortable with decision. [Dispatch] was advised of decision and sent [estimated time] information. About 6 hours into flight; got 'SEL LSAS lob off' and 'SEL yaw UPR A off' alerts. Turned switches off and fail light in switches went away. Left the switches off and continued to destination with no additional problems.This aircraft had a history of FCC problems; and has had FCC problems since. It appears more in depth troubleshooting is appropriate.

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