Ron Lee wrote:
"Stan Prevost" wrote:

That seems to be an overly broad statement. I have put "VFR GPS" in Remarks
when filing /U for an off-airways (random) route and had controllers
specifically refer to using my VFR GPS to proceed direct to an intersection.
Whether they should have done so is another issue. But is sure seemed to
make a difference.


Your non-IFR GPS has intersections in it? What model is it?

Ron Lee

Every Garmin handheld I have owned, 195, 295, and 296, have a complete
Americas Jeppesen LNAV database; all intersections, waypoints, airports,
runway layout for IFR airports, all communications and nav frequencies,
distance to FAA transmitter, and so forth.

The approach is abbreviated but all the fixes are in the database to
build the complete approach as a flight plan.

The terrain database of the 296 is essentially the same as any
full-press EGPWS I have used. It just doesn't have the aural warnings.