TRACON controllers reported an aircraft on an assigned heading went NORDO and flew below the minimum...

Attributes
ACN	1653364
Time
Date	201906
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	Marginal
Light	Night
Aircraft 1
Make Model Name	Small Transport
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
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) 8
Person 2
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 3.7
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Other / Unknown Inflight Event / Encounter CFTT / CFIT

Narrative:

Aircraft X was IFR to ZZZ1 trying to beat a line of severe weather to the airport. He went around at ZZZ1 and I cleared him to ZZZ at the pilot's request. I assigned a vector and altitude to put him in sequence and then handed him off to the final controller for the rest. Final put aircraft X on a base turn heading 280. The pilot lost communications and flew into a 2200 foot MVA (minimum vectoring altitude); then a 3000 foot MVA and turned on his own to the south and climbed to 2500 feet in a 2600 foot MVA. Before hitting all the mvas; we tried literally everything. We tried center; other sectors and adjacent airport towers frequencies; tried guard and got no response at all. Instructions to climb immediately to 3000 feet were even issued on guard before the MVA violation. Eventually; he checked on with the tower and tower climbed him to 3000 feet and worked him in so he wouldn't have to change frequencies. He landed safely. I found out this morning that the pilot had a stuck mic and was the only one who could fly the plane. He was having to reach over to the copilot seat to use the mic for communications.

Original NASA ASRS Text

Title: TRACON controllers reported an aircraft on an assigned heading went NORDO and flew below the Minimum Vectoring Altitude.

Narrative: Aircraft X was IFR to ZZZ1 trying to beat a line of severe weather to the airport. He went around at ZZZ1 and I cleared him to ZZZ at the pilot's request. I assigned a vector and altitude to put him in sequence and then handed him off to the Final Controller for the rest. Final put Aircraft X on a base turn heading 280. The pilot lost communications and flew into a 2200 foot MVA (Minimum Vectoring Altitude); then a 3000 foot MVA and turned on his own to the south and climbed to 2500 feet in a 2600 foot MVA. Before hitting all the MVAs; we tried literally everything. We tried Center; other sectors and adjacent airport Towers frequencies; tried Guard and got no response at all. Instructions to climb immediately to 3000 feet were even issued on guard before the MVA violation. Eventually; he checked on with the Tower and Tower climbed him to 3000 feet and worked him in so he wouldn't have to change frequencies. He landed safely. I found out this morning that the pilot had a stuck mic and was the only one who could fly the plane. He was having to reach over to the copilot seat to use the mic for communications.

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.

TRACON controllers reported an aircraft on an assigned heading went NORDO and flew below the minimum vectoring altitude.