For instance here is from a completed British Airways #BA238 B777-200 from KBOS to EGLL route over NATS using decoded coordinates for filing:
Now a tip: In FSBuild you can enter a waypoint by coordinates.
#Fs commander vs fsnavigator download#
(For both you can download multiple formats at no extra cost for each period.)Īfter converting decimal minutes to seconds it looks like they all match. Aerosoft is new and has more flexible cost options including a less expensive one AIRAC period subscription. You can synchronize the AIRAC databases for FS NAV and FSBuild by a subscription to navigraph or aerosoft AIRAC FMC updates. Of course each nn would be unique to that FMC plan. On a Smiths type FMC LEGS readout (B737NG series) they would read as FIX01, etc., if entered as coordinates only. These might be treated with labels as FIXnnn in FSNAV as well. These are often encountered in pond crossings filed with NATS.
In FSBuild, also, waypoints entered by coordinates show up with a partial coordinate label in the FS9 plan. Haveyou updated FSNV with an AIRAC file as FSBuild now uses?Īnyway, in general, waypoints for limits and path definitions are defined by the authority submitting the digital data for AIRACs or the digital coding authority. Perhaps they are recognized in FSNAV as custom unlabeled waypoints defined by the coordinates as FIXnn. These are not world unique waypoint names but are local to this airport as RNAV locations. In this example the digital files uses the DTnnn symbols. In this image I outlined in red soft waypoints that in an AIRAC digital file would have to be defined with a digital name for this airport to complete navigation described as a combination of a DME ARC or distance based on a NAVAID that defines the path. These are not registered in the global fix database. In the AIRAC for FSBuild a SID or STAR particularly runway specific may have "local soft waypoints" that are not unique globally and may be called something like "D12" or similar.
0 kommentar(er)
