Narrative:

The parachute jump area was active VFR/145 at XS90. This area is controlled by aus app and they notify sat app and ZHU rnd sector 92 when active. The jump plane was climbing in the area southbound and spilled out of the depicted protected airspace. Meanwhile aircraft X was on the setzr SID from sat climbing to FL230. As the targets began to merge I turned aircraft Y to mercr intersection on the SID to pull south and issued an initial heading of 15 degrees right to help expedite the vector. This turn kept him an addition 2 miles south of the depicted jump area (the SID takes departures along the southern boundary of jump area). After reevaluating the situation I stopped aircraft Y at 14000 below the jump plane at 14500. Aircraft X was climbing unusually slow. Majority of the time jets will top this area. As soon as I un-keyed the jump plane began a decent. Aircraft x responded to RA and reported seeing traffic 400 ft above.this has been an ongoing issue for slow climbers or turbo props on this SID with the parachute jump areas active. As stated above the jump are sits just off the SID were the east departures off sat intercept on a northeast heading then turn east on SID. This jump area is located within sat app who owns 13000 and below and aus app who owns 12000 and blow and our 92 sector. I do not have control for turns from sat until out of 13000 and have active MOA at 8000-12000 south of the SID. For many reasons this is an unsafe place for jump are:1) in a major departure corridor for sat app.2) jump planes spill out of depicted area.3) sat app does not ensure departures top jump planes.4) aus app does not keep them in areas.1) don't allow parachute jump operations in or near a major departures or arrival corridors.2) move SID south.3) cap jump area altitude to 12000/13000 and sat app should be required to ensure separation via alt or vector before shipping to 92 sector.4) aus app needs to monitor their jump planes to prevent spilling out.

Google
 

Original NASA ASRS Text

Title: ZHU Controller reported a NMAC between an air carrier and a jump plane due to the proximity of the jump area to the SID routing.

Narrative: The parachute jump area was active VFR/145 at XS90. This area is controlled by AUS app and they notify SAT app and ZHU RND sector 92 when active. The jump plane was climbing in the area southbound and spilled out of the depicted protected airspace. Meanwhile Aircraft X was on the SETZR SID from SAT climbing to FL230. As the targets began to merge I turned Aircraft Y to MERCR intersection on the SID to pull south and issued an initial heading of 15 degrees right to help expedite the vector. This turn kept him an addition 2 miles south of the depicted jump area (the SID takes departures along the southern boundary of jump area). After reevaluating the situation I stopped Aircraft Y at 14000 below the jump plane at 14500. Aircraft X was climbing unusually slow. Majority of the time jets will top this area. As soon as I un-keyed the jump plane began a decent. Aircraft x responded to RA and reported seeing traffic 400 ft above.This has been an ongoing issue for slow climbers or turbo props on this SID with the parachute jump areas active. As stated above the jump are sits just off the SID were the east departures off SAT intercept on a northeast heading then turn east on SID. This jump area is located within SAT app who owns 13000 and below and AUS app who owns 12000 and blow and our 92 sector. I do not have control for turns from SAT until out of 13000 and have active MOA at 8000-12000 south of the SID. For many reasons this is an unsafe place for jump are:1) In a major departure corridor for SAT app.2) Jump planes spill out of depicted area.3) SAT app does not ensure departures top jump planes.4) AUS app does not keep them in areas.1) Don't allow parachute jump operations in or near a major departures or arrival corridors.2) Move SID south.3) Cap jump area altitude to 12000/13000 and SAT app should be required to ensure separation via alt or vector before shipping to 92 sector.4) AUS app needs to monitor their jump planes to prevent spilling out.

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.