Narrative:

IFR flight bdr to mtn, visual conditions. On V16 south of dixie, did not have coyle VOR on flight plan. Started direct to vcn VOR and was west of airway. Notified by ZNY that I was off airway and to go 180 degrees to join airway. I turned to 180 degrees and was single pilot on chart looking for coyle VOR frequency and xradial when ZNY controller notified me I still was not on course. I requested a moment to revise my navigation, but was told I could not continue and to go direct vcn VOR where I rejoined V16. I do not believe loss of separation ever occurred, but I was somewhat west of the airway. Not having the coyle VOR waypoint in my GPS flight plan was my error and quite odd as I fly V16 often and had just flew that route north a few days before. I just missed '+6' entry in my route planning.

Related reports:

Google
 

Original NASA ASRS Text

Title: PA32 CFI PLT EXPERIENCES A DEV FROM V16 AIRWAY WHEN HIS GPS SYS HAS A MISSED WAYPOINT ON HIS TRIP PAST VCN TO MTN, MD.

Narrative: IFR FLT BDR TO MTN, VISUAL CONDITIONS. ON V16 S OF DIXIE, DID NOT HAVE COYLE VOR ON FLT PLAN. STARTED DIRECT TO VCN VOR AND WAS W OF AIRWAY. NOTIFIED BY ZNY THAT I WAS OFF AIRWAY AND TO GO 180 DEGS TO JOIN AIRWAY. I TURNED TO 180 DEGS AND WAS SINGLE PLT ON CHART LOOKING FOR COYLE VOR FREQ AND XRADIAL WHEN ZNY CTLR NOTIFIED ME I STILL WAS NOT ON COURSE. I REQUESTED A MOMENT TO REVISE MY NAV, BUT WAS TOLD I COULD NOT CONTINUE AND TO GO DIRECT VCN VOR WHERE I REJOINED V16. I DO NOT BELIEVE LOSS OF SEPARATION EVER OCCURRED, BUT I WAS SOMEWHAT W OF THE AIRWAY. NOT HAVING THE COYLE VOR WAYPOINT IN MY GPS FLT PLAN WAS MY ERROR AND QUITE ODD AS I FLY V16 OFTEN AND HAD JUST FLEW THAT RTE N A FEW DAYS BEFORE. I JUST MISSED '+6' ENTRY IN MY RTE PLANNING.

Data retrieved from NASA's ASRS site as of July 2007 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.