FSBuild with FSNAVIGATOR

[Paintwagon 0]

Does anyone use FSBUILD with FSNAVIGATOR? When a flight plan is created in Fsbuild with sid/stars, my FSNAVIGATOR shows "FIX01, FIX02,etc for every waypoint intersection within each sid or star, with the correct intersection name very close to the FIX01, Fix02..etc

 

Dennis

[ronzie 21]

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. These are not registered in the global fix database. Perhaps in FS Navigator they are called FIX 1, etc., or they are seen as custom fixes because they are not in FS NAV's database.

 

For example, this plan entered in FSB:

EDDT RAKI1T CDA CDA3A EKCH

 

translates to:

 

[flightplan]

title=EDDT to EKCH

description=EDDT, EKCH

type=IFR

routetype=3

cruising_altitude=26000

departure_id=EDDT, N52* 33.37', E013* 17.31',+000121.00

departure_position=26L

destination_id=EKCH, N55* 36.40', E012* 38.28',+000017.00

departure_name=BERLIN_TEGEL

destination_name=COPENHAGEN_KASTRUP

waypoint.0=EDDT, A, N52* 33.37', E013* 17.31', +000000.00,

waypoint.1=DT261, I, N52* 32.18', E013* 04.20', +02000.00,

waypoint.2=DT263, I, N52* 31.51', E012* 59.48', +02000.00,

waypoint.3=DT265, I, N52* 41.38', E012* 48.44', +05000.00,

waypoint.4=DT266, I, N52* 20.33', E012* 58.28', +11000.00,

waypoint.5=RAKIT, I, N53* 10.42', E013* 54.39', +26000.00,

waypoint.6=CDA, V, N55* 00.05', E012* 22.45', +13000.00,

waypoint.7=NEKSO, I, N55* 13.55', E012* 38.57', +07000.00,

waypoint.8=EKCH, A, N55* 36.40', E012* 38.28', +000000.00,

 

 

 

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. In this example the digital files uses the DTnnn symbols. These are not world unique waypoint names but are local to this airport as RNAV locations.

 

Perhaps they are recognized in FSNAV as custom unlabeled waypoints defined by the coordinates as FIXnn. Haveyou updated FSNV with an AIRAC file as FSBuild now uses?

 

Anyway, in general, waypoints for limits and path definitions are defined by the authority submitting the digital data for AIRACs or the digital coding authority.

 

In FSBuild, also, waypoints entered by coordinates show up with a partial coordinate label in the FS9 plan. These are often encountered in pond crossings filed with NATS. These might be treated with labels as FIXnnn in FSNAV as well.

 

On a Smiths type FMC LEGS readout (B737NG series) they would read as FIX01, etc., if entered as coordinates only. Of course each nn would be unique to that FMC plan.

 

Does this help at all?

 

You can synchronize the AIRAC databases for FS NAV and FSBuild by a subscription to navigraph or aerosoft AIRAC FMC updates. Aerosoft is new and has more flexible cost options including a less expensive one AIRAC period subscription. (For both you can download multiple formats at no extra cost for each period.)

[Paintwagon 0]

Thanks for your response Ronzie.. Please see the attached pics....I also compared the Intersection data for "CHCLL" from FSBuild with FSNAV and found the following:

CHCLL 38.480467 -84.978495 15 -- FSNAV's isec.txt file

CHCLL CHCLL 38.480467 -84.978495 USA -- FSBuild's ints.txt file

They look like the same coordinates to me..

Notice the LAT/LONG difference between FSbuild and FSNAV. However FSNAV and FS Commander show the same L/L...or very close..

 

It looks like the FSNAV pic got cut off a little, but you can see the coordinates at the top in blue. Also, all 3 programs (FSBUILD,FSNAV,FSCOMMANDER) are using Airac cycle 1206. See attahed pics for FSBUILD/FSNAV...

[ronzie 21]

In FIX01 that's minutes and decimal minutes as in that display. For lattitude seconds multiply .83 x 60 = 49.8 seconds. FSB on the route grid displays seconds. In the FS .pln that is seconds following the decimal as:

departure_id KCVG , N39* 02.55'

and the coordinate from wikipedia;

39°02′56″N

FSC cordinate at the screen bottom reads N38o28.76 which equals N38o28' 46'' very close.

 

I think the confusion is where decimal minutes is used vs. seconds displayed following the "." as in the FS9 flight plan.

 

