Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

RNAV question

  • Thread starter Thread starter newmei
  • Start date Start date
  • Watchers Watchers 3

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web

newmei

Well-known member
Joined
Nov 26, 2001
Posts
181
This probably a stupid question. Provided you are within the service volumn of a VOR, (40 miles in my case) how far outside that area can you make a fix? Does the fix have to be within reception range of the VOR? In otherwords can you be right over the VOR your using for a fix and have a fix 150 miles away, (way outside the reception range) , I would think no, but in the GPS day in age, it would be theory possible. Just not sure if RNAV will do this.
 
since there are no responses and i've got a little (really just a little) rnav experience, i'm going to say you have to be in range of the vor in use. if you think about it, you're setting a radial and distance from the vor. if your nav isn't even receiving a signal, how can it operate?

anyway, just my thoughts. anyone currently using rnav?
 
Your limit on generating a RNAV waypoint will be determined by the parameters of the equipment to be used. For example: a Collins RNAV unit may allow for greater distances to be selected than a Bendix/King unit. In any case, as long as you have a reliable VOR/DME signal available to the RNAV unit, you should be able to generate "phantom" waypoints.

Hope this answers your question...
SK:cool:
 
Newmei,

You weren't specific about the type of RNAV you are talking about.

If you are talking about a GA type RNAV based on VOR/DME (like a KNS-80) then you are left with reception ranges and yes you would have a hard time holding a fix like VOR XYZ at 150 miles. (PS, I think you can only put 2 digit distances, i.e. 99.9 miles in a KNS-80 if I remember correctly.)

If you are right over the XYZ VOR and put a point 150 miles on the 360 degree radial, you would have needle on the CDI as long as the VOR was receiving course and DME info. So the computer would calculate and display needle, but eventually you would get flag and no signal when you get out somewhere in the 45-85 mile range.

Now, if you change your guidance to an FMS unit or INS, now your waypoints have a theoretical unlimited mileage. New FMS units are going to use GPS, VOR/DME and possibly INU's to calculate the waypoint - YOU, the operator, are doing nothing to control the input chosen by the box - you simply put in a waypoint and say "go there". The box will pick the best signals and calculate the method to get there on a straight line. If the box has good GPS signal, then it will use that. If no GPS then it will create a string of VOR/DME stations to keep the path - changing the stations (if it is in auto seek mode) at will to do the job. And then the final box trick is to revert to the Inertial Nav Units and basically Ded Recog a path.

The FMS in VOR/DME mode works like a smart pilot using the old KNS-80 logic.

In the old days (before GPS - oh my gawd!), we would look at our sectionals and low enroutes. If you wanted an RNAV direct route, you would create a string of dots and then measure each dot from the closest VOR/DME station. Using the #1,2,3,and 4 positions - you would just load the waypoints and then fly to each waypoint #1, 2, 3 etc like you were just changing stations. The hardest part of the whole deal was giving ATC a coordinate that you would be flying "direct" to. If the end point was NOT a VOR, then you better be pretty good at giving Lat/Long's to the controller.
 

Latest resources

Back
Top