Altitude deviation altitude overshot in climb.

Attributes
ACN	307320
Time
Date	199505
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : sxc
State Reference	CA
Altitude	msl bound lower : 24000 msl bound upper : 24400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zla
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude cruise other
Route In Use	departure other departure sid : sid enroute : direct
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 3400 flight time type : 400
ASRS Report	307320
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 200 flight time total : 7000 flight time type : 200
ASRS Report	305788
Events
Anomaly	altitude deviation : overshoot inflight encounter other non adherence : clearance other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : became reoriented flight crew : returned to intended course or assigned course
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

20 NM east of sxc and on a flight plan filed to FL280 -- passing FL200 it was reported that FL240 would be a smoother ride. We accepted FL240 as a final cruise altitude, however passing FL230 they cleared us direct rzs. As we were turning, the aircraft went through FL240 to anywhere between FL243 and FL244. We immediately descended and leveled at FL240. Nothing was said by ATC. No warnings in the cockpit went off. Supplemental information from acn 305788: our aircraft is a B-737-300 with FMS. During the transition from VOR navigation to lateral navigation for the new fix, the copilot flew above the cleared FL240 to FL244. A return to cleared altitude was accomplished. I think this deviation was caused by a fixation by both of us on switching the FMS from VOR to LNAV modes. Also, we normally cruise much high than FL240, but because of turbulence we were staying low. I think that I was used to climbing for a longer period of time after checking in with the high altitude sector, thus I didn't realize that we would be leveling almost immediately. I should have put more awareness on the vertical navigation, there was plenty of time to handle the lateral navigation after leveloff at FL240.

Original NASA ASRS Text

Title: ALTDEV ALT OVERSHOT IN CLB.

Narrative: 20 NM E OF SXC AND ON A FLT PLAN FILED TO FL280 -- PASSING FL200 IT WAS RPTED THAT FL240 WOULD BE A SMOOTHER RIDE. WE ACCEPTED FL240 AS A FINAL CRUISE ALT, HOWEVER PASSING FL230 THEY CLRED US DIRECT RZS. AS WE WERE TURNING, THE ACFT WENT THROUGH FL240 TO ANYWHERE BTWN FL243 AND FL244. WE IMMEDIATELY DSNDED AND LEVELED AT FL240. NOTHING WAS SAID BY ATC. NO WARNINGS IN THE COCKPIT WENT OFF. SUPPLEMENTAL INFO FROM ACN 305788: OUR ACFT IS A B-737-300 WITH FMS. DURING THE TRANSITION FROM VOR NAV TO LATERAL NAV FOR THE NEW FIX, THE COPLT FLEW ABOVE THE CLRED FL240 TO FL244. A RETURN TO CLRED ALT WAS ACCOMPLISHED. I THINK THIS DEV WAS CAUSED BY A FIXATION BY BOTH OF US ON SWITCHING THE FMS FROM VOR TO LNAV MODES. ALSO, WE NORMALLY CRUISE MUCH HIGH THAN FL240, BUT BECAUSE OF TURB WE WERE STAYING LOW. I THINK THAT I WAS USED TO CLBING FOR A LONGER PERIOD OF TIME AFTER CHKING IN WITH THE HIGH ALT SECTOR, THUS I DIDN'T REALIZE THAT WE WOULD BE LEVELING ALMOST IMMEDIATELY. I SHOULD HAVE PUT MORE AWARENESS ON THE VERT NAV, THERE WAS PLENTY OF TIME TO HANDLE THE LATERAL NAV AFTER LEVELOFF AT FL240.

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.