Flight crew of an embraer 120 undershot their altitude during descent and holding due to forgetting to reset their altimeter upon descending through FL180.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	492810
Time
Date	200011
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : pye.vortac
State Reference	CA
Altitude	msl bound lower : 7000 msl bound upper : 7300
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : o90.tracon
Operator	common carrier : air carrier
Make Model Name	Brasilia EMB-120 All Series
Operating Under FAR Part	Part 119
Navigation In Use	Other
Flight Phase	descent : holding
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 5000 flight time type : 2500
ASRS Report	492810
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : commercial pilot : instrument
Events
Anomaly	altitude deviation : undershoot non adherence : clearance non adherence : published procedure
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : returned to assigned altitude other
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

As we descended from FL230 we were given holding instructions to hold northwest over the pye VOR on the 325 degree radial right turns and efc time of XA05Z. I was concerned that if we had to hold longer than the efc that we may have to go to our alternate of sjc. I was getting the ATIS, talking with the passenger and company, as well as working out fuel burn for holding. During all this, we never reset the altimeter to the current sfo setting of 30.23. As we leveled off, our altimeter was still set to 29.92 so we were flying 300 ft too high for about 10-15 mins. ATC did not say anything regarding altitude to us. We discovered the problem when we left holding as we started the descent checklist. Once we discovered the problem, we descended to the proper altimeter setting altitude. During this period we did not observe any traffic and no TCASII warnings were given. I discussed the situation with my first officer and we both were disappointed in the error we had made. As captain, I will make every effort not to let this happen again.

Original NASA ASRS Text

Title: FLC OF AN EMBRAER 120 UNDERSHOT THEIR ALT DURING DSCNT AND HOLDING DUE TO FORGETTING TO RESET THEIR ALTIMETER UPON DSNDING THROUGH FL180.

Narrative: AS WE DSNDED FROM FL230 WE WERE GIVEN HOLDING INSTRUCTIONS TO HOLD NW OVER THE PYE VOR ON THE 325 DEG RADIAL R TURNS AND EFC TIME OF XA05Z. I WAS CONCERNED THAT IF WE HAD TO HOLD LONGER THAN THE EFC THAT WE MAY HAVE TO GO TO OUR ALTERNATE OF SJC. I WAS GETTING THE ATIS, TALKING WITH THE PAX AND COMPANY, AS WELL AS WORKING OUT FUEL BURN FOR HOLDING. DURING ALL THIS, WE NEVER RESET THE ALTIMETER TO THE CURRENT SFO SETTING OF 30.23. AS WE LEVELED OFF, OUR ALTIMETER WAS STILL SET TO 29.92 SO WE WERE FLYING 300 FT TOO HIGH FOR ABOUT 10-15 MINS. ATC DID NOT SAY ANYTHING REGARDING ALT TO US. WE DISCOVERED THE PROB WHEN WE LEFT HOLDING AS WE STARTED THE DSCNT CHKLIST. ONCE WE DISCOVERED THE PROB, WE DSNDED TO THE PROPER ALTIMETER SETTING ALT. DURING THIS PERIOD WE DID NOT OBSERVE ANY TFC AND NO TCASII WARNINGS WERE GIVEN. I DISCUSSED THE SIT WITH MY FO AND WE BOTH WERE DISAPPOINTED IN THE ERROR WE HAD MADE. AS CAPT, I WILL MAKE EVERY EFFORT NOT TO LET THIS HAPPEN AGAIN.

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.