SW3 pilot overshot his cleared altitude.

Attributes
ACN	415360
Time
Date	199810
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : mke
State Reference	WI
Altitude	msl bound lower : 11000 msl bound upper : 11400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau
Operator	general aviation : corporate
Make Model Name	Merlin III
Operating Under FAR Part	Part 91
Flight Phase	climbout : intermediate altitude cruise other
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 110 flight time total : 7400 flight time type : 25
ASRS Report	415360
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	altitude deviation : overshoot non adherence : clearance non adherence : far other anomaly other
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:

I departed VFR from unu runway 26 and called msn approach to pick up an IFR clearance to biv. At that time I was given a squawk code and told to climb and maintain 7000 ft, expect 11000 ft 'in a little while.' out of about 5000 ft, I was given a turn to 060 degrees, vectors for the climb, and told to contact ZAU. Upon checking in with center, I was cleared to 11000 ft and direct biv. At leveloff at 11000 ft, center said 'I show you 500 ft high, altimeter is 30.20.' I repeated the altimeter setting and descended about 400 ft to 11000 ft. The right altimeter was set correctly, so I assume I set the pilot's wrong on the ground prior to departure. Unfortunately, neither msn or ord issued an altimeter setting to me at time of contact. In future flts, I plan on doublechking both altimeters with kohlsman windows and actual altitude readings of both instruments. I will also request altimeter settings from facilities on initial contact, especially if they have not offered it.

Original NASA ASRS Text

Title: SW3 PLT OVERSHOT HIS CLRED ALT.

Narrative: I DEPARTED VFR FROM UNU RWY 26 AND CALLED MSN APCH TO PICK UP AN IFR CLRNC TO BIV. AT THAT TIME I WAS GIVEN A SQUAWK CODE AND TOLD TO CLB AND MAINTAIN 7000 FT, EXPECT 11000 FT 'IN A LITTLE WHILE.' OUT OF ABOUT 5000 FT, I WAS GIVEN A TURN TO 060 DEGS, VECTORS FOR THE CLB, AND TOLD TO CONTACT ZAU. UPON CHKING IN WITH CTR, I WAS CLRED TO 11000 FT AND DIRECT BIV. AT LEVELOFF AT 11000 FT, CTR SAID 'I SHOW YOU 500 FT HIGH, ALTIMETER IS 30.20.' I REPEATED THE ALTIMETER SETTING AND DSNDED ABOUT 400 FT TO 11000 FT. THE R ALTIMETER WAS SET CORRECTLY, SO I ASSUME I SET THE PLT'S WRONG ON THE GND PRIOR TO DEP. UNFORTUNATELY, NEITHER MSN OR ORD ISSUED AN ALTIMETER SETTING TO ME AT TIME OF CONTACT. IN FUTURE FLTS, I PLAN ON DOUBLECHKING BOTH ALTIMETERS WITH KOHLSMAN WINDOWS AND ACTUAL ALT READINGS OF BOTH INSTS. I WILL ALSO REQUEST ALTIMETER SETTINGS FROM FACILITIES ON INITIAL CONTACT, ESPECIALLY IF THEY HAVE NOT OFFERED IT.

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.