Date: 201201
Location: ZZZ.ARTCC, US
Weather elements / visibility: Turbulence
Aircraft: DC-8 70
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Second reporter function: Supervisor / CIC
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Overcame Equipment Problem
Contributing factors: Weather; Human Factors; Aircraft
Primary problem: Weather

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.


Second narrative: I was made aware by a Controller that a DC87 still had an engine out due to a flame out from encountering extreme mountain wave and turbulence; previously this was the first I'd heard of it. The Controller told me that the pilot was still unable to restart #1 engine. He was not declaring an emergency and he was talking to Dispatch for further guidance. I relayed this information to the OMIC and to the next Center. Upon further review; I was told by the Controller that he had; indeed; worked that aircraft. He had noticed the pilot's altitude fluctuating and the aircraft was veering off course. When he queried the pilot; the pilot responded he had encountered some clear air turbulence and was trying to restart #1 engine. The Controller asked if any assistance was required and the pilot responded; 'No;' but asked for a descent to FL310; which the Controller issued. The Controller then tried to get a PIREP from the pilot as to the type of turbulence; to which the pilot replied that he would get back to the Controller. The pilot did not and no PIREP was issued until I turned one in 30 minutes later; once I became aware of the situation. I think the information that a 'potential' for an aircraft emergency could exist should have been relayed to the FLM sooner; and that the Controller should have been a little more aggressive in determining the classification of turbulence. Additionally; I think the pilot should have been more forthcoming about what he was encountering to ensure that no subsequent aircraft would encounter what he had just experienced.


Synopsis: 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.