A king air pilot; unfamiliar with the avionics in the aircraft involved; leveled 600 ft above his cl...

Attributes
ACN	1012629
Time
Date	201205
Local Time Of Day	0601-1200
Place
Locale Reference	ZHU.ARTCC
State Reference	TX
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	King Air C90 E90
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	Direct
Flight Plan	IFR
Component
Aircraft Component	Altimeter
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 120 Flight Crew Total 7415 Flight Crew Type 1000
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Narrative:

After leveling off at my assigned cruise altitude of 10;000 MSL using the autopilot altitude preselect; the controller asked me to say altitude. When I looked at my pfd altitude display (garmin 600) it showed approximately 10;600 ft. When I checked the mechanical back up altimeter it showed 10;000 ft. When I cross checked the two altimeter settings I realized that the back up altimeter setting was not correct. I disengaged the autopilot and descended to 10;000 ft using the pfd altimeter and reset the autopilot to altitude hold. After talking with the owner of the aircraft on my return he informed me that the autopilot altitude capture was linked to the mechanical standby altimeter; not the pfd altimeter. The aircraft was an 'other owner' aircraft that I was flying on an infrequent basis and believed that the altitude management process was controlled by the primary pfd altimeter. I am now aware that the pfd back up altimeter must be reset at all times along with the primary and secondary altimeters and altitude capture indications must be verified on both altimeters.

Original NASA ASRS Text

Title: A King Air pilot; unfamiliar with the avionics in the aircraft involved; leveled 600 FT above his cleared altitude because the altitude select/capture mode was predicated on the reading from the standby altimeter; not his PFD altimeter; which he had failed to reset prior to takeoff.

Narrative: After leveling off at my assigned cruise altitude of 10;000 MSL using the autopilot altitude preselect; the Controller asked me to say altitude. When I looked at my PFD altitude display (Garmin 600) it showed approximately 10;600 FT. When I checked the mechanical back up altimeter it showed 10;000 FT. When I cross checked the two altimeter settings I realized that the back up altimeter setting was not correct. I disengaged the autopilot and descended to 10;000 FT using the PFD altimeter and reset the autopilot to altitude hold. After talking with the owner of the aircraft on my return he informed me that the autopilot altitude capture was linked to the mechanical standby altimeter; not the PFD altimeter. The aircraft was an 'other owner' aircraft that I was flying on an infrequent basis and believed that the altitude management process was controlled by the primary PFD altimeter. I am now aware that the PFD back up altimeter must be reset at all times along with the primary and secondary altimeters and altitude capture indications must be verified on both altimeters.

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

A king air pilot; unfamiliar with the avionics in the aircraft involved; leveled 600 ft above his cleared altitude because the altitude select/capture mode was predicated on the reading from the standby altimeter; not his pfd altimeter; which he had failed to reset prior to takeoff.