Fsbuild-2 Flight Planner

I am new to FSBuild, but like what I have seen.

I have attempted to enter the following flightplan - VHHH OCEAN2A OCEAN V3 ENVAR M750 MOLKA M750 TAERU M750 MJE A590 POWAL A590 PLADO A590 PINTT A590 HAMND GASTO2 PANC.

When I try to get FSBuild to process the flightplan it has trouble with V3. It tries to plot V3 over 3000 miles from where it should be. To get the flightplan to work I had to put the intersections that make up the airway in manually. OCEAN and ENVAR are on V3. What am I doing wrong?

Thanks for the help,

Bill

I have attempted to enter the following flightplan - VHHH OCEAN2A

I did not see OCEAN2A in fsbuild SID pulldown list.
I did see OCEA2B. Try it.

The flight plan you entered ... where did you get it from?
What version of FSBuild?
Which FSBuild Airac are you using

_________________
Vaughan

If you use RWY07R you will get OCEAN2A.

I am using FS2.3 and AIRAC 0902.

Bill

For 7R I see OCEA2A

The flight plan you entered ... where did you get it from?

I am using FSBuild Version 2.3.7.6

_________________
Vaughan

Did you try OCEA2A yet?

_________________
Vaughan

I did not have trouble with the SID - OCEA2A. The problem is with the Transition Route - OCEAN V3 ENVAR. FSBuild thinks V3 starts 3,000 miles north of OCEAN. FSBuild thinks the distance from OCEAN to ENVAR on V3 is 6,000 miles when it is only 153 miles.

Bill

Going in plan mode with your route string and rwy 07R, FSBuild replaces "OCEAN V3 ENVAR" with "OCEAN DCT ENVAR" (96nm). Looks to me like a problem with the current Airac - V3 does connect the two fixes on the charts that I have.
Tom

_________________
Tom

Your original route:
VHHH OCEAN2A OCEAN V3 ENVAR M750 MOLKA M750 TAERU M750 MJE A590 POWAL A590 PLADO A590 PINTT A590 HAMND GASTO2 PANC.

** You do not have waypoints to get onto/off V3.
** OCEAN2A does not exist.
** OCEA2A for RWY07R does exist and it contains OCEAN as an exit waypoint.
** ENVAR is part of V3 but you cannot get onto it.

So, this works ok:

VHHH OCEA2A ENVAR M750 MOLKA M750 TAERU M750 MJE A590 POWAL A590 PLADO A590 PINTT A590 HAMND GASTO2 PANC

_________________
Vaughan

It might be its confusion a waypoint identified as V3 with an airway that also has the V3 identifier.

When it processes the identifier in the flight plan box it first checks it against the navaids database, only when it doesn't find it amongst the navaid data it then checks it in the airways data.

So if its finds a V3 in the navaids files, that's what it will use by default, and that may be why its over 3000 nm's away.

To get around this, the fsb_nawy_dup.txt file has a list of these duplicate navaids. Its in the main FSB folder. Open that file, and take a look, if 'V3' is not in there, then add it, and try the route again (after restarting the program).

Regards.
Ernie.

_________________
Vaughan