Enroute controller described an engine failure event when traffic at FL370 experienced clear air tur...

Narrative:

The pilot of the DC87 checked on level at FL370. Five minutes later the pilot reported clear air turbulence. I observed the altitude read-out of the aircraft fluctuate; first three hundred feet high then 4-5 hundred feet lower. At that point the pilot advised that his number one engine flamed out; and he would like a descent to FL310 to re-start the engine. I issued the descent clearance and asked the pilot to describe the turbulence so a report could be filled out and advisories could be issued to subsequent aircraft. The aircraft now level at FL310; I asked the pilot if he had stabilized; and would he be requesting climb back to FL370. The pilot responded he was stable and wanted to proceed to destination at FL310. At that time I transferred communication to the next controller and asked that he inquire about the turbulence that the aircraft had encountered because I had not received the information yet. This event was caused by a meteorological event that is impossible to predict or prevent.

Original NASA ASRS Text

Title: Enroute Controller described an engine failure event when traffic at FL370 experienced clear air turbulence and requested an immediate descent to re-start the engine. The report indicated that ATC's follow up PIREP actions was inadequate.

Narrative: The pilot of the DC87 checked on level at FL370. Five minutes later the pilot reported clear air turbulence. I observed the altitude read-out of the aircraft fluctuate; first three hundred feet high then 4-5 hundred feet lower. At that point the pilot advised that his number one engine flamed out; and he would like a descent to FL310 to re-start the engine. I issued the descent clearance and asked the pilot to describe the turbulence so a report could be filled out and advisories could be issued to subsequent aircraft. The aircraft now level at FL310; I asked the pilot if he had stabilized; and would he be requesting climb back to FL370. The pilot responded he was stable and wanted to proceed to destination at FL310. At that time I transferred communication to the next controller and asked that he inquire about the turbulence that the aircraft had encountered because I had not received the information yet. This event was caused by a meteorological event that is impossible to predict or prevent.

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.

Attributes
ACN	991481
Time
Date	201201
Place
Locale Reference	ZZZ.ARTCC
State Reference	US
Aircraft 1
Make Model Name	DC-8 70
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	Aircraft Equipment Problem Critical Inflight Event / Encounter Weather / Turbulence

Enroute controller described an engine failure event when traffic at FL370 experienced clear air turbulence and requested an immediate descent to re-start the engine. The report indicated that ATC's follow up PIREP actions was inadequate.