So Fix01 is CHCLL but CHCLL is not in that database so Fix01 is substituted maybe. On the bottom of the display showing Fix01 that status line shows both formats with decimal minutes on the left of the = sign and seconds on the right. Is that display showing Fix01 FS Nav or something else.

[Paintwagon 0]

After the FSBUILD image is the FSNAV image..Click on this image (to enlarge) to view FIX01. The next image is of FSCommander. Click on it to view Fix01..The status line at the bottom happens to be where the cursor was when the pic was taken...

[ronzie 21]

After converting decimal minutes to seconds it looks like they all match. I just checked lattitudes. Now a tip: In FSBuild you can enter a waypoint by coordinates. For instance here is from flightaware.com a completed British Airways #BA238 B777-200 from KBOS to EGLL route over NATS using decoded coordinates for filing:

 

LBSTA ALLEX N79B YQX KOBEV 5000N 05000W 5100N 04000W 5200N 03000W 5200N 02000W DINIM ELSOX EVRIN UL607 NUMPO UP2 OKESI Y3 BEDEK OCK2F

 

In FSB you just need to remove the space between lattitude and longitude as:

 

LBSTA ALLEX N79B YQX KOBEV 5000N05000W 5100N04000W 5200N03000W 5200N02000W DINIM ELSOX EVRIN UL607 NUMPO UP2 OKESI Y3 BEDEK OCK2F

 

Here is the FS9 plan:

 

[flightplan]

title=KBOS to EGLL

description=KBOS, EGLL

type=IFR

routetype=3

cruising_altitude=37000

departure_id=KBOS, N42* 21.46', W071* 00.23',+000020.00

departure_position=22R

destination_id=EGLL, N51* 28.38', W000* 27.41',+000083.00

departure_name=GEN_EDWARD_LAWRENCE_LOGAN_INTL

destination_name=LONDON_HEATHROW

waypoint.0=KBOS, A, N42* 21.46', W071* 00.23', +000000.00,

waypoint.1=LBSTA, I, N42* 47.59', W070* 36.48', +000000.00,

waypoint.2=ALLEX, I, N44* 25.00', W067* 00.00', +000000.00, N79B

waypoint.3=YQX, V, N48* 53.58', W054* 32.05', +000000.00,

waypoint.4=KOBEV, I, N49* 40.12', W051* 28.00', +000000.00,

waypoint.5=5000N05000W, I, N50* 00.00', W050* 00.00', +000000.00,

waypoint.6=5100N04000W, I, N51* 00.00', W040* 00.00', +000000.00,

waypoint.7=5200N03000W, I, N52* 00.00', W030* 00.00', +000000.00,

waypoint.8=5200N02000W, I, N52* 00.00', W020* 00.00', +000000.00,

waypoint.9=DINIM, I, N51* 00.00', W015* 00.00', +000000.00,

waypoint.10=ELSOX, I, N51* 00.00', W014* 00.00', +000000.00,

waypoint.11=EVRIN, I, N51* 46.55', W006* 33.47', +000000.00, UL607

waypoint.12=NEKAP, I, N51* 43.35', W005* 17.26', +000000.00, UL607

waypoint.13=ABDUK, I, N51* 38.34', W003* 48.01', +000000.00, UL607

waypoint.14=NUMPO, I, N51* 36.35', W003* 17.00', +000000.00, UP2

waypoint.15=OKESI, I, N51* 26.35', W002* 03.42', +000000.00, Y3

waypoint.16=BEDEK, I, N51* 22.14', W001* 33.30', +000000.00,

waypoint.17=NIGIT, I, N51* 18.47', W001* 10.14', +000000.00,

waypoint.18=OCK12, I, N51* 18.32', W000* 45.57', +000000.00,

waypoint.19=OCK, V, N51* 18.17', W000* 26.49', +000000.00,

waypoint.20=EGLL, A, N51* 28.38', W000* 27.41', +000000.00,

 

A nice 6 hour pond crossing for you to keep you awake

 

Sometimes the version of a SID/STAR may be different from the one in FSB due to name length or version. Just drop down the SID/STAR choice from the list box in the upper airport sections to get the closest match for expansion. This one workes as is. If you drop the list down and then don't choose you lose the procedure from the route line so watch for that.

 

See how FSNav handles this one for coordinate syntax.

[Paintwagon 0]

Thanks, Ronzie..

This problem only occurs when I use SID/STARS in FSBUILD. When I want to use FSNAV, I will exclude the use of SID/STARS.. I use FS Commander in a WIDEFS environment with an adjacent computer. It works fine.. Every once is a while I like to use FSNAV.. It is "such" a good program....