<< >> NASA ASRS Report 290342, November 1994

Flight crew made approach with wrong altimeter setting, and upon noticing error, pulled up, got vectors for another approach. After setting the correct altimeter setting.

Attributes
ACN	290342
Time
Date	199411
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : mbs
State Reference	MI
Altitude	msl bound lower : 2000 msl bound upper : 2200
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : mbs
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach landing other
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 240 flight time total : 9000 flight time type : 240
ASRS Report	290342
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	altitude deviation : overshoot non adherence : clearance other anomaly other
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

ZOB cleared us down from 21000 ft to 19000 ft. When 35 mi away from airport then continued step downs until 9000 ft was assigned, then approach took over and assigned 2200 ft and turn for base to VOR approach. We never had a chance to level off. Descent was continuous from 21000 ft to 2200 ft. Altimeter setting was incorrectly given to me from beginning so when approaching final or base, low altitude noticed and immediately climbed to correct and received vectors to do another approach. Approach control/tower asked if he might have induced situation. It was last flight of night at XX00 local (flight XXXX) cvg-mbs. After very turbulent day and 7 hours flying time. I think copilot not clear about 'setting' communicated and controller vector plus air conditioning malfunction close to level-off were all contributing factors.

Related reports:

• Altimeter setting - air carrier gets the wrong altimeter set...
• An approach controller questioned the altitude of an SF34L o...
• An altimeter setting is issued by approach control. The crew...
• Wrong altimeter setting. Flight crew forgot to set altimeter...
• Altimeter setting - air carrier is given the wrong altimeter...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: FLC MADE APCH WITH WRONG ALTIMETER SETTING, AND UPON NOTICING ERROR, PULLED UP, GOT VECTORS FOR ANOTHER APCH. AFTER SETTING THE CORRECT ALTIMETER SETTING.

Narrative: ZOB CLRED US DOWN FROM 21000 FT TO 19000 FT. WHEN 35 MI AWAY FROM ARPT THEN CONTINUED STEP DOWNS UNTIL 9000 FT WAS ASSIGNED, THEN APCH TOOK OVER AND ASSIGNED 2200 FT AND TURN FOR BASE TO VOR APCH. WE NEVER HAD A CHANCE TO LEVEL OFF. DSCNT WAS CONTINUOUS FROM 21000 FT TO 2200 FT. ALTIMETER SETTING WAS INCORRECTLY GIVEN TO ME FROM BEGINNING SO WHEN APCHING FINAL OR BASE, LOW ALT NOTICED AND IMMEDIATELY CLBED TO CORRECT AND RECEIVED VECTORS TO DO ANOTHER APCH. APCH CTL/TWR ASKED IF HE MIGHT HAVE INDUCED SIT. IT WAS LAST FLT OF NIGHT AT XX00 LCL (FLT XXXX) CVG-MBS. AFTER VERY TURBULENT DAY AND 7 HRS FLYING TIME. I THINK COPLT NOT CLR ABOUT 'SETTING' COMMUNICATED AND CTLR VECTOR PLUS AIR CONDITIONING MALFUNCTION CLOSE TO LEVEL-OFF WERE ALL CONTRIBUTING FACTORS.

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.