Ce-560XL flight crew reported altitude excursion while flying the RUUDY5 SID from teb. Both reporter...

Narrative:

I was pilot not flying (PNF) on the leg from teb-ZZZ. My captain briefed the RUUDY5 departure prior to departing teb; and acknowledged the top altitude for the departure as defined by the SID (2000 ft MSL). The departure was properly loaded into our FMS.upon receiving our takeoff clearance; the tower controller told us we were cleared to takeoff runway 24 and join the RUUDY5 departure.at 400 AGL; I followed the captain's command to pull the gear up; and was working through all associated post-takeoff PNF responsibilities. I checked in with ny departure with my altitude. Ny departure acknowledged my altitude. A short time later; ny departure questioned our altitude; as we were crossing wentz at 2;000 feet (instead of the clearly marked 1;500 crossing restriction). Ny departure calmly told us it put us in the arrivals corridor for ewr. While trying to talk to my captain to see what the heck he was doing related to the crossing restriction; ny departure asked why we were flying the wrong course. I realized at this point that the captain had turned on the autopilot by himself; instead of calling for the PNF to do it (me); and had incorrectly selected heading mode instead of navigation mode; and not said aloud (as required by company policy) that he had engaged the autopilot. I told the captain he'd engaged heading and not navigation mode; and he selected navigation mode; turning us toward zimmz intersection (our correct course at that point). The captain requested the SID's top altitude of 2000 be set in the altitude pre-select; instead of putting 1500 in for the intermediate level off to comply with the crossing restriction at wentz.the controller was polite and direct in asking why our altitudes and course were incorrect. The captain (recently retired 121) told me he hadn't understood the chart (government charts); as he was used to jepp charts; and that he hadn't seen the intermediate crossing restriction at wentz (even though he briefed it correctly on the ground).

Original NASA ASRS Text

Title: CE-560XL flight crew reported altitude excursion while flying the RUUDY5 SID from TEB. Both reporters mention the Captain's misunderstanding of NACO charts as a contributing factor.

Narrative: I was Pilot Not Flying (PNF) on the leg from TEB-ZZZ. My captain briefed the RUUDY5 departure prior to departing TEB; and acknowledged the top altitude for the departure as defined by the SID (2000 FT MSL). The departure was properly loaded into our FMS.Upon receiving our takeoff clearance; the tower controller told us we were cleared to takeoff runway 24 and join the RUUDY5 departure.At 400 AGL; I followed the captain's command to pull the gear up; and was working through all associated post-takeoff PNF responsibilities. I checked in with NY departure with my altitude. NY departure acknowledged my altitude. A short time later; NY Departure questioned our altitude; as we were crossing Wentz at 2;000 feet (instead of the clearly marked 1;500 crossing restriction). NY departure calmly told us it put us in the arrivals corridor for EWR. While trying to talk to my Captain to see what the heck he was doing related to the crossing restriction; NY departure asked why we were flying the wrong course. I realized at this point that the Captain had turned on the autopilot by himself; instead of calling for the PNF to do it (me); and had incorrectly selected heading mode instead of NAV mode; and not said aloud (as required by company policy) that he had engaged the autopilot. I told the Captain he'd engaged heading and not NAV mode; and he selected NAV mode; turning us toward ZIMMZ intersection (our correct course at that point). The captain requested the SID's top altitude of 2000 be set in the altitude pre-select; instead of putting 1500 in for the intermediate level off to comply with the crossing restriction at WENTZ.The controller was polite and direct in asking why our altitudes and course were incorrect. The captain (recently retired 121) told me he hadn't understood the chart (government charts); as he was used to JEPP charts; and that he hadn't seen the intermediate crossing restriction at WENTZ (even though he briefed it correctly on the ground).

Data retrieved from NASA's ASRS site 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	1443800
Time
Date	201704
Local Time Of Day	0601-1200
Place
Locale Reference	TEB.Airport
State Reference	NJ
Environment
Light	Daylight
Aircraft 1
Make Model Name	Citation Excel (C560XL)
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	SID RUUDY5
Flight Plan	IFR
Person 1
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 115 Flight Crew Total 1230 Flight Crew Type 620
Person 2
Function	Captain Pilot Flying
Qualification	Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Flight Engineer Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 135 Flight Crew Total 29600 Flight Crew Type 220
Events
Anomaly	Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Undershoot Deviation - Procedural Clearance

Ce-560XL flight crew reported altitude excursion while flying the RUUDY5 SID from teb. Both reporters mention the captain's misunderstanding of naco charts as a contributing factor.