<< >> NASA ASRS Report 509600, April 2001

Altitude crossing restr not met when commuter captain fails to set his altimeter to local qnh prior to crossing cetus intersection near dtw, mi.

Attributes
ACN	509600
Time
Date	200104
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	intersection : cetus
State Reference	MI
Altitude	msl bound lower : 12000 msl bound upper : 12350
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air taxi
Make Model Name	Commercial Fixed Wing
Flight Phase	descent : approach
Route In Use	arrival star : n/s
Flight Plan	IFR
Person 1
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : instrument pilot : cfi pilot : atp
Experience	flight time last 90 days : 200 flight time total : 14000 flight time type : 2500
ASRS Report	509600
Events
Anomaly	altitude deviation : undershoot altitude deviation : crossing restriction not met non adherence : company policies non adherence : published procedure non adherence : clearance
Resolutory Action	flight crew : became reoriented flight crew : returned to assigned altitude
Supplementary
Problem Areas	Flight Crew Human Performance Environmental Factor
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

During descent checklist, somehow captain's altimeter was not reset from 29.92 to local altimeter of 30.27. Captain (me) was PF. We were given 12000 ft to cross cetus, which is normal on the arrival for jet aircraft. I crossed cetus at 12000 ft MSL, but still had 29.92 on my altimeter. After we were already past cetus approximately 5 mi or so, my first officer caught the error. I reset my altimeter which put me 350 ft above assigned altitude. ATC never questioned us or made note of it. What caused the problem: 1) I was distraction at the time I should have been setting my altimeter and did not complete the task. 2) my first officer did not xchk me nor I him at the proper time on the checklist. 3) checklist was not confirmed complete. Solution: always confirm every checklist complete and this would have been avoided.

Related reports:

• An air carrier B737-200 captain forgets to reset his own alt...
• Wrong altimeter setting results in an altitude deviation, an...
• An air carrier flight crew fails to make an altitude crossin...
• Late recognition by CL65 flight crew to correct altimeter se...

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

Original NASA ASRS Text

Title: ALT XING RESTR NOT MET WHEN COMMUTER CAPT FAILS TO SET HIS ALTIMETER TO LCL QNH PRIOR TO XING CETUS INTXN NEAR DTW, MI.

Narrative: DURING DSCNT CHKLIST, SOMEHOW CAPT'S ALTIMETER WAS NOT RESET FROM 29.92 TO LCL ALTIMETER OF 30.27. CAPT (ME) WAS PF. WE WERE GIVEN 12000 FT TO CROSS CETUS, WHICH IS NORMAL ON THE ARR FOR JET ACFT. I CROSSED CETUS AT 12000 FT MSL, BUT STILL HAD 29.92 ON MY ALTIMETER. AFTER WE WERE ALREADY PAST CETUS APPROX 5 MI OR SO, MY FO CAUGHT THE ERROR. I RESET MY ALTIMETER WHICH PUT ME 350 FT ABOVE ASSIGNED ALT. ATC NEVER QUESTIONED US OR MADE NOTE OF IT. WHAT CAUSED THE PROB: 1) I WAS DISTR AT THE TIME I SHOULD HAVE BEEN SETTING MY ALTIMETER AND DID NOT COMPLETE THE TASK. 2) MY FO DID NOT XCHK ME NOR I HIM AT THE PROPER TIME ON THE CHKLIST. 3) CHKLIST WAS NOT CONFIRMED COMPLETE. SOLUTION: ALWAYS CONFIRM EVERY CHKLIST COMPLETE AND THIS WOULD HAVE BEEN AVOIDED.

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.