A communications breakdown on the teb ruudy 4 SID caused an altitude overshoot because takeoff brief...

Attributes
ACN	1043473
Time
Date	201210
Local Time Of Day	1801-2400
Place
Locale Reference	TEB.Airport
State Reference	NJ
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Citationjet (C525/C526) - CJ I / II / III / IV
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	SID RUUDY 4
Flight Plan	IFR
Person 1
Function	Pilot Not Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types

Narrative:

We departed runway 24 at teb on the ruudy 4 departure. The first officer briefed all the altitudes and course headings and planned to fly the departure with the autopilot engaged. On departure the first officer called for the gear and flaps to come up. Then he said autopilot. I assumed he meant he had engaged the autopilot but he meant for me to engage the autopilot for him. We noticed that we needed to level off at 1;300. The first officer was waiting for the autopilot which was not engaged at the time; we recognized the problem and the first officer began the level off and we leveled off at approximately 1;580 and then returned to 1;500. We were slightly off course and corrected back on course. The controller contacted us several times as we were sorting out the issue. We then changed over to new york departure and at that time we were on course and altitude. We needed to be clear on who was going to engage the autopilot during the departure.

Original NASA ASRS Text

Title: A communications breakdown on the TEB RUUDY 4 SID caused an altitude overshoot because takeoff brief did not clearly state that when the First Officer requested 'autopilot ON' the Captain was to complete the action.

Narrative: We departed Runway 24 at TEB on the RUUDY 4 Departure. The First Officer briefed all the altitudes and course headings and planned to fly the departure with the autopilot engaged. On departure the First Officer called for the gear and flaps to come up. Then he said autopilot. I assumed he meant he had engaged the autopilot but he meant for me to engage the autopilot for him. We noticed that we needed to level off at 1;300. The First Officer was waiting for the autopilot which was not engaged at the time; we recognized the problem and the First Officer began the level off and we leveled off at approximately 1;580 and then returned to 1;500. We were slightly off course and corrected back on course. The Controller contacted us several times as we were sorting out the issue. We then changed over to New York Departure and at that time we were on course and altitude. We needed to be clear on who was going to engage the autopilot during 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.

A communications breakdown on the teb ruudy 4 SID caused an altitude overshoot because takeoff brief did not clearly state that when the first officer requested 'autopilot on' the captain was to complete the action.