Fixes provided in routing for IFR flight plans - VFR waypoints okay?

Dave Butler writes:

You can clearly use anything that defines an airway (but not T-airways),
and ground-based navaids like VORs and NDBs, unless specifically tagged
as "VFR Use Only". You specifically may not use VPxxx waypoints.

OK. So I'd probably be better off avoiding VPxxx waypoints to begin
with, even for VFR, if there's any chance that I'd want to use that as
a base for an IFR flight plan. Too bad ... there's lots of VPxxx
waypoints on the VFR charts, whereas the only other ones indicated are
on airways, and there are a lot less of those (at least in high
traffic areas).

Basically you check the "IFR" box on the flight plan form, then in the
altitude box you write "VFR045" for 4500 feet (or something like that).
Someone will correct me.

Hmm ... I didn't know that.

Another advantage of this technique is that when you call up the next
facility for VFR advisories, they already know who you are and where you
are going. When the initial controller "departs" you, it initiates
sending a strip to each of the facilities down the line based on your
filed airspeed, just like for an IFR flight.

Sounds very convenient.

Is there someplace on the Web that discusses everything you can
validly put in an IFR flight plan (or a VFR flight plan, for that
matter)? I can't find any detailed descriptions in the references
I've looked at.

--
Transpose mxsmanic and gmail to reach me by e-mail.

Mxsmanic wrote:

Is there someplace on the Web that discusses everything you can
validly put in an IFR flight plan (or a VFR flight plan, for that
matter)? I can't find any detailed descriptions in the references
I've looked at.

http://www.faa.gov/airports_airtraff.../media/aim.pdf

Dave Butler writes:

http://www.faa.gov/airports_airtraff.../media/aim.pdf

Excellent! Thanks. I had the book, but I didn't know it had detailed
information on routing.

--
Transpose mxsmanic and gmail to reach me by e-mail.