Hi Robert:> I will continue to utilize a VOR for the end of the first leg when the
> beacon is receivable promptly after takeoff.
A magnetic heading would work too. If you're next waypoint is an intersection, you could insert a waypoint as intercepting one of the radials that makes up the next waypoint/intersection.
> That would actually make
> radio navigation easier, since it would eliminate a frequency change,
> intersection and possibly a radial change midway along the leg.
Radial changes along a leg is difficult unless you're using DME or using another VOR radial to make up the waypoint.
> I don't have the charts to determine the two official VOR bearings for
> intersections.
"Official" intersections aren't necessary (not for RNAV at least). You can define any waypoint between any two VOR radials or a single VOR radial and a DME distance.
> Where an intersection is between two VORs, being the
> second in a series of three waypoints, similar information is available
> in the plan. The distance information in the plan often permits the use
> of DME to determine when the plane is approaching a waypoint. Some
> waypoints immediately before the destination airport can be identified
> by using heading hold near the end of the leg and watching for movement
> on the HSI or OBI set for a localizer. Where there is a VOR at the
> destination airport, but no localizer, I will use the facility type
> "Airport/VOR" and add the VOR frequency to the destination line.
Understood. If no NAVAID is available, again, a simple magnetic heading will get you there.
> If enough people want to download the plan file I could email it to Ben.
Aren't some of the guys getting lazy enough already about flight plans?
Ben
-= VPC OffLine Reader 2.1 =-
Registered to: Ben Chiu
-OLR.PL v1.83-