Altitude deviation altitude overshot in climb.

Attributes
ACN	298562
Time
Date	199503
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mco
State Reference	FL
Altitude	msl bound lower : 1500 msl bound upper : 3200
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : mco tower : cmh
Operator	general aviation : corporate
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 91
Navigation In Use	Other Other
Flight Phase	climbout : initial climbout : takeoff ground : preflight
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 110 flight time total : 3750 flight time type : 975
ASRS Report	298562
Person 2
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 150 flight time total : 10000 flight time type : 1000
ASRS Report	298570
Events
Anomaly	altitude deviation : overshoot non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

When I requested the clearance from orlando clearance, I wrote down and read back initial altitude of 15000 ft. I set 15000 ft in the altitude preselect window. There was no other crewmember in the cockpit at the time. Prior to takeoff I briefed the PNF of an initial altitude of 15000 ft. During the climb through 2500 ft we switched to departure control. At that time he said 'stop at 3000 ft.' we accomplished that with a slight deviation above 3000 ft. At that time the departure control said that our clearance was initially to 1500 ft. The 2 things that I learned to do to prevent this situation from occurring again is to wait until there are 2 pilots listening to the clearance and to think about what other airports are in the area and to see if an altitude is appropriate to the area. If not, then question it. Pre departure clearance could also prevent this from happening. Supplemental information from acn 298570: clearance delivery controller did not detect error in readbacks. Crew briefed departure before takeoff and were confident we knew what we were expected to do. Next time: both crewmembers in cockpit during clearance receipt and readback, controller should have detected error in readback.

Original NASA ASRS Text

Title: ALTDEV ALT OVERSHOT IN CLB.

Narrative: WHEN I REQUESTED THE CLRNC FROM ORLANDO CLRNC, I WROTE DOWN AND READ BACK INITIAL ALT OF 15000 FT. I SET 15000 FT IN THE ALT PRESELECT WINDOW. THERE WAS NO OTHER CREWMEMBER IN THE COCKPIT AT THE TIME. PRIOR TO TKOF I BRIEFED THE PNF OF AN INITIAL ALT OF 15000 FT. DURING THE CLB THROUGH 2500 FT WE SWITCHED TO DEP CTL. AT THAT TIME HE SAID 'STOP AT 3000 FT.' WE ACCOMPLISHED THAT WITH A SLIGHT DEV ABOVE 3000 FT. AT THAT TIME THE DEP CTL SAID THAT OUR CLRNC WAS INITIALLY TO 1500 FT. THE 2 THINGS THAT I LEARNED TO DO TO PREVENT THIS SIT FROM OCCURRING AGAIN IS TO WAIT UNTIL THERE ARE 2 PLTS LISTENING TO THE CLRNC AND TO THINK ABOUT WHAT OTHER ARPTS ARE IN THE AREA AND TO SEE IF AN ALT IS APPROPRIATE TO THE AREA. IF NOT, THEN QUESTION IT. PDC COULD ALSO PREVENT THIS FROM HAPPENING. SUPPLEMENTAL INFO FROM ACN 298570: CLRNC DELIVERY CTLR DID NOT DETECT ERROR IN READBACKS. CREW BRIEFED DEP BEFORE TKOF AND WERE CONFIDENT WE KNEW WHAT WE WERE EXPECTED TO DO. NEXT TIME: BOTH CREWMEMBERS IN COCKPIT DURING CLRNC RECEIPT AND READBACK, CTLR SHOULD HAVE DETECTED ERROR IN READBACK.

Data retrieved from NASA's ASRS site as of July 2007 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.