Date: 201212
Local time of day: 1201-1800
Location: TEB.Airport, NJ
Flight conditions: IMC
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operating under: Part 91
Flight phase: Climb
Airspace: Class D TEB
ATC / advisory: TRACON N90
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Human-Machine Interface
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Airspace Structure; Procedure; Human Factors
Primary problem: Human Factors

Narrative: We departed TEB in the evening but a ground stoppage was in affect and total time on the ground with engines running was approximately 30 minutes. As we were parked in the run up hold area we briefed the departure and had the FMS sequenced; HDG mode selected and NAV in standby. We also had 1500 feet selected in the altitude preselect. Once cleared for takeoff; the gear was retracted at 400 feet and power was reduced. Around 800 to 1000 feet I reached over and engaged the autopilot; or so I thought. A few seconds later I realized the autopilot was not engaged as we were in a slight left bank and a slow descent. I placed the aircraft back into the flight director command bars and reduced the power in an effort give myself more time to correct the situation. I recall I slowed the aircraft to around 160 knots. I was able to re-engage the autopilot and the heading seemed to correct back to 240 to intercept the 260. At about this time I noticed that the altitude was about to pass 1500 feet with the restriction being 1500 until WENTZ. We were prior to WENTZ as I saw this occurring; I engaged the autopilot interrupt; nosed the aircraft back to 1500; the highest altitude I observed was 1750 plus or minus 50 feet prior to WENTZ. After WENTZ we were given an altitude assignment above 2000 and thus prior to the TASCA altitude restriction of 2000.Once we leveled off at our cruise altitude myself and the co-pilot did a self analysis to determine how not to repeat this event. We determined it to be an excellent practice of having the right seat pilot engage the autopilot when the left seat pilot calls for such. This will accomplish two things. One; it will allow the pilot flying to concentrate on the PFD so as not to take eyes away to look for the AP button. Two; it forces the both persons to confirm the auto pilot is actually engaged.


Second narrative: I was right sight pilot not flying. Departing Runway 24 on the RNAV Rudy 4 departure; HDG and NAV modes were both engaged before takeoff. After takeoff; I performed the appropriate checklist and noticed the aircraft was in a slight left bank. I then noticed the autopilot was not engaged and the Captain was already correcting heading and altitude before re-engaging autopilot. When checking in with New York Departure; I noticed altitude was at 1;750 MSL and reversing to 1;500 MSL all before reaching WENTZ Intersection. Controller made a short comment before handing us off the next Controller.Asking pilot not flying to engage autopilot after take-off would prevent pilot flying from having to disengage scan. Also delaying non critical parts of after-takeoff checklist in order to monitor RNAV departure would help keep procedure adherence.


Synopsis: Flight crew reports exceeding 1;500 FT prior to WENTZ on the RUUDY 4 departure from TEB.