A CE680 captain reported difficulty maintaining 2;000 ft on the ruudy 4 departure from teb due to th...

Narrative:

[We were] on departure from teterboro on the ruudy 4 departure off runway 24. On departure the captain's seat slid back one position on the seat tracks. Things continued normally. Once airborne the pilot not flying selected gear up and selected navigation on the FMS. What happened thereafter to him is a mystery. As we entered the cloud conditions he announced and selected engine/inlet anti ice on as I proceeded outbound to wentz at 1;500. Upon arriving at wentz I turned toward tasca and started a climb to 2;000. As I did so I thought I had reached up and selected the autopilot on; however rather than level I noticed the airplane had continued to climb. I immediately reduced power; disconnected the autopilot and started descending back to 2;000. It was at this time that I noticed that the altitude selector was still selected to 1;500 feet; so I questioned the pilot not flying; was it not supposed to be 2;000? I selected the autopilot and it started toward 1;500 and again I disconnected the autopilot and adjusted the altitude to 2;000 in the altitude selector. It was at that time that I next noticed that the flaps were still in takeoff position. There was no 'flaps up' call so they remained in the takeoff position. I told the pilot not flying to select flaps up at that time and he did so. Shortly thereafter we were cleared to either six or seven thousand feet and there were no further issues. The altitude excursion was a maximum of 2;700 on the high end and 1;700 on the low end. Aside from the seat track issue it's one thing to fly single pilot if that's what you are prepared to do; however if you are part of a crew; then the pilot not flying is there to keep the pilot flying on track. I'm not sure where my pilot not flying was; but I suspect initially; not with me on the departure.

Original NASA ASRS Text

Title: A CE680 Captain reported difficulty maintaining 2;000 FT on the RUUDY 4 departure from TEB due to the altitude alerter being set to 1;500 FT while attempting to engage the autopilot.

Narrative: [We were] on departure from Teterboro on the RUUDY 4 departure off Runway 24. On departure the Captain's seat slid back one position on the seat tracks. Things continued normally. Once airborne the pilot not flying selected gear up and selected NAV on the FMS. What happened thereafter to him is a mystery. As we entered the cloud conditions he announced and selected engine/inlet anti ice on as I proceeded outbound to WENTZ at 1;500. Upon arriving at WENTZ I turned toward TASCA and started a climb to 2;000. As I did so I thought I had reached up and selected the autopilot on; however rather than level I noticed the airplane had continued to climb. I immediately reduced power; disconnected the autopilot and started descending back to 2;000. It was at this time that I noticed that the altitude selector was still selected to 1;500 feet; so I questioned the pilot not flying; was it not supposed to be 2;000? I selected the autopilot and it started toward 1;500 and again I disconnected the autopilot and adjusted the altitude to 2;000 in the altitude selector. It was at that time that I next noticed that the flaps were still in takeoff position. There was no 'flaps up' call so they remained in the takeoff position. I told the pilot not flying to select flaps up at that time and he did so. Shortly thereafter we were cleared to either six or seven thousand feet and there were no further issues. The altitude excursion was a maximum of 2;700 on the high end and 1;700 on the low end. Aside from the seat track issue it's one thing to fly single pilot if that's what you are prepared to do; however if you are part of a crew; then the pilot not flying is there to keep the pilot flying on track. I'm not sure where my pilot not flying was; but I suspect initially; NOT with me on the departure.

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

Attributes
ACN	1011331
Time
Date	201201
Local Time Of Day	0601-1200
Place
Locale Reference	TEB.Airport
State Reference	NJ
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Make Model Name	Cessna Citation Sovereign (C680)
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	SID RUUDY 4
Flight Plan	IFR
Component
Aircraft Component	Pilot Seat
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 60 Flight Crew Total 10800 Flight Crew Type 450
Events
Anomaly	Deviation - Altitude Overshoot Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Published Material / Policy

A CE680 captain reported difficulty maintaining 2;000 ft on the ruudy 4 departure from teb due to the altitude alerter being set to 1;500 ft while attempting to engage the autopilot.