A PA24 pilot reported filing a GPS flight plan which did not get activated because the aircraft equi...

Narrative:

I filed IFR to my destination via FSS 800--WX-brief. This will come into play later. I took off at XA32 after receiving clearance from clearance delivery as filed; 2000 ft initially and then 11;000 after 10 minutes. Tower gave me takeoff instructions of right turn to 270 and then I was switched to departure passing 900 ft. Checked in with departure who gave me vectors and climbed me to 3000 ft and then 5000 ft. I was heading 360 and then received vectors for 050 until intercepting the orl 355 outbound. Nowhere had my clearance talked about that. I dialed up orl; [identified] and then dialed the outbound course of 355. I turned to track outbound about one minute later. I was looking at my track and I saw it didn't look like it was marrying up. I tuned up my second VOR and was asked by ATC what my heading was. I informed him what my heading was and then he had me fly 050 because I was ten miles west of where they wanted me. I informed him that my VOR appeared to have issues. I noticed -13 degree worth of split. I requested a heading of 040 to avoid a building circuit breaker. He told me to continue and that he was busy and once he figured out what he wanted to do with me he would hand me off. I requested a climb as soon as possible to get on my fuel plan. I was handed off to daytona approach and was now going to get a GPS fix again. I cancelled IFR and proceeded VFR with flight following so I could climb to 11.5K and get heading to my filed destination. Lesson learned - I used the new system offered by FSS which marries my number to an aircraft/equipment code. I had filed not using this system last week and they gave me the GPS plan no problem. When I was filing this morning; the FSS asked me about VOR enroute. I told him I was using GPS; but we never clarified what my equipment code was. The aircraft had been IFR certified two months earlier; and I have about 500 hours IFR. Anyhow; the new FSS system is great; but bad on me not making sure it was what I wanted for equipment code. I should have verified and that would have removed some confusion.

Original NASA ASRS Text

Title: A PA24 Pilot reported filing a GPS flight plan which did not get activated because the aircraft equipment code was not verified with FSS. After departure while on TRACON vectors the reporter noticed a deviation from his filed flight plan; the result of a VOR error and routing confusion.

Narrative: I filed IFR to my destination via FSS 800--WX-brief. This will come into play later. I took off at XA32 after receiving clearance from clearance delivery as filed; 2000 FT initially and then 11;000 after 10 minutes. Tower gave me takeoff instructions of right turn to 270 and then I was switched to departure passing 900 FT. Checked in with Departure who gave me vectors and climbed me to 3000 FT and then 5000 FT. I was heading 360 and then received vectors for 050 until intercepting the ORL 355 outbound. Nowhere had my clearance talked about that. I dialed up ORL; [identified] and then dialed the outbound course of 355. I turned to track outbound about one minute later. I was looking at my track and I saw it didn't look like it was marrying up. I tuned up my second VOR and was asked by ATC what my heading was. I informed him what my heading was and then he had me fly 050 because I was ten miles west of where they wanted me. I informed him that my VOR appeared to have issues. I noticed -13 degree worth of split. I requested a heading of 040 to avoid a building CB. He told me to continue and that he was busy and once he figured out what he wanted to do with me he would hand me off. I requested a climb ASAP to get on my fuel plan. I was handed off to Daytona Approach and was now going to get a GPS fix again. I cancelled IFR and proceeded VFR with flight following so I could climb to 11.5K and get heading to my filed destination. Lesson learned - I used the new system offered by FSS which marries my number to an aircraft/equipment code. I had filed not using this system last week and they gave me the GPS plan no problem. When I was filing this morning; the FSS asked me about VOR enroute. I told him I was using GPS; but we never clarified what my equipment code was. The aircraft had been IFR certified two months earlier; and I have about 500 hours IFR. Anyhow; the new FSS system is great; but bad on me not making sure it was what I wanted for equipment code. I should have verified and that would have removed some confusion.

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	891459
Time
Date	201005
Local Time Of Day	0601-1200
Place
Locale Reference	MCO.TRACON
State Reference	FL
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	PA-24 Turbo Comanche
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	Direct
Flight Plan	IFR
Component
Aircraft Component	ILS/VOR
Person 1
Function	Single Pilot
Qualification	Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Commercial Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 35 Flight Crew Total 2400 Flight Crew Type 40
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Track / Heading All Types

A PA24 pilot reported filing a GPS flight plan which did not get activated because the aircraft equipment code was not verified with FSS. After departure while on TRACON vectors the reporter noticed a deviation from his filed flight plan; the result of a VOR error and routing confusion.