Narrative:

The other problem on this same flight came about 3 hours later at ako VOR (akron co). I was using ako altimeter setting which was 2 hours old but close to my previous setting at gld (goodland, ks). 29.83 and 29.84 denver's altitude setting was 30.32 and was given to me by center. I thought the older setting was more consistent with what I'd been hearing for the area. There was storms moving through the area and this is probably what made things change so fast. When I crossed ako I turned, adjusted radios, and got off altitude. I thought about 75 ft. Center informed me I was 300 ft high. I reset altitude and was ok. No other aircraft was involved in either instance. A contributing factor to both instances may have been that I started the flight after a full days work.

Google
 

Original NASA ASRS Text

Title: ALT EXCURSION, WRONG ALTIMETER SETTING.

Narrative: THE OTHER PROBLEM ON THIS SAME FLT CAME ABOUT 3 HRS LATER AT AKO VOR (AKRON CO). I WAS USING AKO ALTIMETER SETTING WHICH WAS 2 HRS OLD BUT CLOSE TO MY PREVIOUS SETTING AT GLD (GOODLAND, KS). 29.83 AND 29.84 DENVER'S ALT SETTING WAS 30.32 AND WAS GIVEN TO ME BY CENTER. I THOUGHT THE OLDER SETTING WAS MORE CONSISTENT WITH WHAT I'D BEEN HEARING FOR THE AREA. THERE WAS STORMS MOVING THROUGH THE AREA AND THIS IS PROBABLY WHAT MADE THINGS CHANGE SO FAST. WHEN I CROSSED AKO I TURNED, ADJUSTED RADIOS, AND GOT OFF ALT. I THOUGHT ABOUT 75 FT. CENTER INFORMED ME I WAS 300 FT HIGH. I RESET ALT AND WAS OK. NO OTHER ACFT WAS INVOLVED IN EITHER INSTANCE. A CONTRIBUTING FACTOR TO BOTH INSTANCES MAY HAVE BEEN THAT I STARTED THE FLT AFTER A FULL DAYS WORK.

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.