Narrative:

I would appreciate you not using this narrative in any publication as it could be recognized by the facts of the issue. Climbing out from sfo on the offshore SID, first officer flying and me, the captain, doing the various PNF chores and company administrative items, as well as working the radio. First officer flying is a seasoned pilot, in the reserve flying military heavy transport as captain, has a law degree and sort of thinks like the stereotypical lawyer of many jokes today. Unfortunately, we don't like each other much and I try to keep that from entering the cockpit, but he has on occasions past sort of set me up by not 'catching' a misset navigation frequency, etc, and then being very slick about not being able to be caught at it. I don't think this is paranoid thinking on my part. As best as I can tell, he is just a tad slippery, and I do make mistakes. On our way to FL330 center called and advised us to stop climb at FL290, which to the best of my recollection, I think I set in the autoplt altitude controller and say '290' register. I then stupidly spent some time pulling the next departure's SID from my commercial chart and overlining parts of the route, etc, when center called saying our call sign and to stop climb and return to FL290. I looked up and saw the original FL330 in the window and the aircraft climbing through FL300 or FL310. The first officer didn't respond, so I thumbed the autoplt down to FL290 as quickly and smoothly as I could. He said he didn't hear the FL290 clearance, nor the call to return to FL290. I don't know--it is possible that I didn't insert FL290 into the autoplt. It is true that I wasn't paying enough attention to the aircraft during the climb and that I alone am responsible. I hope it was my blunder and that we don't have first officer's who carry their personal dislikes too far.

Related reports:

Google
 

Original NASA ASRS Text

Title: CLRNC AMENDED WITH STOP CLRNC ON CLIMB. ALT DEVIATION OVERSHOT.

Narrative: I WOULD APPRECIATE YOU NOT USING THIS NARRATIVE IN ANY PUBLICATION AS IT COULD BE RECOGNIZED BY THE FACTS OF THE ISSUE. CLBING OUT FROM SFO ON THE OFFSHORE SID, F/O FLYING AND ME, THE CAPT, DOING THE VARIOUS PNF CHORES AND COMPANY ADMINISTRATIVE ITEMS, AS WELL AS WORKING THE RADIO. F/O FLYING IS A SEASONED PLT, IN THE RESERVE FLYING MIL HVY TRANSPORT AS CAPT, HAS A LAW DEGREE AND SORT OF THINKS LIKE THE STEREOTYPICAL LAWYER OF MANY JOKES TODAY. UNFORTUNATELY, WE DON'T LIKE EACH OTHER MUCH AND I TRY TO KEEP THAT FROM ENTERING THE COCKPIT, BUT HE HAS ON OCCASIONS PAST SORT OF SET ME UP BY NOT 'CATCHING' A MISSET NAV FREQ, ETC, AND THEN BEING VERY SLICK ABOUT NOT BEING ABLE TO BE CAUGHT AT IT. I DON'T THINK THIS IS PARANOID THINKING ON MY PART. AS BEST AS I CAN TELL, HE IS JUST A TAD SLIPPERY, AND I DO MAKE MISTAKES. ON OUR WAY TO FL330 CENTER CALLED AND ADVISED US TO STOP CLB AT FL290, WHICH TO THE BEST OF MY RECOLLECTION, I THINK I SET IN THE AUTOPLT ALT CTLR AND SAY '290' REGISTER. I THEN STUPIDLY SPENT SOME TIME PULLING THE NEXT DEP'S SID FROM MY COMMERCIAL CHART AND OVERLINING PARTS OF THE RTE, ETC, WHEN CENTER CALLED SAYING OUR CALL SIGN AND TO STOP CLB AND RETURN TO FL290. I LOOKED UP AND SAW THE ORIGINAL FL330 IN THE WINDOW AND THE ACFT CLBING THROUGH FL300 OR FL310. THE F/O DIDN'T RESPOND, SO I THUMBED THE AUTOPLT DOWN TO FL290 AS QUICKLY AND SMOOTHLY AS I COULD. HE SAID HE DIDN'T HEAR THE FL290 CLRNC, NOR THE CALL TO RETURN TO FL290. I DON'T KNOW--IT IS POSSIBLE THAT I DIDN'T INSERT FL290 INTO THE AUTOPLT. IT IS TRUE THAT I WASN'T PAYING ENOUGH ATTN TO THE ACFT DURING THE CLB AND THAT I ALONE AM RESPONSIBLE. I HOPE IT WAS MY BLUNDER AND THAT WE DON'T HAVE F/O'S WHO CARRY THEIR PERSONAL DISLIKES TOO FAR.

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.