Narrative:

[I was] working the llo/sat sector radar position. During east flow operations at iah; our sector is required to give the aus (78) sector iah landers at FL290 or below. Such was the case today. The complicating factor was the numerous reports of moderate turbulence. The rides seemed to be getting worse and worse at FL290 and below. Prior to my taking the sector; the previous radar controller had asked the controller at sector 78 for relief from the FL290 restriction due to the bad rides. The sector 78 controller did not allow a change to the procedure. After I took the sector; I continued to get reports of moderate turbulence. Then I received a report from of a nearby incident of severe turbulence at FL250 very near the flight path of these iah landing aircraft. I asked the supervisor to try and get relief from the FL290 restriction again. He said he spoke to the supervisor in the other specialty; and they felt they could not allow a deviation from the east flow restriction. I felt obligated to comply; but did receive questions from some pilots about forcing them down to FL290 early as I was issuing them the previous reports of moderate and severe turbulence. I really didn't know what to tell them except that there was an east flow restriction. As far as I know; no other aircraft encountered the severe turbulence. It just seems as though we unnecessarily put these aircraft into a known hazard. We have received much emphasis lately at ZHU to avoid weather depicted; and to issue weather information. I don't really see the difference in this case when it is turbulence. If I depicted extreme precipitation and did not tell the pilot; I would be held accountable. Well; in this case; I knew of severe turbulence; but my supervisor was still requiring me to put aircraft into close proximity with the reported hazard. I fail to see the distinction. Recommendation; weather avoidance needs to be more than a box checking exercise.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZHU controller voiced concern regarding the failure of an adjacent sector to adjust hand off altitude procedures during know turbulence encounters.

Narrative: [I was] working the LLO/SAT Sector RADAR position. During east flow operations at IAH; our sector is required to give the AUS (78) sector IAH landers at FL290 or below. Such was the case today. The complicating factor was the numerous reports of moderate turbulence. The rides seemed to be getting worse and worse at FL290 and below. Prior to my taking the sector; the previous RADAR controller had asked the controller at sector 78 for relief from the FL290 restriction due to the bad rides. The Sector 78 controller did not allow a change to the procedure. After I took the sector; I continued to get reports of moderate turbulence. Then I received a report from of a nearby incident of severe turbulence at FL250 very near the flight path of these IAH landing aircraft. I asked the supervisor to try and get relief from the FL290 restriction again. He said he spoke to the supervisor in the other specialty; and they felt they could not allow a deviation from the east flow restriction. I felt obligated to comply; but did receive questions from some pilots about forcing them down to FL290 early as I was issuing them the previous reports of moderate and severe turbulence. I really didn't know what to tell them except that there was an east flow restriction. As far as I know; no other aircraft encountered the severe turbulence. It just seems as though we unnecessarily put these aircraft into a known hazard. We have received much emphasis lately at ZHU to avoid weather depicted; and to issue weather information. I don't really see the difference in this case when it is turbulence. If I depicted extreme precipitation and did not tell the pilot; I would be held accountable. Well; in this case; I knew of severe turbulence; but my supervisor was still requiring me to put aircraft into close proximity with the reported hazard. I fail to see the distinction. Recommendation; weather avoidance needs to be more than a box checking exercise.

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