Altitude overshot on climb when FMC not properly programmed.

Attributes
ACN	87045
Time
Date	198805
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : crp
State Reference	TX
Altitude	msl bound lower : 22000 msl bound upper : 23000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zhu
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude cruise other
Route In Use	enroute airway : zhu
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 220 flight time total : 8000 flight time type : 4800
ASRS Report	87045
Person 2
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	altitude deviation : overshoot
Independent Detector	other controllera
Resolutory Action	flight crew : returned to intended course or assigned course other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Climb and maintain FL220. The PNF set in 220 in the MCP panel. The PNF acknowledged FL220. The PNF left the ATC frequency to get the ATIS for crp. While off the frequency the aircraft leveled off. The PNF came back on the frequency and hou center asked what our altitude was. The PNF looked at the altitude and we were at FL230. Center asked us to descend to FL220. No traffic was involved and hou center said, 'no big deal.' the problem could have occurred 1 of 2 ways--one being the last flight of the night, the crew being tired and just setting the wrong altitude in the MCP panel and not paying close enough attention to the altitude set. Being that I set the altitude, I felt I set 220 in the MCP panel. We have had a problem in the past by not getting the knob on the MCP panel to rest in the proper detent. Therefore, it would go to an altitude on either side of the set altitude, in this case the higher detent. I feel this problem is created by rapidly setting the MCP altitude and also shallow detents of the MCP altitude knob.

Original NASA ASRS Text

Title: ALT OVERSHOT ON CLIMB WHEN FMC NOT PROPERLY PROGRAMMED.

Narrative: CLB AND MAINTAIN FL220. THE PNF SET IN 220 IN THE MCP PANEL. THE PNF ACKNOWLEDGED FL220. THE PNF LEFT THE ATC FREQ TO GET THE ATIS FOR CRP. WHILE OFF THE FREQ THE ACFT LEVELED OFF. THE PNF CAME BACK ON THE FREQ AND HOU CENTER ASKED WHAT OUR ALT WAS. THE PNF LOOKED AT THE ALT AND WE WERE AT FL230. CENTER ASKED US TO DSND TO FL220. NO TFC WAS INVOLVED AND HOU CENTER SAID, 'NO BIG DEAL.' THE PROB COULD HAVE OCCURRED 1 OF 2 WAYS--ONE BEING THE LAST FLT OF THE NIGHT, THE CREW BEING TIRED AND JUST SETTING THE WRONG ALT IN THE MCP PANEL AND NOT PAYING CLOSE ENOUGH ATTN TO THE ALT SET. BEING THAT I SET THE ALT, I FELT I SET 220 IN THE MCP PANEL. WE HAVE HAD A PROB IN THE PAST BY NOT GETTING THE KNOB ON THE MCP PANEL TO REST IN THE PROPER DETENT. THEREFORE, IT WOULD GO TO AN ALT ON EITHER SIDE OF THE SET ALT, IN THIS CASE THE HIGHER DETENT. I FEEL THIS PROB IS CREATED BY RAPIDLY SETTING THE MCP ALT AND ALSO SHALLOW DETENTS OF THE MCP ALT KNOB.

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