TRACON controller reported missing an aircraft altitude report resulting in the aircraft entering a ...

Narrative:

I was working both radar sectors combined. Tower had just scanned down the next departure strip of aircraft X. While I was waiting for aircraft X to tag I also had another aircraft to the far north that I was flashing at center and they had yet to take the flash. I called center so they would take the handoff before the aircraft entered centers airspace. While that was going on aircraft X called and amid all the talk on the frequencies that I was listening to I thought aircraft X said that he was climbing to his initial altitude of 16000 feet. I then gave him a turn heading 180 and aircraft X asked for higher as he was leveling the aircraft at 6000 feet. He was in a 6500 MVA. I immediately continued his climb and got the aircraft out of the higher MVA.its impossible to prevent human error. However; when someone is assigned to work ZZZ radar and they have to work both sectors combined the frequency congestion can be ridiculous even when the traffic is minimal. Also; clearance delivery (clearance delivery) should have caught the wrong read back in the clearance when they assigned the initial altitude of 16000 feet. I also should have caught it but I missed it in the clutter on the frequencies. It's also possible that clearance delivery marks each strip that they have to issue manually so they know that the correct altitude was issued and read back correctly.

Original NASA ASRS Text

Title: TRACON Controller reported missing an aircraft altitude report resulting in the aircraft entering a higher MVA.

Narrative: I was working both radar sectors combined. Tower had just scanned down the next departure strip of Aircraft X. While I was waiting for Aircraft X to tag I also had another aircraft to the far north that I was flashing at Center and they had yet to take the flash. I called Center so they would take the handoff before the aircraft entered Centers airspace. While that was going on Aircraft X called and amid all the talk on the frequencies that I was listening to I thought Aircraft X said that he was climbing to his initial altitude of 16000 feet. I then gave him a turn heading 180 and Aircraft X asked for higher as he was leveling the aircraft at 6000 feet. He was in a 6500 MVA. I immediately continued his climb and got the aircraft out of the higher MVA.Its impossible to prevent human error. However; when someone is assigned to work ZZZ radar and they have to work both sectors combined the frequency congestion can be ridiculous even when the traffic is minimal. Also; CD (Clearance Delivery) should have caught the wrong read back in the clearance when they assigned the initial altitude of 16000 feet. I also should have caught it but I missed it in the clutter on the frequencies. It's also possible that CD marks each strip that they have to issue manually so they know that the correct altitude was issued and read back correctly.

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	1603789
Time
Date	201812
Local Time Of Day	0601-1200
Place
Locale Reference	ZZZ.TRACON
State Reference	US
Environment
Light	Dusk
Aircraft 1
Make Model Name	Dash 8 Series Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Departure
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 3
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT

TRACON controller reported missing an aircraft altitude report resulting in the aircraft entering a higher MVA.