ZME controller reported of an aircraft that encountered severe turbulence on its route. Controller t...

Narrative:

I just learned that there was an issue; that some people were injured. Aircraft X was handed-off to ZTL (T08) and switched to their frequency without any reported issue.several minutes later; T08 called back to relay that aircraft X had reported severe turbulence on their frequency at the ZME/ZTL boundary (near janes intersection); with no other information; no injuries reported. (Of course; injuries are not required to make the report serious; any severe turbulence report is dangerous). For the next hour I relayed the PIREP to pilot's heading anywhere near the area regardless of altitude. During the same time frame; I received severe turbulence reports (if I remember the specifics correctly) [near] bhm at FL370 [also at the ZME/ZTL boundary] and over mon at FL340. Aircraft eastbound and westbound near these areas received the pireps but reported no ill effects.ZTL did a great job; calling me to ensure I received the PIREP. We all forward pireps to our local center weather service unit (cwsu) for facility dissemination but that does not ensure the information gets passed to adjacent facilities. Controllers should verbally coordinate pireps occurring near their facility boundary. I've found this more commonly occurs near approach controls; but the need is the same for adjacent artccs. Turbulence is especially difficult because it can develop and then dissipate so quickly; with preceding and following aircraft not finding it.

Original NASA ASRS Text

Title: ZME Controller reported of an aircraft that encountered severe turbulence on its route. Controller then took steps to advise others of the turbulence.

Narrative: I just learned that there was an issue; that some people were injured. Aircraft X was handed-off to ZTL (T08) and switched to their frequency without any reported issue.Several minutes later; T08 called back to relay that Aircraft X had reported severe turbulence on their frequency at the ZME/ZTL boundary (near JANES intersection); with no other information; no injuries reported. (Of course; injuries are not required to make the report serious; any severe turbulence report is dangerous). For the next hour I relayed the PIREP to pilot's heading anywhere near the area regardless of altitude. During the same time frame; I received severe turbulence reports (if I remember the specifics correctly) [near] BHM at FL370 [also at the ZME/ZTL boundary] and over MON at FL340. Aircraft eastbound and westbound near these areas received the PIREPs but reported no ill effects.ZTL did a great job; calling me to ensure I received the PIREP. We all forward PIREPs to our local Center Weather Service Unit (CWSU) for facility dissemination but that does not ensure the information gets passed to adjacent facilities. Controllers should verbally coordinate PIREPs occurring near their facility boundary. I've found this more commonly occurs near Approach Controls; but the need is the same for adjacent ARTCCs. Turbulence is especially difficult because it can develop and then dissipate so quickly; with preceding and following aircraft not finding it.

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.

Attributes
ACN	1290157
Time
Date	201508
Local Time Of Day	1801-2400
Place
Locale Reference	ZME.ARTCC
State Reference	TN
Environment
Light	Night
Aircraft 1
Make Model Name	Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 23
Events
Anomaly	ATC Issue All Types Inflight Event / Encounter Weather / Turbulence

ZME controller reported of an aircraft that encountered severe turbulence on its route. Controller then took steps to advise others of the turbulence.