A TRACON departure controller reported two aircraft called him executing missed approaches due to wi...

Narrative:

Aircraft X was on approach talking to tower. Tower called requesting control of aircraft X so he could clear him for the visual approach. Aircraft X was cleared for the visual approach. Aircraft Y was several miles behind aircraft X and reported the runway in sight; and was cleared for the visual approach. The spacing looked good so aircraft Y was then shipped to tower. Tower called moments later to inform me that both aircraft were going around due to wind shear and they were now requesting the opposite direction runway. I believe my mistake in this moment was that as a radar controller; I should have given tower altitudes and headings to give to both aircraft before shipping them to me. At the very least; I should have inquired about what both aircraft would be doing when they came to me. Aircraft X checked in first requesting an ILS approach. He was in a climb through 3;800 feet in a 3;300 feet minimum vectoring altitude (MVA) and appeared to be runway heading so I assumed he had missed approach instructions. Shortly after; he leveled off at 4;000 feet. When I saw this; I immediately issued a climb to 7;000 feet but by then he entered a 4;200 foot MVA at 4;000 feet. Additionally; his response was asking me for a heading. I vectored him out for an ILS approach. Aircraft Y checked on at 3;800 feet in a 5;000 feet MVA. I did not issue him a climb or heading. I asked if he still had the runway in sight and wanted to do a visual approach. He said yes to both questions so I cleared him for the visual approach and shipped him to tower. The tower could have kept both aircraft on their frequency and worked them in the pattern since both aircraft have the runway in sight. He could have just changed them to the opposite direction runway. If that was not an option; then I should have given altitudes and headings for him to give the aircraft prior to them being returned to my frequency. We need standard missed approach instructions for visual approaches at for both runways.

Original NASA ASRS Text

Title: A TRACON Departure Controller reported two aircraft called him executing missed approaches due to windshear and flew below the Minimum Vectoring Altitude due to lack of coordination and no established procedure.

Narrative: Aircraft X was on approach talking to Tower. Tower called requesting control of Aircraft X so he could clear him for the visual approach. Aircraft X was cleared for the visual approach. Aircraft Y was several miles behind Aircraft X and reported the runway in sight; and was cleared for the visual approach. The spacing looked good so Aircraft Y was then shipped to Tower. Tower called moments later to inform me that both aircraft were going around due to wind shear and they were now requesting the opposite direction runway. I believe my mistake in this moment was that as a Radar Controller; I should have given Tower altitudes and headings to give to both aircraft before shipping them to me. At the very least; I should have inquired about what both aircraft would be doing when they came to me. Aircraft X checked in first requesting an ILS approach. He was in a climb through 3;800 feet in a 3;300 feet minimum vectoring altitude (MVA) and appeared to be runway heading so I assumed he had missed approach instructions. Shortly after; he leveled off at 4;000 feet. When I saw this; I immediately issued a climb to 7;000 feet but by then he entered a 4;200 foot MVA at 4;000 feet. Additionally; his response was asking me for a heading. I vectored him out for an ILS approach. Aircraft Y checked on at 3;800 feet in a 5;000 feet MVA. I did not issue him a climb or heading. I asked if he still had the runway in sight and wanted to do a visual approach. He said yes to both questions so I cleared him for the visual approach and shipped him to Tower. The Tower could have kept both aircraft on their frequency and worked them in the pattern since both aircraft have the runway in sight. He could have just changed them to the opposite direction runway. If that was not an option; then I should have given altitudes and headings for him to give the aircraft prior to them being returned to my frequency. We need standard missed approach instructions for visual approaches at for both runways.

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	1607672
Time
Date	201901
Local Time Of Day	1801-2400
Place
Locale Reference	EUG.TRACON
State Reference	OR
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Bombardier/Canadair Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Cessna Aircraft Undifferentiated or Other Model
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Inflight Event / Encounter Weather / Turbulence Inflight Event / Encounter CFTT / CFIT

A TRACON departure controller reported two aircraft called him executing missed approaches due to windshear and flew below the minimum vectoring altitude due to lack of coordination and no established procedure.