Cleared to FL360; A320 flight crew sets FL370 even though they follow SOP verification procedures.

Attributes
ACN	796922
Time
Date	200807
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : laa.vortac
State Reference	CO
Altitude	msl bound lower : 36000 msl bound upper : 36700
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zkc.artcc
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	cruise : enroute altitude change
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument pilot : atp
Experience	flight time last 90 days : 200 flight time total : 15500 flight time type : 5900
ASRS Report	796922
Person 2
Affiliation	government : faa
Function	controller : radar
Events
Anomaly	altitude deviation : overshoot non adherence : clearance non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	controller : issued advisory flight crew : returned to assigned altitude
Supplementary
Problem Areas	Flight Crew Human Performance Aircraft
Primary Problem	Flight Crew Human Performance

Narrative:

We were in cruise wbound at FL340. Convective activity and a layer of clouds just below our altitude ahead required a climb. We asked for FL360; and were cleared to climb. First officer; PF; selected FL360 on the altitude preselect and stated; '36000 ft.' I looked at the FMA and verified '36000 ft' displayed. Altitude knob was pulled to initiate climb. This was all per our SOP. We resumed a conversation. I verified '35 for 36' as we passed FL350. First officer responded same. Next event was a call from center about our continued climb past FL360. I looked as we were passing FL367. Altitude preselect showed FL370. I quickly took control and immediately selected FL360 and descended to level off. There was no traffic conflict. I do not know how FL370 was selected. All I can surmise is the PF turned the knob inadvertently to FL370 as it was pulled to initiate the climb. While I verified the 1000 ft to level off; I missed re-verifying the leveloff altitude selected on the FMA. That error was our last line of defense; as the PF missed the incorrect leveloff altitude as well. Contributing factor was a conversation taking place during this altitude change. Another contributing factor was my laptop open on the work table; which I looked past to verify changes. I suggest that the SOP be changed to require that the altitude selected in the preselect be selected and initiated (by pulling or pushing) prior to verification. That would eliminate an inadvertent turning of the altitude preselect knob while initiating the required change (pulling or pushing). We verified and looked away probably just at the instant that the knob must have been turned.

Original NASA ASRS Text

Title: CLRED TO FL360; A320 FLT CREW SETS FL370 EVEN THOUGH THEY FOLLOW SOP VERIFICATION PROCEDURES.

Narrative: WE WERE IN CRUISE WBOUND AT FL340. CONVECTIVE ACTIVITY AND A LAYER OF CLOUDS JUST BELOW OUR ALT AHEAD REQUIRED A CLB. WE ASKED FOR FL360; AND WERE CLRED TO CLB. FO; PF; SELECTED FL360 ON THE ALT PRESELECT AND STATED; '36000 FT.' I LOOKED AT THE FMA AND VERIFIED '36000 FT' DISPLAYED. ALT KNOB WAS PULLED TO INITIATE CLB. THIS WAS ALL PER OUR SOP. WE RESUMED A CONVERSATION. I VERIFIED '35 FOR 36' AS WE PASSED FL350. FO RESPONDED SAME. NEXT EVENT WAS A CALL FROM CTR ABOUT OUR CONTINUED CLB PAST FL360. I LOOKED AS WE WERE PASSING FL367. ALT PRESELECT SHOWED FL370. I QUICKLY TOOK CTL AND IMMEDIATELY SELECTED FL360 AND DSNDED TO LEVEL OFF. THERE WAS NO TFC CONFLICT. I DO NOT KNOW HOW FL370 WAS SELECTED. ALL I CAN SURMISE IS THE PF TURNED THE KNOB INADVERTENTLY TO FL370 AS IT WAS PULLED TO INITIATE THE CLB. WHILE I VERIFIED THE 1000 FT TO LEVEL OFF; I MISSED RE-VERIFYING THE LEVELOFF ALT SELECTED ON THE FMA. THAT ERROR WAS OUR LAST LINE OF DEFENSE; AS THE PF MISSED THE INCORRECT LEVELOFF ALT AS WELL. CONTRIBUTING FACTOR WAS A CONVERSATION TAKING PLACE DURING THIS ALT CHANGE. ANOTHER CONTRIBUTING FACTOR WAS MY LAPTOP OPEN ON THE WORK TABLE; WHICH I LOOKED PAST TO VERIFY CHANGES. I SUGGEST THAT THE SOP BE CHANGED TO REQUIRE THAT THE ALT SELECTED IN THE PRESELECT BE SELECTED AND INITIATED (BY PULLING OR PUSHING) PRIOR TO VERIFICATION. THAT WOULD ELIMINATE AN INADVERTENT TURNING OF THE ALT PRESELECT KNOB WHILE INITIATING THE REQUIRED CHANGE (PULLING OR PUSHING). WE VERIFIED AND LOOKED AWAY PROBABLY JUST AT THE INSTANT THAT THE KNOB MUST HAVE BEEN TURNED.

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.