Controller reported issuing traffic to an aircraft on a missed approach. Both aircraft were below th...

Narrative:

Aircraft X was executing the published missed approach at ghm. I noticed a VFR aircraft that appeared to be inbound to the airport; but from the opposite direction. I called aircraft X when I first saw him on radar on his missed. On the second call I received a reply and immediately issued traffic. I issued traffic several times and said something to the effect of I can't turn you because you're below the mia but; aircraft X finally got the traffic in sight and stated he was turning. After climbing above the mia I cleared the aircraft on to his destination.in my [xx] years I've never encountered this situation. I'm [reporting] this because if it happened again I might take action below the mia. The mia in this case is 2500 ft and with the potential collision at 2200 ft I might turn the [aircraft] at 2000 ft. I don't think I had time to ask if he could maintain his own terrain and obstruction avoidance. Plus; he was a student pilot and; in my experience; this question causes confusion. So; next time; I would probably ask if the pilot had ground contact and suggest a turn. This is an unusual situation because at most of our airports I wouldn't be able to talk to aircraft at this low an altitude. The sector transmitter is at ghm so I was able to communicate early at this airport. I would have thought that the two involved aircraft would have known about each other through unicom I'm wondering if this should have been treated as an emergency and I should have had a 'deal' with the mia and would have turned the aircraft while he was slightly below the mia. I would have felt better if I had done this.

Original NASA ASRS Text

Title: Controller reported issuing traffic to an aircraft on a missed approach. Both aircraft were below the MIA and the Controller could not turn the aircraft to avoid traffic. Controller later questioned if he should have done something different.

Narrative: Aircraft X was executing the published missed approach at GHM. I noticed a VFR aircraft that appeared to be inbound to the airport; but from the opposite direction. I called Aircraft X when I first saw him on radar on his missed. On the second call I received a reply and immediately issued traffic. I issued traffic several times and said something to the effect of I can't turn you because you're below the MIA but; Aircraft X finally got the traffic in sight and stated he was turning. After climbing above the MIA I cleared the aircraft on to his destination.In my [XX] years I've never encountered this situation. I'm [reporting] this because if it happened again I might take action below the MIA. The MIA in this case is 2500 ft and with the potential collision at 2200 ft I might turn the [aircraft] at 2000 ft. I don't think I had time to ask if he could maintain his own terrain and obstruction avoidance. Plus; he was a student pilot and; in my experience; this question causes confusion. So; next time; I would probably ask if the pilot had ground contact and suggest a turn. This is an unusual situation because at most of our airports I wouldn't be able to talk to aircraft at this low an altitude. The sector transmitter is at GHM so I was able to communicate early at this airport. I would have thought that the two involved aircraft would have known about each other through Unicom I'm wondering if this should have been treated as an emergency and I should have had a 'deal' with the MIA and would have turned the aircraft while he was slightly below the MIA. I would have felt better if I had done this.

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	1350279
Time
Date	201604
Local Time Of Day	1201-1800
Place
Locale Reference	ZME.ARTCC
State Reference	TN
Environment
Light	Daylight
Aircraft 1
Make Model Name	PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	Other Instrument Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Initial Approach
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Controller reported issuing traffic to an aircraft on a missed approach. Both aircraft were below the mia and the controller could not turn the aircraft to avoid traffic. Controller later questioned if he should have done something different.