MD80 crew had altitude overshoot.

Attributes
ACN	449850
Time
Date	199909
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : sey.vor
State Reference	RI
Altitude	msl bound lower : 21720 msl bound upper : 22000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zbw.artcc
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Route In Use	enroute airway : ns.airway
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain instruction : instructor oversight : pic
Qualification	pilot : multi engine pilot : atp pilot : commercial
Experience	flight time last 90 days : 215 flight time total : 10500 flight time type : 954
ASRS Report	449850
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer instruction : trainee
Qualification	pilot : instrument pilot : commercial pilot : atp pilot : multi engine
Experience	flight time last 90 days : 60 flight time total : 3450 flight time type : 60
ASRS Report	449470
Events
Anomaly	altitude deviation : overshoot non adherence : clearance non adherence : company policies non adherence : published procedure
Independent Detector	aircraft equipment : altitude alert other flight crewa
Resolutory Action	flight crew : returned to assigned altitude
Supplementary
Problem Areas	Flight Crew Human Performance Company
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

PF, student first officer -- PNF, check airman. I demonstrated to the student first officer a climb out of bos using performance mode on the pms with the autoplt DFGS. At the top of climb, I set cruise in the pms at mach .60, as was the desired cruise mach on the flight plan. As the flight approached the new york area, I decided to increase our indicated airspeed to 290 KTS to conform to arrival traffic into jfk. I did not input 290 KTS into the pms, instead I set 290 KTS in the DFGS. The altitude alert sounded at FL217.2. I corrected the altitude deviation and returned to FL220. I believe that inputting the speed change in the DFGS, thus disengaging the pms, caused the altitude deviation. When selected, performance mode will operate +/-150-200 ft the desired flight level. If performance mode is disengaged while in a slight descent, the descent will continue until corrected. The lesson learned is to check and xchk the flight mode annunciator when manipulating the DFGS -- especially when using performance mode.

Original NASA ASRS Text

Title: MD80 CREW HAD ALT OVERSHOOT.

Narrative: PF, STUDENT FO -- PNF, CHK AIRMAN. I DEMONSTRATED TO THE STUDENT FO A CLBOUT OF BOS USING PERFORMANCE MODE ON THE PMS WITH THE AUTOPLT DFGS. AT THE TOP OF CLB, I SET CRUISE IN THE PMS AT MACH .60, AS WAS THE DESIRED CRUISE MACH ON THE FLT PLAN. AS THE FLT APCHED THE NEW YORK AREA, I DECIDED TO INCREASE OUR INDICATED AIRSPD TO 290 KTS TO CONFORM TO ARR TFC INTO JFK. I DID NOT INPUT 290 KTS INTO THE PMS, INSTEAD I SET 290 KTS IN THE DFGS. THE ALT ALERT SOUNDED AT FL217.2. I CORRECTED THE ALTDEV AND RETURNED TO FL220. I BELIEVE THAT INPUTTING THE SPD CHANGE IN THE DFGS, THUS DISENGAGING THE PMS, CAUSED THE ALTDEV. WHEN SELECTED, PERFORMANCE MODE WILL OPERATE +/-150-200 FT THE DESIRED FLT LEVEL. IF PERFORMANCE MODE IS DISENGAGED WHILE IN A SLIGHT DSCNT, THE DSCNT WILL CONTINUE UNTIL CORRECTED. THE LESSON LEARNED IS TO CHK AND XCHK THE FLT MODE ANNUNCIATOR WHEN MANIPULATING THE DFGS -- ESPECIALLY WHEN USING PERFORMANCE MODE.

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.