TRACON controller failed to note an incorrect altitude assignment read back resulting in an airspace...

Narrative:

I was working departure radar. It was a little busy; with a couple of arrivals; a couple of departures and an arrival to a satellite airport. The satellite arrival couldn't get current weather conditions and time/attention was taken to ensure he had correct weather information. Not sure why he couldn't receive it. He mentioned a conflicting weather station also transmitting on the weather frequency. An E135 departed runway 23 and couldn't be turned on course immediately due to arrivals. His on course was about 065 degrees. He was assigned a 140 heading and an altitude of 100. He read back the 140 heading and that he was climbing to 140. I heard heading read back and didn't catch the altitude reading of 140. I know I heard the heading because it was essential for separation with inbound aircraft. I think I relaxed after that and paid relatively less attention to the altitude read back; as there were no aircraft involved above the climbing aircraft. My guess is that the pilot got confused and thought his assigned heading and altitude were the same. Nothing magic about my recommendation; getting a correct read back is essential. I preach this in OJT; starting at flight data. I believe the adage that 'what I say often isn't as important as what the pilot reads back'. A pilot's read back is my best clue as to what they understood and think they're supposed to do. Sometimes complacency can creep into our job. Pretty much every single regional jet that departs is assigned 100. It happens day in and day out. It is still essential to listen to the read back. My best recommendation is to listen better; even if no other aircraft is involved. To make every pilot read back count. I could also make a better effort to 'chunk' my information better; particularly with 2 control instructions.

Original NASA ASRS Text

Title: TRACON Controller failed to note an incorrect altitude assignment read back resulting in an airspace infraction; the reporter noting heading and altitude assignments were likely confused.

Narrative: I was working Departure RADAR. It was a little busy; with a couple of arrivals; a couple of departures and an arrival to a satellite airport. The satellite arrival couldn't get current weather conditions and time/attention was taken to ensure he had correct weather information. Not sure why he couldn't receive it. He mentioned a conflicting weather station also transmitting on the weather frequency. An E135 departed Runway 23 and couldn't be turned on course immediately due to arrivals. His on course was about 065 degrees. He was assigned a 140 heading and an altitude of 100. He read back the 140 heading and that he was climbing to 140. I heard heading read back and didn't catch the altitude reading of 140. I know I heard the heading because it was essential for separation with inbound aircraft. I think I relaxed after that and paid relatively less attention to the altitude read back; as there were no aircraft involved above the climbing aircraft. My guess is that the pilot got confused and thought his assigned heading and altitude were the same. Nothing magic about my recommendation; getting a correct read back is essential. I preach this in OJT; starting at Flight Data. I believe the adage that 'what I say often isn't as important as what the pilot reads back'. A pilot's read back is my best clue as to what they understood and think they're supposed to do. Sometimes complacency can creep into our job. Pretty much every single regional jet that departs is assigned 100. It happens day in and day out. It is still essential to listen to the read back. My best recommendation is to listen better; even if no other aircraft is involved. To make every pilot read back count. I could also make a better effort to 'chunk' my information better; particularly with 2 control instructions.

Data retrieved from NASA's ASRS site as of July 2013 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	992478
Time
Date	201202
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	EMB ERJ 140 ER/LR
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Person 1
Function	Departure Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

TRACON controller failed to note an incorrect altitude assignment read back resulting in an airspace infraction; the reporter noting heading and altitude assignments were likely confused.