Flight crew of an air carrier medium large transport correctly sets the altitude hold for a crossing restr of FL240. However, he mind sets FL290 and levels off there. On initial call to the next sector, the controller questions the leveloff altitude.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	429153
Time
Date	199902
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : dag.vortac
State Reference	CA
Altitude	msl bound lower : 24000 msl bound upper : 29000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zla.artcc
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	cruise : enroute altitude change
Route In Use	arrival star : ns
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : flight engineer pilot : multi engine
Experience	flight time last 90 days : 100 flight time total : 16000 flight time type : 9000
ASRS Report	429153
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : multi engine pilot : commercial
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

A crossing restr was issued by ZLA to cross jokur intersection at FL240. While cruising at FL330, I read back the restr. A flight attendant entered the cockpit to ask a question. While she was talking, I put an altitude of FL290 into my mind and proceeded to execute a cruise descent to FL290. As I addressed the question by the flight attendant, the copilot was copying the las ATIS. When we changed frequency to the new sector, the controller asked us about our previous crossing restr. I had just leveled out at FL290 over jokur - obviously the altitude hold didn't capture because it was properly set at FL240. The controller issued a new descent clearance and didn't state any further concern. I believe the real problem in this event is the mixture of distraction and complacency. I allowed a false number into my mind without verification for accuracy. The distraction kept me from the normal verification process that takes place in other circumstances.

Original NASA ASRS Text

Title: FLC OF AN ACR MLG CORRECTLY SETS THE ALT HOLD FOR A XING RESTR OF FL240. HOWEVER, HE MIND SETS FL290 AND LEVELS OFF THERE. ON INITIAL CALL TO THE NEXT SECTOR, THE CTLR QUESTIONS THE LEVELOFF ALT.

Narrative: A XING RESTR WAS ISSUED BY ZLA TO CROSS JOKUR INTXN AT FL240. WHILE CRUISING AT FL330, I READ BACK THE RESTR. A FLT ATTENDANT ENTERED THE COCKPIT TO ASK A QUESTION. WHILE SHE WAS TALKING, I PUT AN ALT OF FL290 INTO MY MIND AND PROCEEDED TO EXECUTE A CRUISE DSCNT TO FL290. AS I ADDRESSED THE QUESTION BY THE FLT ATTENDANT, THE COPLT WAS COPYING THE LAS ATIS. WHEN WE CHANGED FREQ TO THE NEW SECTOR, THE CTLR ASKED US ABOUT OUR PREVIOUS XING RESTR. I HAD JUST LEVELED OUT AT FL290 OVER JOKUR - OBVIOUSLY THE ALT HOLD DIDN'T CAPTURE BECAUSE IT WAS PROPERLY SET AT FL240. THE CTLR ISSUED A NEW DSCNT CLRNC AND DIDN'T STATE ANY FURTHER CONCERN. I BELIEVE THE REAL PROB IN THIS EVENT IS THE MIXTURE OF DISTR AND COMPLACENCY. I ALLOWED A FALSE NUMBER INTO MY MIND WITHOUT VERIFICATION FOR ACCURACY. THE DISTR KEPT ME FROM THE NORMAL VERIFICATION PROCESS THAT TAKES PLACE IN OTHER CIRCUMSTANCES.

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.