B737-300 crew recorded the ATIS altimeter setting incorrectly and misset their altimeters accordingl...

Attributes
ACN	539168
Time
Date	200202
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : stl.airport
State Reference	MO
Altitude	msl single value : 1600
Environment
Flight Conditions	IMC
Weather Elements	Ice
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : t75.tracon tower : msp.tower
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 30l other
Flight Phase	descent : approach
Route In Use	approach : instrument precision
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : commercial pilot : instrument
Experience	flight time last 90 days : 224 flight time total : 8700 flight time type : 4652
ASRS Report	539168
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	non adherence : published procedure non adherence : far non adherence : company policies other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Flight Crew Human Performance Company
Primary Problem	Flight Crew Human Performance

Narrative:

Altimeter setting error. During descent into stl, we set the local altimeter setting per the ATIS (30.44). During the ILS runway 30L approach, we noticed a discrepancy in altitude at the marker. We received a last min approach clearance change from runway 30R to runway 30L and at the marker we thought we still had the runway 30R marker tuned. At approximately 1100 ft MSL, we broke out of the WX and continued the approach to landing. After landing, we discovered the actual altimeter setting was 30.04. I do not think we deviated in altitude during the descent from cruise because we never leveled off except a gradual leveloff at 10000 ft to slow. We intercepted the ILS runway 30L GS and flew the GS to landing. The captain listened to and recorded the ATIS. There were no distrs at that time. The last min approach change was a distraction because we quickly briefed the new approach. I also do not remember stl approach or center giving us a local altimeter for descent.

Original NASA ASRS Text

Title: B737-300 CREW RECORDED THE ATIS ALTIMETER SETTING INCORRECTLY AND MISSET THEIR ALTIMETERS ACCORDINGLY.

Narrative: ALTIMETER SETTING ERROR. DURING DSCNT INTO STL, WE SET THE LCL ALTIMETER SETTING PER THE ATIS (30.44). DURING THE ILS RWY 30L APCH, WE NOTICED A DISCREPANCY IN ALT AT THE MARKER. WE RECEIVED A LAST MIN APCH CLRNC CHANGE FROM RWY 30R TO RWY 30L AND AT THE MARKER WE THOUGHT WE STILL HAD THE RWY 30R MARKER TUNED. AT APPROX 1100 FT MSL, WE BROKE OUT OF THE WX AND CONTINUED THE APCH TO LNDG. AFTER LNDG, WE DISCOVERED THE ACTUAL ALTIMETER SETTING WAS 30.04. I DO NOT THINK WE DEVIATED IN ALT DURING THE DSCNT FROM CRUISE BECAUSE WE NEVER LEVELED OFF EXCEPT A GRADUAL LEVELOFF AT 10000 FT TO SLOW. WE INTERCEPTED THE ILS RWY 30L GS AND FLEW THE GS TO LNDG. THE CAPT LISTENED TO AND RECORDED THE ATIS. THERE WERE NO DISTRS AT THAT TIME. THE LAST MIN APCH CHANGE WAS A DISTR BECAUSE WE QUICKLY BRIEFED THE NEW APCH. I ALSO DO NOT REMEMBER STL APCH OR CTR GIVING US A LCL ALTIMETER FOR DSCNT.

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-300 crew recorded the ATIS altimeter setting incorrectly and misset their altimeters accordingly.