MD80 first officer missets altimeter by 1000 ft and captain does not catch error until aircraft desc...

Attributes
ACN	829808
Time
Date	200904
Place
Locale Reference	FJC.VORTAC
State Reference	PA
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR MIP
Flight Plan	IFR
Component
Aircraft Component	Altimeter
Person 1
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Commercial Flight Crew Instrument
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 10000 Flight Crew Type 3800
Events
Anomaly	Conflict Airborne Conflict Deviation - Altitude Overshoot Deviation - Procedural Clearance

Narrative:

Episode occurred in april at around XA30L. We were proceeding from holding at mip to holding at lizzi while trying to get into lga behind a fast moving storm. We were given a descent to 13;000 ft with an altimeter of 29.16. Very low altimeters were associated with this system. The pilot flying mis-set his to 30.16 and neither one of us caught it in the business of setting up for another holding. I remember looking at it during the initial crosscheck through FL180 and seeing the .16 and continued with my tasks. The altimeter sweep hands looked normal since they were precisely 1;000 ft apart. Since I had the correct altimeter setting on my side; I was the one to notice we had gone through our cleared altitude. When I noticed; we were at 12;600 ft; about 400 ft low. We queried the controller to confirm the true setting and expedited back to 13;000 ft. As we got to 13;000 ft; another aircraft was approaching us and passed almost directly underneath at 12;000 ft! We received a TCAS TA but no RA.

Original NASA ASRS Text

Title: MD80 First Officer missets altimeter by 1000 FT and Captain does not catch error until aircraft descends below assigned altitude entering holding. Aircraft is quickly brought back to assigned altitude as TCAS traffic alert sounds. Altimeter set at 30.16 instead of 29.16.

Narrative: Episode occurred in April at around XA30L. We were proceeding from holding at MIP to holding at LIZZI while trying to get into LGA behind a fast moving storm. We were given a descent to 13;000 FT with an altimeter of 29.16. Very low altimeters were associated with this system. The pilot flying mis-set his to 30.16 and neither one of us caught it in the business of setting up for another holding. I remember looking at it during the initial crosscheck through FL180 and seeing the .16 and continued with my tasks. The altimeter sweep hands looked normal since they were precisely 1;000 FT apart. Since I had the correct altimeter setting on my side; I was the one to notice we had gone through our cleared altitude. When I noticed; we were at 12;600 FT; about 400 FT low. We queried the Controller to confirm the true setting and expedited back to 13;000 FT. As we got to 13;000 FT; another aircraft was approaching us and passed almost directly underneath at 12;000 FT! We received a TCAS TA but no RA.

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

MD80 first officer missets altimeter by 1000 ft and captain does not catch error until aircraft descends below assigned altitude entering holding. Aircraft is quickly brought back to assigned altitude as TCAS traffic alert sounds. Altimeter set at 30.16 instead of 29.16.