Narrative:

We were climbing west out of albany, ny, and had filed for 16000 ft as a final. A deep surface low was just passing new york state at the time with altimeter settings of 29.20 inches in syracuse and 29.18 inches in buffalo. 16000 ft put us near the tops of the clouds with light to moderate rime icing. A B737 just south of our position had reported severe icing at 15000 ft so we asked for FL180 to get above the clouds. ZBW gave us 17000 ft for starters, but we were still in the tops, in the icing. Level at 17000 ft I ran the deice boot cycle and found that the right outer segment would not inflate -- leaving the 1/2 inch of accumulated ice on that section. Boston then gave us 19000 ft for an altitude. I set 19000 ft in the altitude select window of the automatic flight control system (afcs autoplt). The temperature was -30 degrees C and we were fairly light, so the climb performance was still very good at 1200-1500 FPM. During this climb I was attempting to get the outer right boot to inflate manually, while also rechking the other segments. Passing FL180 for FL190, I called '18 for 19, altimeters 29.92.' however, being tied up with the deice panel, I did not immediately reset the altimeter. We were through FL183 when I began to slowly reset my altimeter, although the first officer was the PF the afcs was tied to my instruments (only instruments integrated with the RNAV system). Due to the extraordinarily low altimeter setting of 29.18 inches, resetting to 29.92 inches made nearly an 800 ft increase in the indicated altitude. We also climbed several hundred ft during my resetting, so by the time I was nearing 29.92 inches, I recognized that we would probably indicate above FL190 by the time the altimeter was reset. So I instructed the first officer to level off and start a slow descent, realizing we needed to adjust to indicate FL190. (The leveloff probably took 100 or 200 ft also, due to the rate of climb.) indeed, we indicated FL194 by that time, but already in a slow descent by the time my altimeter was fully set. ZBW queried us on our assigned altitude. I responded FL190. He said he indicated 500 ft high. I responded that we were correcting. I did not explain the unusual circumstances to him. Flight levels above FL180 are not a frequent occurrence with us, probably only 5 or 6 times in the last yr. Callback conversation with reporter revealed the following information: this reporter states that the DH8 deice boot problem was likely just a result of a frozen pneumatic line for that boot segment (there are about 5 segments per wing), and that he just didn't think about the significance of the low altimeter until after the fact.

Google
 

Original NASA ASRS Text

Title: AN EQUIP MALFUNCTION AND A LOW ALTIMETER SETTING WITH AN ALT ASSIGNMENT AT THE LOWEST USABLE FLT LEVEL CONTRIBUTED TO A DHC8 FLC'S FAILURE TO LEVEL AT FL190. ALTDEV ALT OVERSHOT.

Narrative: WE WERE CLBING W OUT OF ALBANY, NY, AND HAD FILED FOR 16000 FT AS A FINAL. A DEEP SURFACE LOW WAS JUST PASSING NEW YORK STATE AT THE TIME WITH ALTIMETER SETTINGS OF 29.20 INCHES IN SYRACUSE AND 29.18 INCHES IN BUFFALO. 16000 FT PUT US NEAR THE TOPS OF THE CLOUDS WITH LIGHT TO MODERATE RIME ICING. A B737 JUST S OF OUR POS HAD RPTED SEVERE ICING AT 15000 FT SO WE ASKED FOR FL180 TO GET ABOVE THE CLOUDS. ZBW GAVE US 17000 FT FOR STARTERS, BUT WE WERE STILL IN THE TOPS, IN THE ICING. LEVEL AT 17000 FT I RAN THE DEICE BOOT CYCLE AND FOUND THAT THE R OUTER SEGMENT WOULD NOT INFLATE -- LEAVING THE 1/2 INCH OF ACCUMULATED ICE ON THAT SECTION. BOSTON THEN GAVE US 19000 FT FOR AN ALT. I SET 19000 FT IN THE ALT SELECT WINDOW OF THE AUTOMATIC FLT CTL SYS (AFCS AUTOPLT). THE TEMP WAS -30 DEGS C AND WE WERE FAIRLY LIGHT, SO THE CLB PERFORMANCE WAS STILL VERY GOOD AT 1200-1500 FPM. DURING THIS CLB I WAS ATTEMPTING TO GET THE OUTER R BOOT TO INFLATE MANUALLY, WHILE ALSO RECHKING THE OTHER SEGMENTS. PASSING FL180 FOR FL190, I CALLED '18 FOR 19, ALTIMETERS 29.92.' HOWEVER, BEING TIED UP WITH THE DEICE PANEL, I DID NOT IMMEDIATELY RESET THE ALTIMETER. WE WERE THROUGH FL183 WHEN I BEGAN TO SLOWLY RESET MY ALTIMETER, ALTHOUGH THE FO WAS THE PF THE AFCS WAS TIED TO MY INSTS (ONLY INSTS INTEGRATED WITH THE RNAV SYS). DUE TO THE EXTRAORDINARILY LOW ALTIMETER SETTING OF 29.18 INCHES, RESETTING TO 29.92 INCHES MADE NEARLY AN 800 FT INCREASE IN THE INDICATED ALT. WE ALSO CLBED SEVERAL HUNDRED FT DURING MY RESETTING, SO BY THE TIME I WAS NEARING 29.92 INCHES, I RECOGNIZED THAT WE WOULD PROBABLY INDICATE ABOVE FL190 BY THE TIME THE ALTIMETER WAS RESET. SO I INSTRUCTED THE FO TO LEVEL OFF AND START A SLOW DSCNT, REALIZING WE NEEDED TO ADJUST TO INDICATE FL190. (THE LEVELOFF PROBABLY TOOK 100 OR 200 FT ALSO, DUE TO THE RATE OF CLB.) INDEED, WE INDICATED FL194 BY THAT TIME, BUT ALREADY IN A SLOW DSCNT BY THE TIME MY ALTIMETER WAS FULLY SET. ZBW QUERIED US ON OUR ASSIGNED ALT. I RESPONDED FL190. HE SAID HE INDICATED 500 FT HIGH. I RESPONDED THAT WE WERE CORRECTING. I DID NOT EXPLAIN THE UNUSUAL CIRCUMSTANCES TO HIM. FLT LEVELS ABOVE FL180 ARE NOT A FREQUENT OCCURRENCE WITH US, PROBABLY ONLY 5 OR 6 TIMES IN THE LAST YR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THIS RPTR STATES THAT THE DH8 DEICE BOOT PROB WAS LIKELY JUST A RESULT OF A FROZEN PNEUMATIC LINE FOR THAT BOOT SEGMENT (THERE ARE ABOUT 5 SEGMENTS PER WING), AND THAT HE JUST DIDN'T THINK ABOUT THE SIGNIFICANCE OF THE LOW ALTIMETER UNTIL AFTER THE FACT.

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.