D01 TRACON controller reported an airborne conflict between an aircraft on a go-around and a departu...

Narrative:

I was working the [sector radar] position during a moderate level of traffic time. I cleared aircraft X for a visual approach to runway 17L and told the aircraft to contact tower. I had previously released aircraft Y with the rundown list on a pre-coordinated heading via the SOP.aircraft X checked back on my frequency unexpectedly and advised me he was performing a go-around. Tower then called me and I asked them what the plan was with the go-around and the departure; which they had released and was airborne directly in front of the go-around. Tower paused; then indicated the go-around was runway heading; and the departure was going to turn right to a 300 heading. In my judgment that was not a safe plan; I issued aircraft X an immediate right turn to a heading of 260 and told the tower to issue the departure runway heading to try to gain some sort of separation.the LOA between the facilities has no coordinated go-around procedures. It does have some requirements for the tower in the event of a go-around; which in this case the tower did not follow; but no procedure for the tower to issue. Also the LOA does not require the tower to ensure any separation between IFR aircraft. Develop and implement in the LOA go around procedures.change the LOA so that there are separation requirements set.

Original NASA ASRS Text

Title: D01 TRACON Controller reported an airborne conflict between an aircraft on a go-around and a departure that were not separated due to lack of facility LOA's not covering this maneuver.

Narrative: I was working the [Sector Radar] position during a moderate level of traffic time. I cleared Aircraft X for a visual approach to Runway 17L and told the aircraft to contact Tower. I had previously released Aircraft Y with the rundown list on a pre-coordinated heading via the SOP.Aircraft X checked back on my frequency unexpectedly and advised me he was performing a go-around. Tower then called me and I asked them what the plan was with the go-around and the departure; which they had released and was airborne directly in front of the go-around. Tower paused; then indicated the go-around was runway heading; and the departure was going to turn right to a 300 heading. In my judgment that was not a safe plan; I issued Aircraft X an immediate right turn to a heading of 260 and told the Tower to issue the departure runway heading to try to gain some sort of separation.The LOA between the facilities has no coordinated go-around procedures. It does have some requirements for the Tower in the event of a go-around; which in this case the Tower did not follow; but no procedure for the Tower to issue. Also the LOA does not require the Tower to ensure any separation between IFR aircraft. Develop and implement in the LOA go around procedures.Change the LOA so that there are separation requirements set.

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	1626940
Time
Date	201903
Local Time Of Day	1201-1800
Place
Locale Reference	DEN.Airport
State Reference	CO
Aircraft 1
Make Model Name	Light Transport
Flight Phase	Initial Climb
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport
Operating Under FAR Part	Part 135
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 7
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

D01 TRACON controller reported an airborne conflict between an aircraft on a go-around and a departure that were not separated due to lack of facility LOA's not covering this maneuver.