Narrative:

I was flying the ruudy 2 departure from teb and climbed above the 1500 foot restriction on climb out just prior to wentz waypoint. I was climbing toward 2000 ft when the departure controller told me I was higher than 1500 feet; so I immediately descended from about 1800-1900 ft down to 1500 ft. No traffic alerts on my traffic advisory system on board; no traffic sighted; and no traffic called out by the departure controller. I had flown this departure previously and been given early deviations to assigned altitudes from these controllers and was half expecting them to give me a more direct low altitude departure with waypoints off the departure procedure and more onto my routing. It was VMC and I believe no traffic conflict existed at that time; however I now know that the airspace immediately above the ruudy 2 departure is used by aircraft approaching ewr. I have made 3x5 cards with the waypoints and call-outs and altitudes for the ruudy 2 departure for my use in the future. I have been on that departure before and been given earlier altitudes and vectors more direct to my flight plan; etc. The aircraft I was flying does not have altitude preselect on the flight director/autopilot and so since I wasn't in the king air or citation I usually fly. I erred by not controlling the altitude function manually. It won't happen again. I often bring along a second 'safety pilot' when flying in and out of busy east coast airspace like dca or nyc but on this trip it was a friday early afternoon in good weather and I knew it would be light traffic in and out of teb.

Google
 

Original NASA ASRS Text

Title: A BE55 Pilot reported not leveling at 1500 FT on the TEB RUUDY 2 departure. Other aircraft he flies have an altitude alerter but this aircraft did not.

Narrative: I was flying the RUUDY 2 departure from TEB and climbed above the 1500 foot restriction on climb out just prior to WENTZ waypoint. I was climbing toward 2000 FT when the Departure Controller told me I was higher than 1500 feet; so I immediately descended from about 1800-1900 FT down to 1500 FT. No traffic alerts on my traffic advisory system on board; no traffic sighted; and no traffic called out by the Departure Controller. I had flown this Departure previously and been given early deviations to assigned altitudes from these Controllers and was half expecting them to give me a more direct low altitude departure with waypoints off the Departure procedure and more onto my routing. It was VMC and I believe no traffic conflict existed at that time; however I now know that the airspace immediately above the RUUDY 2 departure is used by aircraft approaching EWR. I have made 3x5 cards with the waypoints and call-outs and altitudes for the RUUDY 2 Departure for my use in the future. I have been on that departure before and been given earlier altitudes and vectors more direct to my flight plan; etc. The aircraft I was flying does not have altitude preselect on the flight director/autopilot and so since I wasn't in the King Air or Citation I usually fly. I erred by not controlling the altitude function manually. It won't happen again. I often bring along a second 'Safety Pilot' when flying in and out of busy east coast airspace like DCA or NYC but on this trip it was a Friday early afternoon in good weather and I knew it would be light traffic in and out of 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.