Narrative:

During departure on runway 24 performing the TEB5 departure; we received a low altitude warning from the taws. After check with departure; it was determined that our altitude was lower than what was indicated on the altimeter. After a quick cross check of altimeters; it was determined that the captain's altimeter was set lower than the copilot's. A climb was initiated and altimeters corrected. The situation was caused by the captain putting in the wrong altimeter setting. At the time the setting was set (by me) the captain commented that it appeared to be a very low setting. The copilot said yes it was. To avoid the problem in the future; the unit SOP has to be revised to repeating the altimeter twice and assuring all altimeters are set to the proper setting.supplemental information from acn 723177: while captain (PF) was occupied with duties outside the aircraft; I (PNF) went to the aircraft to obtain the IFR clearance and ATIS information. After obtaining both; I set the current altimeter setting in the copilot standby barometric altimeter; but neglected to set it in the copilot's main altimeter. When the captain arrived in the aircraft; I briefed him on the current ATIS information -- including altimeter setting -- and he acknowledged. The captain set in an erroneous altimeter setting in his altimeter; and I was remiss in cross checking; not only his setting but the setting in the copilot's primary altimeter. After takeoff from runway 24; the PF altimeter indicated he was too high for the departure; and began corrective action to comply with teb 5 departure altitude restrictions (1500 ft). He began descent to the called for altitude; resulting in a GPWS alert and a call from ny departure control inquiring about our low altitude. A climb was initiated immediately. The cockpit altimeter setting error was immediately corrected and the flight proceeded uneventfully to its destination. The problem arose as a result of the PNF's unfamiliarity with this particular aircraft and the local area. Local procedures have been implemented to prevent a reoccurrence; and ensure proper cockpit cross checking.callback conversation with reporter acn 723177 revealed the following information: the reporter states that he is fairly new to this model citation and did not perform some cross checks that he would normally perform. The captain actually set his altimeter one inch high; which went undetected until airborne.

Google
 

Original NASA ASRS Text

Title: CE560 CAPT MISSETS ALTIMETER BY ONE INCH MERCURY ON DEP FROM TEB.

Narrative: DURING DEP ON RWY 24 PERFORMING THE TEB5 DEP; WE RECEIVED A LOW ALT WARNING FROM THE TAWS. AFTER CHK WITH DEP; IT WAS DETERMINED THAT OUR ALT WAS LOWER THAN WHAT WAS INDICATED ON THE ALTIMETER. AFTER A QUICK CROSS CHK OF ALTIMETERS; IT WAS DETERMINED THAT THE CAPT'S ALTIMETER WAS SET LOWER THAN THE COPLT'S. A CLB WAS INITIATED AND ALTIMETERS CORRECTED. THE SITUATION WAS CAUSED BY THE CAPT PUTTING IN THE WRONG ALTIMETER SETTING. AT THE TIME THE SETTING WAS SET (BY ME) THE CAPT COMMENTED THAT IT APPEARED TO BE A VERY LOW SETTING. THE COPLT SAID YES IT WAS. TO AVOID THE PROB IN THE FUTURE; THE UNIT SOP HAS TO BE REVISED TO REPEATING THE ALTIMETER TWICE AND ASSURING ALL ALTIMETERS ARE SET TO THE PROPER SETTING.SUPPLEMENTAL INFO FROM ACN 723177: WHILE CAPT (PF) WAS OCCUPIED WITH DUTIES OUTSIDE THE ACFT; I (PNF) WENT TO THE ACFT TO OBTAIN THE IFR CLRNC AND ATIS INFO. AFTER OBTAINING BOTH; I SET THE CURRENT ALTIMETER SETTING IN THE COPLT STANDBY BAROMETRIC ALTIMETER; BUT NEGLECTED TO SET IT IN THE COPLT'S MAIN ALTIMETER. WHEN THE CAPT ARRIVED IN THE ACFT; I BRIEFED HIM ON THE CURRENT ATIS INFO -- INCLUDING ALTIMETER SETTING -- AND HE ACKNOWLEDGED. THE CAPT SET IN AN ERRONEOUS ALTIMETER SETTING IN HIS ALTIMETER; AND I WAS REMISS IN CROSS CHKING; NOT ONLY HIS SETTING BUT THE SETTING IN THE COPLT'S PRIMARY ALTIMETER. AFTER TKOF FROM RWY 24; THE PF ALTIMETER INDICATED HE WAS TOO HIGH FOR THE DEP; AND BEGAN CORRECTIVE ACTION TO COMPLY WITH TEB 5 DEP ALT RESTRICTIONS (1500 FT). HE BEGAN DSCNT TO THE CALLED FOR ALT; RESULTING IN A GPWS ALERT AND A CALL FROM NY DEP CTL INQUIRING ABOUT OUR LOW ALT. A CLB WAS INITIATED IMMEDIATELY. THE COCKPIT ALTIMETER SETTING ERROR WAS IMMEDIATELY CORRECTED AND THE FLT PROCEEDED UNEVENTFULLY TO ITS DEST. THE PROBLEM AROSE AS A RESULT OF THE PNF'S UNFAMILIARITY WITH THIS PARTICULAR ACFT AND THE LOCAL AREA. LOCAL PROCS HAVE BEEN IMPLEMENTED TO PREVENT A REOCCURRENCE; AND ENSURE PROPER COCKPIT CROSS CHKING.CALLBACK CONVERSATION WITH RPTR ACN 723177 REVEALED THE FOLLOWING INFO: THE RPTR STATES THAT HE IS FAIRLY NEW TO THIS MODEL CITATION AND DID NOT PERFORM SOME CROSS CHKS THAT HE WOULD NORMALLY PERFORM. THE CAPT ACTUALLY SET HIS ALTIMETER ONE INCH HIGH; WHICH WENT UNDETECTED UNTIL AIRBORNE.

Data retrieved from NASA's ASRS site as of January 2009 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.