Ord tower controller reported an aircraft conducting a go-around flew below the minimum vectoring al...

Narrative:

Aircraft X declared a go-around due to windshear on short final to runway 27R. As the local controller; I issued go-around instructions of runway heading climb to 2;100 feet; which is the MVA in that immediate part of the airspace. There was a heavy jet departure from runway 28R crossing my traffic's departure path; which I was aiming to stay 1;000 feet below for wake turbulence. Then I advised the other local controller; position 3LC; and they coordinated my go-around instructions into their airspace at 5;000 feet and 040 heading. I then issued these instructions to the aircraft X pilot; no response; then issued a landing clearance to a short final arrival; answered a question about my instructions to my supervisor on the shout line; then re-issued the turn and climb to the aircraft X pilot; this time with a read back. By this point in time; aircraft X was 2 miles off the departure end of the runway; and had entered an airspace with a MVA of 2;500 feet while flying at 2;100 feet. No loss of separation or wake turbulence occurred; flight continued without incident.ensure that heavy jet traffic are not turned too early toward other runways to protect for possible go-arounds. Advise supervisor to not use a shout line or perhaps wait longer to inquire the busy controller. Prioritize pilot read backs of critical instructions over other duties.

Original NASA ASRS Text

Title: ORD Tower Controller reported an aircraft conducting a go-around flew below the Minimum Vectoring Altitude because they did not hear their go-around instructions the first time they were issued.

Narrative: Aircraft X declared a go-around due to windshear on short final to Runway 27R. As the Local Controller; I issued go-around instructions of runway heading climb to 2;100 feet; which is the MVA in that immediate part of the airspace. There was a heavy jet departure from Runway 28R crossing my traffic's departure path; which I was aiming to stay 1;000 feet below for wake turbulence. Then I advised the other Local Controller; position 3LC; and they coordinated my go-around instructions into their airspace at 5;000 feet and 040 heading. I then issued these instructions to the Aircraft X pilot; no response; then issued a landing clearance to a short final arrival; answered a question about my instructions to my Supervisor on the shout line; then re-issued the turn and climb to the Aircraft X pilot; this time with a read back. By this point in time; Aircraft X was 2 miles off the departure end of the runway; and had entered an airspace with a MVA of 2;500 feet while flying at 2;100 feet. No loss of separation or wake turbulence occurred; flight continued without incident.Ensure that heavy jet traffic are not turned too early toward other runways to protect for possible go-arounds. Advise Supervisor to not use a shout line or perhaps wait longer to inquire the busy controller. Prioritize pilot read backs of critical instructions over other duties.

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	1654982
Time
Date	201906
Local Time Of Day	1801-2400
Place
Locale Reference	ORD.Tower
State Reference	IL
Aircraft 1
Make Model Name	EMB ERJ 145 ER/LR
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 0.5
Events
Anomaly	ATC Issue All Types Inflight Event / Encounter Weather / Turbulence Inflight Event / Encounter CFTT / CFIT

Ord tower controller reported an aircraft conducting a go-around flew below the minimum vectoring altitude because they did not hear their go-around instructions the first time they were issued.