Narrative:

We departed hpn on sep/xa/98. During taxi and prior, it was indicated that the severe WX avoidance program would be in effect and we were advised to expect rerouting after departure via the westchester 9 departure. ATC gave us radar vectors (consisting of a box pattern) in order to coordinate the rerte. During the initial climb, which constituted intermediate leveloffs, we were advised that our mode C indicated 16700 ft when level at 17000 ft. I immediately asked for current altimeter setting, which ATC gave as 29.69 (jfk). The aircraft's altimeters were set 29.97. The error was obvious. Referring back to the hpn ATIS, altimeter was 29.97. The xxz sa at hpn was 29.79. I can't honestly say if the airport ATIS was 29.79 or 29.97. The original error was not noticed at hpn probably because of numerous distrs arising from the encroaching severe WX. We had written the hpn ATIS as 29.97 on the scratch pad but failed to observe the indicated altitude on the ground at hpn. Factors I believe contributed to this error were the arriving on passenger 20 mins prior to the planned departure time. Gate hold procedures and numerous ATC communications all occurring at critical times in the checklist procedure. None of which excuse such an oversight. Befuddling is the fact that no other ATC facilities reported the variance even though leveloffs at various altitudes were made during the climb to 17000 ft. ATC advised us of the error when level at 17000 ft. Problem was resolved with the correct altimeter setting entry. ATC did not indicate if there had been any conflicts with other aircraft.

Google
 

Original NASA ASRS Text

Title: MDT CREW MISSET ALTIMETER AT DEP STATION.

Narrative: WE DEPARTED HPN ON SEP/XA/98. DURING TAXI AND PRIOR, IT WAS INDICATED THAT THE SEVERE WX AVOIDANCE PROGRAM WOULD BE IN EFFECT AND WE WERE ADVISED TO EXPECT REROUTING AFTER DEP VIA THE WESTCHESTER 9 DEP. ATC GAVE US RADAR VECTORS (CONSISTING OF A BOX PATTERN) IN ORDER TO COORDINATE THE RERTE. DURING THE INITIAL CLB, WHICH CONSTITUTED INTERMEDIATE LEVELOFFS, WE WERE ADVISED THAT OUR MODE C INDICATED 16700 FT WHEN LEVEL AT 17000 FT. I IMMEDIATELY ASKED FOR CURRENT ALTIMETER SETTING, WHICH ATC GAVE AS 29.69 (JFK). THE ACFT'S ALTIMETERS WERE SET 29.97. THE ERROR WAS OBVIOUS. REFERRING BACK TO THE HPN ATIS, ALTIMETER WAS 29.97. THE XXZ SA AT HPN WAS 29.79. I CAN'T HONESTLY SAY IF THE ARPT ATIS WAS 29.79 OR 29.97. THE ORIGINAL ERROR WAS NOT NOTICED AT HPN PROBABLY BECAUSE OF NUMEROUS DISTRS ARISING FROM THE ENCROACHING SEVERE WX. WE HAD WRITTEN THE HPN ATIS AS 29.97 ON THE SCRATCH PAD BUT FAILED TO OBSERVE THE INDICATED ALT ON THE GND AT HPN. FACTORS I BELIEVE CONTRIBUTED TO THIS ERROR WERE THE ARRIVING ON PAX 20 MINS PRIOR TO THE PLANNED DEP TIME. GATE HOLD PROCS AND NUMEROUS ATC COMS ALL OCCURRING AT CRITICAL TIMES IN THE CHKLIST PROC. NONE OF WHICH EXCUSE SUCH AN OVERSIGHT. BEFUDDLING IS THE FACT THAT NO OTHER ATC FACILITIES RPTED THE VARIANCE EVEN THOUGH LEVELOFFS AT VARIOUS ALTS WERE MADE DURING THE CLB TO 17000 FT. ATC ADVISED US OF THE ERROR WHEN LEVEL AT 17000 FT. PROB WAS RESOLVED WITH THE CORRECT ALTIMETER SETTING ENTRY. ATC DID NOT INDICATE IF THERE HAD BEEN ANY CONFLICTS WITH OTHER ACFT.

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.