Narrative:

Climbing through FL270 the aircraft started violently rolling left and right; uncommanded; and very near uncontrollably. There were no associated messages on the EICAS panel nor were there any lights illuminated on the overhead panel. What needs to be emphasized here is that it was very difficult to maintain control of the aircraft and there were no associated messages notifying us of a problem. We leveled off at FL270; slowed to 250 knots; notified ATC of our deviations and basically just worked to keep the aircraft straight and level. Quickly; the first officer and I determined that the first thing we should do was to isolate the yaw dampers. After turning the right one off the problem persisted so we switched it back on and tried the left one. Once it was switched off the problem stopped. At that point; we notified ATC that we would be remaining at FL270 and would be returning to normal speed. I called maintenance control and dispatch to bring them up to speed on our issue. Maintenance just told us to follow our QRH procedure of which there was none due to not having any associated EICAS message; and dispatch asked us if we felt comfortable continuing on to [a nearby alternate]; [to] which I replied yes because we were already halfway there and had 95 knots of wind on the tail. The rest of the flight was uneventful. Once on the ground; the mechanic meticulously followed his maintenance procedures inspecting the aircraft for stress and damage and informed us that maintenance engineering had pulled the data which apparently did not show a problem with the yaw damper nor were any exceedences recorded. He ended up deferring the left yaw damper and we pressed on to [destination].

Google
 

Original NASA ASRS Text

Title: B757-200 flight crew reported diverting to a nearby alternate when they experienced violent nearly uncontrollable rolls in climb at FL270 from a malfunctioning yaw damper.

Narrative: Climbing through FL270 the aircraft started violently rolling left and right; uncommanded; and very near uncontrollably. There were no associated messages on the EICAS panel nor were there any lights illuminated on the overhead panel. What needs to be emphasized here is that it was very difficult to maintain control of the aircraft and there were no associated messages notifying us of a problem. We leveled off at FL270; slowed to 250 knots; notified ATC of our deviations and basically just worked to keep the aircraft straight and level. Quickly; the FO and I determined that the first thing we should do was to isolate the yaw dampers. After turning the right one off the problem persisted so we switched it back on and tried the left one. Once it was switched off the problem stopped. At that point; we notified ATC that we would be remaining at FL270 and would be returning to normal speed. I called maintenance control and Dispatch to bring them up to speed on our issue. Maintenance just told us to follow our QRH procedure of which there was none due to not having any associated EICAS message; and Dispatch asked us if we felt comfortable continuing on to [a nearby alternate]; [to] which I replied yes because we were already halfway there and had 95 knots of wind on the tail. The rest of the flight was uneventful. Once on the ground; the mechanic meticulously followed his maintenance procedures inspecting the aircraft for stress and damage and informed us that maintenance engineering had pulled the data which apparently did not show a problem with the yaw damper nor were any exceedences recorded. He ended up deferring the left yaw damper and we pressed on to [destination].

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.