Fsbuild-2 Flight Planner

Hallo Ernie, here are some examples.

Part of UP600:
UP600 6300 AMSEL 35.966667 -7.883333 H
UP600 6310 VFA 37.013400 -7.975100 H F
UP600 6313 SOTEX 38.292778 -8.220000 H F
UP600 6315 MAGUM 39.167433 -8.392419 H F
UP600 6320 FTM 39.665681 -8.492650 H
UP600 6325 MANIK 40.691944 -8.616169 H
UP600 6330 PRT 42.572500 21.031389 H
UP600 6340 TURON 42.067900 -8.563400 H
UP600 6350 STG 48.696428 9.256547 H
UP600 6360 BEGAS 45.000000 -9.000000 H
UP600 6370 LASNO 48.598333 -9.000000 H

The same position error exists on 22 airways for "STG" (Santiago): 6 Low and 16 High Altitude;
10 airways for "PRT" (Porto): 5 Low and 5 High Airways

Part of UN873:
UN873 6675 TORVA 60.784300 5.599000 H F
UN873 6680 ARS 59.586194 16.650389 H F
UN873 6690 LINSA 59.724500 17.411800 H F
UN873 6700 DODAM 60.044444 19.301667 H F
UN873 6710 MAR 37.055317 -4.939886 H F
UN873 6715 BUKOT 60.196111 20.540556 H F
UN873 6720 TUNUS 60.388611 23.086389 H F
UN873 6724 LAKUT 60.438056 23.876389 H F
UN873 6728 MAROM 60.447778 24.043611 H F

The same position error exists on 15 airways for "MAR" (MARIE): 6 Low and 9 High Altitude;
"TORVA" for UN873(High) and N873(Low)

Part of B491:
B491 5800 URULA 44.810000 38.633333 B
B491 5810 SM 44.783333 38.800000 B
B491 5820 ATREL 44.253333 40.946667 B
B491 5830 PR 50.144000 14.367300 B
B491 5840 KW 43.398333 132.153333 B
B491 5850 INKUT 43.195000 46.086667 B
B491 5860 MEBOS 42.815000 47.653333 B
B491 5870 OLMAT 42.528333 49.285000 B

Both "PR" (Peredovaya-2 airways) and "KW" (Kislovodsk-3 airways) way out of position!!

This is only a small example of the many position errors i discovered. It seems the wrong intersection/navaid "ID" was used when building the airway file as the postions in the nav's or ints files are correct.

Regards,
nand144

Ok thanks for that.

I was able to find the problem. Its not an easy fix, so its not likely for this update. But it should hopefully be fixed for the next update.

Regards.
Ernie.

Hallo Ernie,
I just downloaded the newest cycle (0813) from the website and had i quick look before updating.
I have the impression that there are still anomalies in it:
just looked at only 3 airways
About >100 deg. difference in longitude for 2 consectutive fixes ?

UN873 6680 ARS 59.586194 16.650389 H F
UN873 6690 LINSA 59.724500 17.411800 H F
UN873 6700 DODAM 37.213333 126.496667 H F
UN873 6710 MAR 60.140900 19.914300 H F
UN873 6715 BUKOT 60.196111 20.540556 H F
UN873 6720 TUNUS 60.388611 23.086389 H F



B492 5660 SH 32.501778 -93.878108 L
B492 5670 LAMEX 48.165000 30.088333 L
B492 5675 LIDNO 48.726944 29.946944 L
B492 5680 GOROS 49.456667 29.758333 L
B492 5690 SL 50.186667 29.563333 L

B491 5760 LENKA 45.363333 35.788333 L
B491 5770 BETEG 45.183333 36.383333 L
B491 5780 PALER 35.270900 -85.351800 B
B491 5790 ANAKA 45.001667 37.348333 B
B491 5800 URULA 44.810000 38.633333 B

regards,
nand144

It should be noted that most Australian airways are similarly affected. I have been caught out on a couple of occasions whilst flying VATSIM. I have to pretty much remember to correct almost all waypoints in a given airway (eg W449) otherwise I end up tracking to some place in the northern hemisphere with an estimated time of arrival 39+ hours Embarrassing when ATC asks why I am not navigating according to my submitted flight plan.

_________________
Russell Diehl
TinRoof Rusty