Be-36 pilot reports a track deviation due to errors entering his cleared route into his GPS and lack...

Narrative:

I filed a flight plan using fltplan.com. I received and correctly read back my clearance from delivery. However I input the clearance to my GPS navigator by referencing the forecast winds aloft section of fltplan.com; not the actual route. This caused me to omit fixes poxku and pdz and I navigated towards terrain. ATC called; and asked if I was given a vector to join V8 which I had not. I was then given a vector which I dialed into my heading however I had disengaged my autopilot; and I did not notice I was not turning to the heading. I was given a second vector when I noticed autopilot was not engaged. The controller then asked how I was navigating to pdz; which I did not respond to as I was not navigating towards pdz. This problem was compounded by my recent installation of a 'glass panel' aspen navigation system. I am not familiar with the system yet and did not confirm where my first vector was towards. Additionally; I should have requested vectors; or direct to a fix when I realized I did not know where I was going. I have been trying to fly in the IFR system in VMC as much as possible to gain experience with the new navigation systems. I probably need to continue that with an instructor.

Original NASA ASRS Text

Title: BE-36 pilot reports a track deviation due to errors entering his cleared route into his GPS and lack of familiarity with a new glass panel flight display.

Narrative: I filed a flight plan using fltplan.com. I received and correctly read back my clearance from delivery. However I input the clearance to my GPS navigator by referencing the forecast winds aloft section of fltplan.com; not the actual route. This caused me to omit fixes POXKU and PDZ and I navigated towards terrain. ATC called; and asked if I was given a vector to join V8 which I had not. I was then given a vector which I dialed into my heading however I had disengaged my autopilot; and I did not notice I was not turning to the heading. I was given a second vector when I noticed autopilot was not engaged. The Controller then asked how I was navigating to PDZ; which I did not respond to as I was not navigating towards PDZ. This problem was compounded by my recent installation of a 'Glass Panel' Aspen Navigation system. I am not familiar with the system yet and did not confirm where my first vector was towards. Additionally; I should have requested vectors; or direct to a fix when I realized I did not know where I was going. I have been trying to fly in the IFR system in VMC as much as possible to gain experience with the new navigation systems. I probably need to continue that with an instructor.

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	1113119
Time
Date	201309
Local Time Of Day	0601-1200
Place
Locale Reference	SCT.TRACON
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Bonanza 36
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	Other SANN19
Flight Plan	IFR
Component
Aircraft Component	GPS & Other Satellite Navigation
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Instrument Flight Crew Private
Experience	Flight Crew Last 90 Days 60 Flight Crew Total 1100 Flight Crew Type 400
Events
Anomaly	Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT

Be-36 pilot reports a track deviation due to errors entering his cleared route into his GPS and lack of familiarity with a new glass panel flight display.