Narrative:

Passenger showed up one hour early so we both felt rushed for time. We were given the ruudy 4 departure off of runway 24. The takeoff brief the first officer gave said he would takeoff in navigation mode and ask me to select autopilot on at flap retraction and let the autopilot fly the plane since it is a high work load environment. When autopilot was selected on the plane immediately turned to the right which took us off course. I pressed the heading button and the first officer flew it in heading mode and I reset the autopilot which caused enough distraction for both of us to miss the altitude. We went about 150 ft above the assigned altitude of 1;500 ft. Departure asked us if we were flying the ruudy 4 departure. I answered that we were flying the ruudy 4. He then gave us a climb to 10;000 and the rest of the flight was uneventful. What I didn't know; until after the deviation occurred; was that I did not set the flight director mode controller to the first officer's side. So the autopilot did exactly what I asked it to do. It flew the navigation course that I had set in my side not what the first officer had set in his side. I did not ensure that my side was set up exactly like the first officer's. In fact my side was still set to the ILS frequency that we used 5 hours ago when we landed coming into teb. Had I ensured that the flight director mode controller was set to the first officer's side there wouldn't have been a deviation. Be much more vigilant and ensure the automation is set up correctly. Not be so rushed even when passengers are asking to leave. Follow the checklist slowly. Be quicker to remove automation when it is distracting. Don't disengage the autopilot. That would have saved us if we would have flown it in bug mode with autopilot engaged.

Related reports:

Google
 

Original NASA ASRS Text

Title: CE560 Captain reports track and altitude deviations during the RUUDY 4 RNAV departure from TEB due to improper flight guidance setup prior to departure.

Narrative: Passenger showed up one hour early so we both felt rushed for time. We were given the RUUDY 4 departure off of Runway 24. The takeoff brief the First Officer gave said he would takeoff in NAV mode and ask me to select autopilot on at flap retraction and let the autopilot fly the plane since it is a high work load environment. When autopilot was selected on the plane immediately turned to the right which took us off course. I pressed the heading button and the First Officer flew it in heading mode and I reset the autopilot which caused enough distraction for both of us to miss the altitude. We went about 150 FT above the assigned altitude of 1;500 FT. Departure asked us if we were flying the RUUDY 4 departure. I answered that we were flying the RUUDY 4. He then gave us a climb to 10;000 and the rest of the flight was uneventful. What I didn't know; until after the deviation occurred; was that I did not set the flight director mode controller to the First Officer's side. So the autopilot did exactly what I asked it to do. It flew the NAV course that I had set in my side not what the First Officer had set in his side. I did not ensure that my side was set up exactly like the First Officer's. In fact my side was still set to the ILS frequency that we used 5 hours ago when we landed coming into TEB. Had I ensured that the flight director mode controller was set to the First Officer's side there wouldn't have been a deviation. Be much more vigilant and ensure the automation is set up correctly. Not be so rushed even when passengers are asking to leave. Follow the checklist slowly. Be quicker to remove automation when it is distracting. Don't disengage the autopilot. That would have saved us if we would have flown it in bug mode with autopilot engaged.

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.