You may be mixing things up here, no bug request necessary
V442 is defined by the 12 degree VOR Radial, but LNM shows the magnetic heading for your course - two completely different things. The VOR radial and the actual magnetic heading rarely are exactly the same because of magnetic variation… Check out this old thread A VOR was off by 5 degrees. List of problematic VORs? and it might become clear (I had the same question back then )
Today I got an interesting idea/case which is easy to reproduce (same issue as above):
Case 1: Make the following route KSNA → SLI → PDZ → APLES → HEC (Course between PDZ and APLES same as on SkyVector chart)
Case 2: Set KSNA as departure and select the ANAHM1 transition HEC, it is the same connection as in CASE 1 only done automatically (course between PDZ and APLES is 15, not good)
I must also say my Navigraph AIRAC is 2105 which might be the issue, or Navigraph didn’t update that SID (less likely). Would be happy if someone could try it with current the Navigraph AIRAC.
P.S. Until this point I didn’t know that LIttleNavmap does not calculate it self the course between waypoints/vor if it uses Navigraph data…
The courses shown for Victor airways on enroute charts typically do not show the actual magnetic heading. The number 012 in this case is what you set the OBS course selector to in the aircraft to track a specific radial.
VOR radials are referenced to the zero degree radial of the specific VOR. The zero degree radial is set to actual magnetic north as it existed when the VOR was originally constructed. It is never changed after initial entry into service. Because of changes in magnetic variation over the years, very few VORs have zero degree radials that point to where magnetic north is now in 2021.
The PDZ zero degree radial is based on 1965 variation of 15E. The actual variation in 2021 is 11.7 E
I understand thank you for the explanation. Why is it different if I select the SID departure and if I make the SID departure points my self in LittleNavmap? See Case 1 and Case 2 above.
LNM uses VOR declination to calculate magnetic courses from and to the VOR for enroute segments in the flight plan.
This should explain the discrepancies. Declination for VOR (calibrated) and environment (shown in status bar) is taken from the sim, BTW.
No calculation is necessary for procedures since course is already given in magnetic (and does not consider VOR calibration). This can also result in small rounding errors where a departure line does not match the runway heading, for example.
The multiplayer aircraft are not delivered through SimConnect. I hope Asobo fixes this in a future update. It is acknowledged as an issue as far as I’ve seen in the forum.
You are right I disabled the calibration as you described and it shows the same course as the procedure (15 degrees), the problem is that the calibrated value 11 degrees was the correct one and the procedure 15 degrees was the wrong one, and there is no way to enable the calibration for the procedures right?
11 degrees is not correct. The actual magnetic heading from PDZ VOR to APLES waypoint is indeed 15 degrees.
Again, (I cannot emphasize this too much), VOR radials do not represent magnetic courses. The number 12 is what you have to dial into the VOR course selector to fly the V442 airway from PDZ to APLES. If you fly outbound on this radial with the CDI needle centered, your magnetic heading will be 15 degrees.
This would only be the case if there is no wind. With a crosswind you would have to apply either a left or right wind correction, so your actual heading would be either greater or less than 15 degrees.
This would be difficult since some procedures use complex maneuvers. I’d rather use the magnetic course as provided in the procedure data.
Absolutely correct.
To add more to the “fun”: For longer legs there is also start and end course which can be different due to great circle line.
As if that wasn’t enough there might be also different declination values at the start and end of a leg.
You can enable display of true course at flight plan legs in options on page Map Display 2. Tree element Flight Plan on the right side. Very helpful far north or south.
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x60c0b1e3
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.19041.1081, Zeitstempel: 0xde3fc775
Ausnahmecode: 0xc0000409
Fehleroffset: 0x000000000010bd3e
ID des fehlerhaften Prozesses: 0x52d8
Startzeit der fehlerhaften Anwendung: 0x01d77823aff14524
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: f648f41a-6470-4bab-ae6f-5d36b7875106
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
I loaded that PLN with no issues on the world map.
I don’t have the plane you are using, I used the DC-6.
Also starting the flight was no issue.
Very heavy raining weather there currently, though.
As far as I remember you either have to enter them on the main map screen before you launch your flight, or you need to enter them into the G1000 by hand. I haven’t used the WorkIng Title mods for the G1000 in months, but I don’t remember them having the same feature as the modded GNS 530, where you can load a flight plan on disk.
To be fair, none of this is to do with the program Little Navmap. You should probably ask this in the appropriate group, for third party planes.