Phl TRACON controller reported climbing an aircraft to an incorrect altitude; after the center reque...

Attributes
ACN	1447182
Time
Date	201705
Local Time Of Day	0001-0600
Place
Locale Reference	PHL.Airport
State Reference	PA
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Person 1
Function	Departure
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 5
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Narrative:

I was working the north side of the approach airspace and ZNY called and asked for control to climb our departures to 12;000. I gave ZNY the control to climb. The next aircraft that called was aircraft X. I radar identified them and climbed them to 12;000 in an area that phl owns 10;000. I turned aircraft X to the fix on his route and noticed shortly after that he was climbing out of 10;500. I asked aircraft X to confirm assigned altitude and he answered 12;000. I made the point out to ZDC and noticed traffic at 12;000 descending eastward behind aircraft X. ZDC referenced traffic; but I left the land line to stop aircraft X at 11;000. ZDC called back about the referenced traffic but aircraft X was already back in my airspace. I then handed aircraft X off to ZNY at 12;000; which was approved by ZNY.no recommendations. I heard 12;000 when I approved ZNY control to climb; and that was in my head at the time.

Original NASA ASRS Text

Title: PHL TRACON Controller reported climbing an aircraft to an incorrect altitude; after the Center requested the controller to climb departures. Readback/hearback issues were cited as contributors to the event.

Narrative: I was working the north side of the approach airspace and ZNY called and asked for control to climb our departures to 12;000. I gave ZNY the control to climb. The next aircraft that called was Aircraft X. I radar identified them and climbed them to 12;000 in an area that PHL owns 10;000. I turned Aircraft X to the fix on his route and noticed shortly after that he was climbing out of 10;500. I asked Aircraft X to confirm assigned altitude and he answered 12;000. I made the point out to ZDC and noticed traffic at 12;000 descending eastward behind Aircraft X. ZDC referenced traffic; but I left the land line to stop Aircraft X at 11;000. ZDC called back about the referenced traffic but Aircraft X was already back in my airspace. I then handed Aircraft X off to ZNY at 12;000; which was approved by ZNY.No recommendations. I heard 12;000 when I approved ZNY control to climb; and that was in my head at the time.

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.

Phl TRACON controller reported climbing an aircraft to an incorrect altitude; after the center requested the controller to climb departures. Readback/hearback issues were cited as contributors to the event.