Narrative:

The #2 engine vibration indicated 9.9 in cruise at FL340; M.80. Vibration went away for 10-15 minutes after slowing to M.77. While discussing the event with maintenance control and dispatch the #2 engine compressor stalled and significant aircraft yaw/vibration occurred. We reduced #2 thrust lever to idle; declared an emergency and told dispatch we were heading to a nearby suitable airport. The first officer took over flying and ATC duties; set up the approach; got ATIS and expeditiously descended to a 10 mile abeam position for landing on [runway] 14L at the diversion airport. After signing off with dispatch and maintenance control I ran the engine stall checklist; talked to the flight attendants; and passengers; requested landing data; ran the overweight landing checklist and took the controls for a hand-flown visual single engine approach and landing. The #2 engine had normal indications at idle so we left it running at idle. At around 1;200 AGL; the #2 engine temperature spiked to hot/max red (didn't see an actual temperature) but we elected to continue the landing rather than run the overheat checklist. Fire trucks met us at mid-field; we immediately shut down #2; and were inspected by the fire crew. No indications of fire existed so we taxied to the gate and deplaned passengers. The first officer did an outstanding job of coordinating the emergency with ATC; descending the aircraft and setting us up for a timely approach and landing; and backing me up throughout the landing. Somewhere in the busyness of it all we got a 'fire loop B det fault' that flashed for a few moments then went away; and I believe but can't be certain that we also got a momentary engine #2 fire detection inoperative ECAM that also went away after just a few seconds on the screen. I am curious if we had fire detection during the overheat while landing since the #2 engine temperature got so hot with no fire indications.

Related reports:

Google
 

Original NASA ASRS Text

Title: The flight crew of an A320 diverted to the nearest suitable airport following receipt of high vibration indications and compressor stalls from the right engine.

Narrative: The #2 Engine vibration indicated 9.9 in cruise at FL340; M.80. Vibration went away for 10-15 minutes after slowing to M.77. While discussing the event with Maintenance Control and Dispatch the #2 Engine Compressor stalled and significant aircraft yaw/vibration occurred. We reduced #2 thrust lever to idle; declared an emergency and told Dispatch we were heading to a nearby suitable airport. The First Officer took over flying and ATC duties; set up the approach; got ATIS and expeditiously descended to a 10 mile abeam position for landing on [Runway] 14L at the diversion airport. After signing off with Dispatch and Maintenance Control I ran the Engine Stall Checklist; talked to the flight attendants; and passengers; requested landing data; ran the Overweight Landing Checklist and took the controls for a hand-flown visual single engine approach and landing. The #2 Engine had normal indications at idle so we left it running at idle. At around 1;200 AGL; the #2 Engine temperature spiked to hot/max red (didn't see an actual temperature) but we elected to continue the landing rather than run the Overheat Checklist. Fire trucks met us at mid-field; we immediately shut down #2; and were inspected by the fire crew. No indications of fire existed so we taxied to the gate and deplaned passengers. The First Officer did an outstanding job of coordinating the emergency with ATC; descending the aircraft and setting us up for a timely approach and landing; and backing me up throughout the landing. Somewhere in the busyness of it all we got a 'FIRE LOOP B DET FAULT' that flashed for a few moments then went away; and I believe but can't be certain that we also got a momentary Engine #2 fire detection inoperative ECAM that also went away after just a few seconds on the screen. I am curious if we had fire detection during the overheat while landing since the #2 Engine temperature got so hot with no fire indications.

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