A single pilot departed on the teb ruudy 4 but failed to program the garmin 530 to include the depar...

Narrative:

After picking up my flight plan from clearance I entered it into my garmin 530 but it would not take the ruudy 4 SID in a pre-stored flight plan. I would have to plug that in after I activated that stored flight plan. I activated my pre-stored flight plan and had a normal takeoff from teb. After takeoff I activated the autopilot and climbed to 1;500 ft on a 240 degree heading as instructed by the ruudy 4 SID. I switched from teb tower to the departure controller. A couple of minutes later I noticed I was headed toward ewr and knowing that was not correct I disabled the autopilot. I was hand flying in some light turbulence while trying to establish what went wrong. I figured out I had not entered the SID in the flight plan before takeoff and was looking at the SID on my ipad to determine what correction I needed to make. The airspace is tight in that area and the departure controller told me to turn immediately right to 320. He said 'there was a possible loss of separation' with some traffic that was landing in teb on a different runway. I never saw the other aircraft and he did not say how far away I was. The time between when I realized I was in the wrong place to the controller vectoring me to 320 was a couple of minutes. As I said the airspace is very tight in that area. The problem arose from my confidence in the pre-stored flight plan that I had not amended after activation. A contributing factor may have been the workload. I normally have a second pilot who could not fly this leg and my workload increased as a result. I didn't seem overload until I realized I was not on the ruudy 4 SID. Then things got very busy while I hand flew in light turbulence while trying to examine the SID and deal with the controllers. It was discovered when I saw I was headed for newark and that didn't seem right. As a corrective action I will make certain my SID is entered into the active flight plan after activating a pre-stored flight plan. I wish I could say this was an equipment malfunction but I failed to enter the SID after activating the pre-stored flight plan. Maybe unconsciously I thought I had the flight plan covered because I had pre-stored it before loading passengers. I had 8 hours of sleep the night before was not fatigued and didn't feel overloaded until I realized I was in the wrong place.

Original NASA ASRS Text

Title: A single pilot departed on the TEB RUUDY 4 but failed to program the Garmin 530 to include the Departure and had a track deviation which ATC corrected with a vector away from conflicting traffic.

Narrative: After picking up my flight plan from clearance I entered it into my Garmin 530 but it would not take the RUUDY 4 SID in a pre-stored flight plan. I would have to plug that in after I activated that stored flight plan. I activated my pre-stored flight plan and had a normal takeoff from TEB. After takeoff I activated the autopilot and climbed to 1;500 FT on a 240 degree heading as instructed by the RUUDY 4 SID. I switched from TEB Tower to the Departure Controller. A couple of minutes later I noticed I was headed toward EWR and knowing that was not correct I disabled the autopilot. I was hand flying in some light turbulence while trying to establish what went wrong. I figured out I had not entered the SID in the flight plan before takeoff and was looking at the SID on my iPad to determine what correction I needed to make. The airspace is tight in that area and the Departure Controller told me to turn immediately right to 320. He said 'there was a possible loss of separation' with some traffic that was landing in TEB on a different runway. I never saw the other aircraft and he did not say how far away I was. The time between when I realized I was in the wrong place to the Controller vectoring me to 320 was a couple of minutes. As I said the airspace is very tight in that area. The problem arose from my confidence in the pre-stored flight plan that I had not amended after activation. A contributing factor may have been the workload. I normally have a second pilot who could not fly this leg and my workload increased as a result. I didn't seem overload until I realized I was not on the RUUDY 4 SID. Then things got very busy while I hand flew in light turbulence while trying to examine the SID and deal with the controllers. It was discovered when I saw I was headed for Newark and that didn't seem right. As a corrective action I will make certain my SID is entered into the active flight plan after activating a pre-stored flight plan. I wish I could say this was an equipment malfunction but I failed to enter the SID after activating the pre-stored flight plan. Maybe unconsciously I thought I had the flight plan covered because I had pre-stored it before loading passengers. I had 8 hours of sleep the night before was not fatigued and didn't feel overloaded until I realized I was in the wrong place.

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.

Attributes
ACN	1044418
Time
Date	201210
Local Time Of Day	1201-1800
Place
Locale Reference	TEB.Airport
State Reference	NJ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	PA-42 Cheyenne IV/400/400LS
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	SID RUUDY4
Flight Plan	IFR
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Instrument Flight Crew Private Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 60 Flight Crew Total 12250 Flight Crew Type 2500
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

A single pilot departed on the teb ruudy 4 but failed to program the garmin 530 to include the departure and had a track deviation which ATC corrected with a vector away from conflicting traffic.