I've also found this on some of the Australian airports. I've done the magnetic declination fix and whenever I try and do an ILS27 approach into Melbourne, Australia, my FMC is out by 2 or 3 degrees and thus I misalign with the runway.

 

It's not constant, as I can think of only a few others (most recently Hobart, Tasmania), but it is often enough to cause concern.

 

Thanx for the thread, guys, I'm going to keep coming back here occasionally to see if you guys come up with a fix,

 

 

Frank Cooper

I've also found this on some of the Australian airports. I've done the magnetic declination fix and whenever I try and do an ILS27 approach into Melbourne, Australia, my FMC is out by 2 or 3 degrees and thus I misalign with the runway.

 

It's not constant, as I can think of only a few others (most recently Hobart, Tasmania), but it is often enough to cause concern.

 

Thanx for the thread, guys, I'm going to keep coming back here occasionally to see if you guys come up with a fix,

 

 

Frank Cooper

Hello Frank,

 

Hervé has posted how to correct embedded magdev figures within an fsx airport in post #11. Just heed the warnings

Hi guys,

 

How do I find out which airports are not using the magdec file and how do I find out which file/folder they are contained?

 

Regards,

 

 

How do I find out which airports are not using the magdec file and how do I find out which file/folder they are contained?

 

There is a confusion here. Magdec file data will apply everywhere; it ensures aircraft instrument (magnetic) information fits the real data. No more no less.

 

Now regarding airport and ILSs, and from my observations, things can be summarized as follows:  

 

1) Correct alignment (centered loc needle) only depends on ILS characteristics (that is position of localizer, true ILS course as compared to rwy heading) but not on any magnetic variation value. However, displayed "cockpit" heading (HSI) while centered on the ILS will be that of published charts only if the local magnetic variation value (as provided by the magdec.bgl file) is near or equal to the one officially in force at the corresponding airport (most airports use 2010 data but not all..in such a case there is no simple fix)         

 

2) Displayed ILS courses (on FS map & GPS) depend on ILS characteristics (as before) but also on ILS magnetic variation as set in the BGL file (magdec.bgl value is not involved here). For advanced FMC display, I presume it depends on information included in FMC data (as for example the WpNavAPT.txt file for PMDG) that are already magnetic..but I didn't test that extensively

 

 

 

how do I find out which file/folder they are contained

 

 You may use AFCAD (FS9) or Airport Design editor (FS9 & FSX) to locate the BGL file that contains specific airport information

Okaii thank you for that explanation, I think I understand it more now. 

 

Regards,

Okaii Herve, I edited the wpnavapt.txt file for KSAT 12R to put 127 where 124 was and now the runway lines up with the centerline on the ND. I noticed 127 was already there for the ILS section so it looks like only that has been updated with the AIRAC 1309. Is the AIRAC supposed to update the 124 value as well, I noticed you had 126 for FS9?

 

Regards,

 

 

Is the AIRAC supposed to update the 124 value as well, I noticed you had 126 for FS9?

Presumably yes..mine was the one for FS9 as provided by AeroSoft (NavDataPro - LIDO based) and also AIRAC1309. Whatever it is, I think you can play with it if your main purpose is to have a consistent picture but don't forget such FMC databases are built from REAL aeronautical data (that means not always FS compliant) and don't forget to make a backup of original files as always :rolleyes: Also, be aware it will not solve all possible instrumental inconsistencies. An endless "game" indeed ;-)   

Ahh okaii thanks Herve. I'm gonna leave it as it is from Navigraph. Since if I change the values myself when AIRAC 1310 comes out it will only reset what I change back to what they say it is.

 

It is an endless game lol

 

Thanks,

 

Fly UK - Head of Operations

 

Jordan McTiffin