Fsbuild-2 Flight Planner

Hi all,

So when I decide to go the auto generate routing, it is usually.....OK at best. Many Wp and nav aids...no problem. My issue is with the long hauls I often do. KNGP to FMMI. This is a Texus to Africa run. This auto generated route has me criss crossing the Atlantic 4 times for a total mileage of 27,900.

Obviously this is not an accurate FP. All I did was load up FS Build V.2.3.1
My last update was maybe 2 months ago. Can someone else do a few US - Africa AUTO GENERATED routes to see if it is my installation or just that FS Build does not do well with Africa?

Thanks

BTW, here is the auto generated flight plan:

KNGP VUH LCH J2 LCH Q24 PAYTN J2 TAY T204 SSI JAINS R513 PRISS R514 BDA 3158N 3052N 2947N 2841N 2636N 2530N 2325N 2120N 1815N NALET UG615 MTI OG UR984 KILMO UR984 EDEBA R984 NLY UA610 SOLPA UA607 VND A406 VMF UA406 DVL UR410 TETEM R410 VCL UA400 TIDAL TN.TN1Z FMMI

This result occurs when an airway identifier used in the flight plan is exactly the same as a Navaid in the database.

In your example that is the case for the airway identifier 'J2'.

In those cases when the route is 'built' the waypoint has the higher precedence, and will be selected instead of the airway. So you see the two separate 'J2' waypoint/Navaids inserted into the flight plan instead of the 'J2' airway route intended by the autogenerator.

You can use the 'fsb_nawy_dup.txt' file to specifiy which identifiers are to be treated as airways and not navaids.

Add 'J2' to the list in the file (then restart Fsbuild) and paste the route back into the flight plan box (no need to autogen again) the Build will from then on ignore all instances of 'J2' as a Navaid and will only treat 'J2' as an airway.

This happens occasionally when in a Navdata update a new Navaid is included in the database that has the same indenfier previously used in an airway or a new airway ID matches an indentifier previously used as a navaid.

Regards.
Ernie.