B737 flight crew misset altimeter passing FL180 and overshot assigned altitude of 5000 ft while on r...

Attributes
ACN	570620
Time
Date	200301
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : pvd.airport
State Reference	RI
Altitude	msl bound lower : 4000 msl bound upper : 5000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pvd.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 175 flight time total : 5000 flight time type : 2000
ASRS Report	570620
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	altitude deviation : overshoot non adherence : published procedure non adherence : clearance
Independent Detector	other controllera
Resolutory Action	controller : issued advisory flight crew : returned to assigned altitude
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Passing through FL180, the altimeter to be set was 29.71. Pilot at the controls (captain) set 30.71. After leveling off at 4000 ft on the captain's altimeter, approach asked our altitude. My initial response was our assigned '5000 ft.' that's what my altimeter showed along with what the altitude window showed. I quickly looked at the captain's altimeter and was shocked to see the 1000 ft disparity. I immediately realized that the captain had set the wrong altimeter setting. However, I had also realized that I must have missed his mistake when completing the descent/approach checklist. After advising approach control, we made an uneventful climb back up to 5000 ft and was told that there was no traffic conflict. Lessons learned: because of the 1000 ft split on the altimeter, I assumed the altitude was correct -- it looked correct! Both needles were at the 12 O'clock position in level flight. In the future. I will ensure that I check the numerical setting of the altimeter, along with the 1000 ft prior aural altitude alert -- like I'm supposed to do! I learned a lot from this one!

Original NASA ASRS Text

Title: B737 FLC MISSET ALTIMETER PASSING FL180 AND OVERSHOT ASSIGNED ALT OF 5000 FT WHILE ON RADAR VECTOR TO PVD.

Narrative: PASSING THROUGH FL180, THE ALTIMETER TO BE SET WAS 29.71. PLT AT THE CTLS (CAPT) SET 30.71. AFTER LEVELING OFF AT 4000 FT ON THE CAPT'S ALTIMETER, APCH ASKED OUR ALT. MY INITIAL RESPONSE WAS OUR ASSIGNED '5000 FT.' THAT'S WHAT MY ALTIMETER SHOWED ALONG WITH WHAT THE ALT WINDOW SHOWED. I QUICKLY LOOKED AT THE CAPT'S ALTIMETER AND WAS SHOCKED TO SEE THE 1000 FT DISPARITY. I IMMEDIATELY REALIZED THAT THE CAPT HAD SET THE WRONG ALTIMETER SETTING. HOWEVER, I HAD ALSO REALIZED THAT I MUST HAVE MISSED HIS MISTAKE WHEN COMPLETING THE DSCNT/APCH CHKLIST. AFTER ADVISING APCH CTL, WE MADE AN UNEVENTFUL CLB BACK UP TO 5000 FT AND WAS TOLD THAT THERE WAS NO TFC CONFLICT. LESSONS LEARNED: BECAUSE OF THE 1000 FT SPLIT ON THE ALTIMETER, I ASSUMED THE ALT WAS CORRECT -- IT LOOKED CORRECT! BOTH NEEDLES WERE AT THE 12 O'CLOCK POS IN LEVEL FLT. IN THE FUTURE. I WILL ENSURE THAT I CHK THE NUMERICAL SETTING OF THE ALTIMETER, ALONG WITH THE 1000 FT PRIOR AURAL ALT ALERT -- LIKE I'M SUPPOSED TO DO! I LEARNED A LOT FROM THIS ONE!

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.

B737 flight crew misset altimeter passing FL180 and overshot assigned altitude of 5000 ft while on radar vector to pvd.