Despite not understanding by which departure procedure he was cleared; the pilot of an EA500 took of...

Narrative:

When receiving an IFR clearance from poc; I was given a clearance that included; 'runway 26L departure procedure; vectors to join...(rest of route)'.I looked through my electronic charts and procedure database in my garmin 400 and did not see a procedure listed. I; admittedly; did not ask for clarification prior to departure.after handoff from tower and radar contact with departure; I was asked why I was not in a left hand turn in accordance with the departure procedure. I admitted that I was not familiar with the procedure when asked and vectors were given. Although the controller did state that; 'he was not going to violate' me; he continued to question me on the radio and asked 'why' several times.I have two concerns with what occurred this morning. First and foremost; I should have looked at the airport notes and the odp(obstacle departure procedure). Completely; 100% my fault and a very strong lesson learned. My second concern is that; although I appreciate that the controller was trying to help me learn; as a single pilot flying in complex airspace trying to correct a bad situation; I would have preferred to discuss the situation with the controller off-line; after the situation had been corrected. I have definitely learned my lesson after this; and the only take away I would like to provide the national airspace system is; that although tolerance and guidance are hugely appreciated by pilots like me; the added stress of trying to answer 'why' and 'what were you thinking' questions is counter productive to correcting a possibly dangerous situation.again; I greatly appreciate the help and guidance I receive from ATC everyday; but wanted to submit an example of a case where the lesson could have been better absorbed with an after the fact discussion versus 'real-time.'

Original NASA ASRS Text

Title: Despite not understanding by which departure procedure he was cleared; the Pilot of an EA500 took off from POC and was confronted by an ATC Controller who clarified the procedure in a manner the reporter felt was unnecessarily brusque.

Narrative: When receiving an IFR clearance from POC; I was given a clearance that included; 'Runway 26L departure procedure; vectors to join...(rest of route)'.I looked through my electronic charts and procedure database in my Garmin 400 and did not see a procedure listed. I; admittedly; did not ask for clarification prior to departure.After handoff from Tower and radar contact with Departure; I was asked why I was not in a left hand turn in accordance with the departure procedure. I admitted that I was not familiar with the procedure when asked and vectors were given. Although the Controller did state that; 'he was not going to violate' me; he continued to question me on the radio and asked 'why' several times.I have two concerns with what occurred this morning. First and foremost; I should have looked at the airport notes and the ODP(Obstacle Departure Procedure). Completely; 100% my fault and a very strong lesson learned. My second concern is that; although I appreciate that the Controller was trying to help me learn; as a single pilot flying in complex airspace trying to correct a bad situation; I would have preferred to discuss the situation with the Controller off-line; after the situation had been corrected. I have definitely learned my lesson after this; and the only take away I would like to provide the national airspace system is; that although tolerance and guidance are hugely appreciated by pilots like me; the added stress of trying to answer 'why' and 'what were you thinking' questions is counter productive to correcting a possibly dangerous situation.Again; I greatly appreciate the help and guidance I receive from ATC everyday; but wanted to submit an example of a case where the lesson could have been better absorbed with an after the fact discussion versus 'real-time.'

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	911464
Time
Date	201009
Local Time Of Day	0601-1200
Place
Locale Reference	POC.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Eclipse 500
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	Other KPOC ODP RWY26L
Flight Plan	IFR
Component
Aircraft Component	Electronic Flt Bag (EFB)
Person 1
Function	Captain Pilot Flying Single Pilot
Qualification	Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Multiengine
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types

Despite not understanding by which departure procedure he was cleared; the pilot of an EA500 took off from poc and was confronted by an ATC controller who clarified the procedure in a manner the reporter felt was unnecessarily brusque.