While first officer is on lavatory break; MD80 captain is cleared to descend to FL330 and reads that back but sets 300 in the altitude alerter. As first officer returns and aircraft is leveling at FL300; ATC queries crew about their altitude.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	812746
Time
Date	200811
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : zzz.vortac
State Reference	US
Altitude	msl single value : 30000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zzz.artcc
Operator	common carrier : air carrier
Make Model Name	DC-9 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 15000 flight time type : 5000
ASRS Report	812746
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 210 flight time total : 11000 flight time type : 7000
ASRS Report	812744
Events
Anomaly	altitude deviation : overshoot non adherence : clearance
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Cruising at FL350. While the first officer was in the lavatory; ZKC cleared us pilot's discretion to cross 70 mi southwest of bdf at FL330. I read back FL330 but for some reason I set FL300 in the altitude alert. As the first officer was returning; I started my descent and was given a frequency change to ZAU. When checking in; I called leaving FL340 for FL300 and was acknowledged by center. Upon reaching FL300; center called to question my altitude and gave me a number to call. I talked to both ctrs and was told there was no loss of separation but there would possibly be a 'deviation of clearance' filed. I don't know how I could have set FL300 in the alert. Obviously; if the first officer had been present; he would have questioned the altitude alert setting due to our challenge and response procedures. I'm not sure why the controller didn't question my call of FL340 for FL300.

Original NASA ASRS Text

Title: WHILE FIRST OFFICER IS ON LAVATORY BREAK; MD80 CAPTAIN IS CLEARED TO DESCEND TO FL330 AND READS THAT BACK BUT SETS 300 IN THE ALTITUDE ALERTER. AS FIRST OFFICER RETURNS AND AIRCRAFT IS LEVELING AT FL300; ATC QUERIES CREW ABOUT THEIR ALTITUDE.

Narrative: CRUISING AT FL350. WHILE THE FO WAS IN THE LAVATORY; ZKC CLRED US PLT'S DISCRETION TO CROSS 70 MI SW OF BDF AT FL330. I READ BACK FL330 BUT FOR SOME REASON I SET FL300 IN THE ALT ALERT. AS THE FO WAS RETURNING; I STARTED MY DSCNT AND WAS GIVEN A FREQ CHANGE TO ZAU. WHEN CHKING IN; I CALLED LEAVING FL340 FOR FL300 AND WAS ACKNOWLEDGED BY CTR. UPON REACHING FL300; CTR CALLED TO QUESTION MY ALT AND GAVE ME A NUMBER TO CALL. I TALKED TO BOTH CTRS AND WAS TOLD THERE WAS NO LOSS OF SEPARATION BUT THERE WOULD POSSIBLY BE A 'DEV OF CLRNC' FILED. I DON'T KNOW HOW I COULD HAVE SET FL300 IN THE ALERT. OBVIOUSLY; IF THE FO HAD BEEN PRESENT; HE WOULD HAVE QUESTIONED THE ALT ALERT SETTING DUE TO OUR CHALLENGE AND RESPONSE PROCS. I'M NOT SURE WHY THE CTLR DIDN'T QUESTION MY CALL OF FL340 FOR FL300.

Data retrieved from NASA's ASRS site as of May 2009 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.