An N90 controller reported a CL30 departed teb on the ruudy 3 RNAV departure and failed to level at ...

Narrative:

While working the departure radar and departure satellite positions combined; a CL30 departed teb airport on runway 24 ruudy 2 and checked in climbing through 2500 ft. The published altitude restriction for both departure procedures off of runway 24 is 1500 ft due to ewr arrivals flying overhead and near teb as low as 2500 ft. I noticed the CL30 climbing through 2200; 2300; 2400 ft as the pilot checked in on frequency with a newark arrival directly behind him at 3000 ft. The CL30 was in front of and passed all conflicting traffic so I climbed the aircraft to 8000 ft and continued radar service on the aircraft. I informed the aircraft of the altitude restriction and the reason for the restriction. The pilot seemed to acknowledge/understand his mistake and continued without further incident. The teterboro runway 24 and ruudy departure procedures seem to confuse many pilots given the unusually high number of pilot deviations that occur on initial contact and immediately upon departure from teb. These procedures need to be reviewed; simplified and clarified; with input from the users; given this critical phase of flight and complexity of the airspace in and around teb.

Original NASA ASRS Text

Title: An N90 Controller reported a CL30 departed TEB on the RUUDY 3 RNAV Departure and failed to level at 1;500 FT. The Reporter suggests user involvement in a departure revision to decrease the numerous TEB departure deviations.

Narrative: While working the Departure Radar and Departure Satellite positions combined; A CL30 departed TEB airport on Runway 24 RUUDY 2 and checked in climbing through 2500 FT. The published altitude restriction for both departure procedures off of Runway 24 is 1500 FT due to EWR arrivals flying overhead and near TEB as low as 2500 FT. I noticed the CL30 climbing through 2200; 2300; 2400 FT as the pilot checked in on frequency with a Newark arrival directly behind him at 3000 FT. The CL30 was in front of and passed all conflicting traffic so I climbed the aircraft to 8000 FT and continued radar service on the aircraft. I informed the aircraft of the altitude restriction and the reason for the restriction. The pilot seemed to acknowledge/understand his mistake and continued without further incident. The Teterboro Runway 24 and Ruudy departure procedures seem to confuse many pilots given the unusually high number of pilot deviations that occur on initial contact and immediately upon departure from TEB. These procedures need to be reviewed; simplified and clarified; with input from the users; given this critical phase of flight and complexity of the airspace in and around TEB.

Data retrieved from NASA's ASRS site as of April 2012 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	896499
Time
Date	201007
Local Time Of Day	1201-1800
Place
Locale Reference	TEB.Airport
State Reference	NJ
Environment
Light	Daylight
Aircraft 1
Make Model Name	Challenger 300
Flight Phase	Initial Climb
Route In Use	SID RUUDY 1
Flight Plan	IFR
Person 1
Function	Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Clearance

An N90 controller reported a CL30 departed teb on the ruudy 3 RNAV departure and failed to level at 1;500 ft. The reporter suggests user involvement in a departure revision to decrease the numerous teb departure deviations.