A flight crew sets assigned altitude in altitude alert window which didn't alert when it was supposed to. The flight crew noticed after they were 2000 ft above assigned altitude.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	576515
Time
Date	200303
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	navaid : bsr.vortac
State Reference	CA
Altitude	msl bound lower : 13000 msl bound upper : 15000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zoa.artcc
Operator	common carrier : air carrier
Make Model Name	Brasilia EMB-120 All Series
Operating Under FAR Part	Part 121
Navigation In Use	other vortac
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : multi engine pilot : instrument pilot : flight engineer pilot : commercial pilot : cfi
Experience	flight time last 90 days : 200 flight time total : 5500 flight time type : 1800
ASRS Report	576515
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	aircraft equipment problem : less severe altitude deviation : overshoot non adherence : clearance other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted none taken : detected after the fact
Supplementary
Problem Areas	ATC Human Performance Aircraft Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Problem arose due to the altitude alerter not having a definite 'click' for each 100 ft. Center assigned 13000 ft. The first officer engaged the autoplt (both pilots verified 13000 ft set in altitude alert) at approximately 11000 ft. Neither pilot noticed the arm light flashing on the first officer's fcp. Center gave a frequency change and when I looked at the altimeter versus the altitude alerter is when I discovered we were at 15000 ft, not 13000 ft. For some reason, the altitude alerter never gave an alert for 400 ft below or 200 ft above altitude. I told center we were level 15000 ft and she said to climb to FL230. Nothing further was said and no conflict was caused. Definitely complacency on my part after hearing 'autoplt engaged,' was a contributing human factor. Also, I should exercise better judgement in monitoring the first officer (who is inexperienced) as the PNF. No immediate action was required as I believe no traffic conflict occurred.

Original NASA ASRS Text

Title: A FLT CREW SETS ASSIGNED ALT IN ALT ALERT WINDOW WHICH DIDN'T ALERT WHEN IT WAS SUPPOSED TO. THE FLT CREW NOTICED AFTER THEY WERE 2000 FT ABOVE ASSIGNED ALT.

Narrative: PROB AROSE DUE TO THE ALT ALERTER NOT HAVING A DEFINITE 'CLICK' FOR EACH 100 FT. CTR ASSIGNED 13000 FT. THE FO ENGAGED THE AUTOPLT (BOTH PLTS VERIFIED 13000 FT SET IN ALT ALERT) AT APPROX 11000 FT. NEITHER PLT NOTICED THE ARM LIGHT FLASHING ON THE FO'S FCP. CTR GAVE A FREQ CHANGE AND WHEN I LOOKED AT THE ALTIMETER VERSUS THE ALT ALERTER IS WHEN I DISCOVERED WE WERE AT 15000 FT, NOT 13000 FT. FOR SOME REASON, THE ALT ALERTER NEVER GAVE AN ALERT FOR 400 FT BELOW OR 200 FT ABOVE ALT. I TOLD CTR WE WERE LEVEL 15000 FT AND SHE SAID TO CLB TO FL230. NOTHING FURTHER WAS SAID AND NO CONFLICT WAS CAUSED. DEFINITELY COMPLACENCY ON MY PART AFTER HEARING 'AUTOPLT ENGAGED,' WAS A CONTRIBUTING HUMAN FACTOR. ALSO, I SHOULD EXERCISE BETTER JUDGEMENT IN MONITORING THE FO (WHO IS INEXPERIENCED) AS THE PNF. NO IMMEDIATE ACTION WAS REQUIRED AS I BELIEVE NO TFC CONFLICT OCCURRED.

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.