Sct TRACON controller reported an aircraft departed psp and needed to return to the airport. They st...

Attributes
ACN	1418491
Time
Date	201701
Local Time Of Day	1801-2400
Place
Locale Reference	SCT.TRACON
State Reference	CA
Environment
Light	Night
Aircraft 1
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 135
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 135
Flight Phase	Takeoff
Flight Plan	IFR
Person 1
Function	Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT

Narrative:

Released aircraft X off psp runway 13R. A few minutes later I released aircraft Y off of udd. Aircraft X departed and [needed to return to the airport] with psp tower. The tower called and said aircraft X was going to stay with them and go back to the airport and land. Aircraft X continued on the 100 degree heading and never climbed out of 2;000 or entered the traffic pattern. That heading kept aircraft X aimed right at the udd airport where the other aircraft was released for departure. I had to call the psp tower and tell them to climb aircraft X who was well below the MVA in the area. The two aircraft never had a loss of separation. The tower should have given me the aircraft if it was not going to stay in the tower pattern. I should have tried to reach out to aircraft Y on the ground to attempt to cancel the release if it hadn't already switched to advisories for departure. Better communication between myself and the tower would have made the situation clearer and maybe easier to solve.

Original NASA ASRS Text

Title: SCT TRACON Controller reported an aircraft departed PSP and needed to return to the airport. They stayed on PSP Tower's frequency; but left the airport environment. This lead to a conflict with an aircraft departing UDD.

Narrative: Released Aircraft X off PSP RWY 13R. A few minutes later I released Aircraft Y off of UDD. Aircraft X departed and [needed to return to the airport] with PSP tower. The tower called and said Aircraft X was going to stay with them and go back to the airport and land. Aircraft X continued on the 100 degree heading and never climbed out of 2;000 or entered the traffic pattern. That heading kept Aircraft X aimed right at the UDD airport where the other aircraft was released for departure. I had to call the PSP tower and tell them to climb Aircraft X who was well below the MVA in the area. The two aircraft never had a loss of separation. The tower should have given me the aircraft if it was not going to stay in the tower pattern. I should have tried to reach out to Aircraft Y on the ground to attempt to cancel the release if it hadn't already switched to advisories for departure. Better communication between myself and the tower would have made the situation clearer and maybe easier to solve.

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.

Sct TRACON controller reported an aircraft departed psp and needed to return to the airport. They stayed on psp tower's frequency; but left the airport environment. This lead to a conflict with an aircraft departing udd.