Narrative:

The events leading up to this incident actually had its roots in my flight to the kansas city area the previous nov/thu/01. My family and I made a trip from dbq to OA6 to visit my parents. The barometric pressure at OA6 was in the 29.80 to 29.90 range based on the aircraft altimeter. OA6 has no WX reporting capabilities. Due to the fact that there is no fuel available at OA6, I needed to make a quick flight to lxt to get fuel for our return trip to dbq. I set the altimeter to what I thought was field elevation at OA6 (1000 ft) and flew to lxt for fuel. The altimeter was quite a bit different than when I left it 3 days earlier so I had to make a big adjustment. After I got refueled at lxt, I taxied to the end of the runway, did my runup, and called kansas city clearance. I took off on runway 36 at lxt and contacted kansas city approach at approximately 2000 ft MSL a few mins later. I was cleared to 5000 ft and direct anx passing through 4000 ft. When I was almost straight north of anx, the approach controller said that I was cleared to 5000 ft and to descend to 5000 ft. My altimeter indicated 4900 ft at the time so I asked the controller what he showed for my altitude, and he said 6000 ft. I then asked for an altimeter setting and then realized that I had set my altimeter at OA6 1000 ft low and had not caught it. I immediately descended to 5000 ft. This is a classic low pressure to high pressure scenario. When I parked the airplane, the barometric pressure was significantly lower than when I left 3 days later. As PIC, it is my responsibility to make sure my altimeter is set properly, among all of the other preflight responsibilities. There are several factors involved in this incident. I am used to a tape style altimeter or a drum style altimeter. I do not fly with a 3 pointer altimeter very often and am not used to the display. This was a contributing factor in my missetting the altimeter to begin with. Both OA6 and lxt field elevations are very nearly 1000 ft MSL which, along with my lack of familiarity with the 3 pointer altimeter contributed to the error. There are a couple of xchk, items on the controller's part that failed me also. On my initial call-up to kansas city approach, I called with my current altitude as well as my cleared altitude. The controller didn't catch the 1000 ft discrepancy. I do not recall the controller giving me a local altimeter setting. That doesn't mean he didn't give it to me but usually I xchk issued altimeter settings with my altimeter. In the future, when the altimeter is significantly different than when I left it, I will exercise more care in setting it. Also, if ATC does not issue me an altimeter setting on initial contact, I will ask for one.

Google
 

Original NASA ASRS Text

Title: ALT OVERSHOT. ACFT ALTIMETER FAMILIARITY AND OVERNIGHT PRESSURE CHANGE ARE ISSUES.

Narrative: THE EVENTS LEADING UP TO THIS INCIDENT ACTUALLY HAD ITS ROOTS IN MY FLT TO THE KANSAS CITY AREA THE PREVIOUS NOV/THU/01. MY FAMILY AND I MADE A TRIP FROM DBQ TO OA6 TO VISIT MY PARENTS. THE BAROMETRIC PRESSURE AT OA6 WAS IN THE 29.80 TO 29.90 RANGE BASED ON THE ACFT ALTIMETER. OA6 HAS NO WX RPTING CAPABILITIES. DUE TO THE FACT THAT THERE IS NO FUEL AVAILABLE AT OA6, I NEEDED TO MAKE A QUICK FLT TO LXT TO GET FUEL FOR OUR RETURN TRIP TO DBQ. I SET THE ALTIMETER TO WHAT I THOUGHT WAS FIELD ELEVATION AT OA6 (1000 FT) AND FLEW TO LXT FOR FUEL. THE ALTIMETER WAS QUITE A BIT DIFFERENT THAN WHEN I LEFT IT 3 DAYS EARLIER SO I HAD TO MAKE A BIG ADJUSTMENT. AFTER I GOT REFUELED AT LXT, I TAXIED TO THE END OF THE RWY, DID MY RUNUP, AND CALLED KANSAS CITY CLRNC. I TOOK OFF ON RWY 36 AT LXT AND CONTACTED KANSAS CITY APCH AT APPROX 2000 FT MSL A FEW MINS LATER. I WAS CLRED TO 5000 FT AND DIRECT ANX PASSING THROUGH 4000 FT. WHEN I WAS ALMOST STRAIGHT N OF ANX, THE APCH CTLR SAID THAT I WAS CLRED TO 5000 FT AND TO DSND TO 5000 FT. MY ALTIMETER INDICATED 4900 FT AT THE TIME SO I ASKED THE CTLR WHAT HE SHOWED FOR MY ALT, AND HE SAID 6000 FT. I THEN ASKED FOR AN ALTIMETER SETTING AND THEN REALIZED THAT I HAD SET MY ALTIMETER AT OA6 1000 FT LOW AND HAD NOT CAUGHT IT. I IMMEDIATELY DSNDED TO 5000 FT. THIS IS A CLASSIC LOW PRESSURE TO HIGH PRESSURE SCENARIO. WHEN I PARKED THE AIRPLANE, THE BAROMETRIC PRESSURE WAS SIGNIFICANTLY LOWER THAN WHEN I LEFT 3 DAYS LATER. AS PIC, IT IS MY RESPONSIBILITY TO MAKE SURE MY ALTIMETER IS SET PROPERLY, AMONG ALL OF THE OTHER PREFLT RESPONSIBILITIES. THERE ARE SEVERAL FACTORS INVOLVED IN THIS INCIDENT. I AM USED TO A TAPE STYLE ALTIMETER OR A DRUM STYLE ALTIMETER. I DO NOT FLY WITH A 3 POINTER ALTIMETER VERY OFTEN AND AM NOT USED TO THE DISPLAY. THIS WAS A CONTRIBUTING FACTOR IN MY MISSETTING THE ALTIMETER TO BEGIN WITH. BOTH OA6 AND LXT FIELD ELEVATIONS ARE VERY NEARLY 1000 FT MSL WHICH, ALONG WITH MY LACK OF FAMILIARITY WITH THE 3 POINTER ALTIMETER CONTRIBUTED TO THE ERROR. THERE ARE A COUPLE OF XCHK, ITEMS ON THE CTLR'S PART THAT FAILED ME ALSO. ON MY INITIAL CALL-UP TO KANSAS CITY APCH, I CALLED WITH MY CURRENT ALT AS WELL AS MY CLRED ALT. THE CTLR DIDN'T CATCH THE 1000 FT DISCREPANCY. I DO NOT RECALL THE CTLR GIVING ME A LCL ALTIMETER SETTING. THAT DOESN'T MEAN HE DIDN'T GIVE IT TO ME BUT USUALLY I XCHK ISSUED ALTIMETER SETTINGS WITH MY ALTIMETER. IN THE FUTURE, WHEN THE ALTIMETER IS SIGNIFICANTLY DIFFERENT THAN WHEN I LEFT IT, I WILL EXERCISE MORE CARE IN SETTING IT. ALSO, IF ATC DOES NOT ISSUE ME AN ALTIMETER SETTING ON INITIAL CONTACT, I WILL ASK FOR ONE.

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.