ZHU controller describes scenario where a departure is taken off its route to allow its climb; while...

Attributes
ACN	1179579
Time
Date	201406
Local Time Of Day	1201-1800
Place
Locale Reference	ZHU.ARTCC
State Reference	TX
Environment
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 1 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR WAPPL
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 4
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Track / Heading All Types

Narrative:

Aircraft X was a cxo departure climbing inside of I90 airspace on the lch departure. I90 switched him to me climbing to 160 with 2 wappl arrivals descending on top of him. My d-side called over to das to point the departure out and they referenced aircraft Y and aircraft Z on the [arrival]. I called over to approach to tell them I was delaying him at 160 for the arrivals. The I90 controller told me to put him on a 120 heading to avoid the arrivals in which I did. This departure is not procedurally separated from these wappl arrivals and we can't climb the cxo/dwh departures with the lack of separation. The I90 controller continued to descend the arrivals through the altitudes of aircraft X. Once they were cleared inside of approach airspace I climbed the departure. This to my knowledge happens on a daily basis and is a very unsafe condition.look into a procedure change on the north satellite departures going out the trios gate to.

Original NASA ASRS Text

Title: ZHU Controller describes scenario where a departure is taken off its route to allow its climb; while it comes into conflict with two arrivals. The Controller describes the routes are not able to climb or descend traffic laterally but controllers do this everyday.

Narrative: Aircraft X was a CXO departure climbing inside of I90 airspace on the LCH departure. I90 switched him to me climbing to 160 with 2 WAPPL arrivals descending on top of him. My D-Side called over to DAS to point the departure out and they referenced Aircraft Y and Aircraft Z on the [Arrival]. I called over to Approach to tell them I was delaying him at 160 for the arrivals. The I90 Controller told me to put him on a 120 heading to avoid the arrivals in which I did. This departure is not procedurally separated from these WAPPL arrivals and we can't climb the CXO/DWH departures with the lack of separation. The I90 Controller continued to descend the arrivals through the altitudes of Aircraft X. Once they were cleared inside of approach airspace I climbed the departure. This to my knowledge happens on a daily basis and is a very unsafe condition.Look into a procedure change on the north satellite departures going out the Trios gate to.

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.

ZHU controller describes scenario where a departure is taken off its route to allow its climb; while it comes into conflict with two arrivals. The controller describes the routes are not able to climb or descend traffic laterally but controllers do this everyday.