Zeuss_1238

747 not aligned with runway

Recommended Posts

I just recently purchased the PMDG 747 and am super impressed and enjoy the product but, yesterday I tried a flight and when I stepped through my route I noticed the path wasn't alligned with the runway! The plane would be off and wouldn't go directly to the runway.

is there a way to fix this?

I had a similar issue in the Aerosoft Airbus in p3d v3 a few months back but now its showing up again :/ 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

2 minutes ago, Zeuss_1238 said:

I just recently purchased the PMDG 747 and am super impressed and enjoy the product but, yesterday I tried a flight and when I stepped through my route I noticed the path wasn't alligned with the runway! The plane would be off and wouldn't go directly to the runway.

is there a way to fix this?

I had a similar issue in the Aerosoft Airbus in p3d v3 a few months back but now its showing up again :/ 

What airport are you using (payware/default?) and what airac cycle do you have installed?

Share this post


Link to post
Share on other sites
27 minutes ago, PMDG777 said:

What airport are you using (payware/default?) and what airac cycle do you have installed?

Using default, and the current airac cycle, 1708

I was going from KORD Chicago to KADW Andrews Air Force base in Maryland

Share this post


Link to post
Share on other sites
12 minutes ago, Zeuss_1238 said:

Using default, and the current airac cycle, 1708

I was going from KORD Chicago to KADW Andrews Air Force base in Maryland

I'm guessing the scenery and latest airac don't quite match up which is why there's a slight heading difference

Share this post


Link to post
Share on other sites
7 minutes ago, PMDG777 said:

I'm guessing the scenery and latest airac don't quite match up which is why there's a slight heading difference

I see

Is there anything I can do?

Share this post


Link to post
Share on other sites
15 minutes ago, Zeuss_1238 said:

I see

Is there anything I can do?

Can you be more specific about the issue that you're having? I'm not convinced that what you're seeing isn't simply the plane correcting for the wind.

Share this post


Link to post
Share on other sites

The AIRAC files are built using current magnetic declination data...the stock FSX/P3D mag dec files are based on very old 2006 data.  The difference (resulting from migration of the earth's magnetic poles over time) can cause you to line up off-centerline when using an AIRAC-based nav systems with the default scenery base.

Herve Sors keeps an updated magdec file for FSX/P3D for download on his site at: https://www.aero.sors.fr/navaids.html

Updating to that generally solves the slightly-off-centerline issues people have when using AIRAC-based nav systems.

Regards

Share this post


Link to post
Share on other sites
27 minutes ago, w6kd said:

The AIRAC files are built using current magnetic declination data...the stock FSX/P3D mag dec files are based on very old 2006 data.  The difference (resulting from migration of the earth's magnetic poles over time) can cause you to line up off-centerline when using an AIRAC-based nav systems with the default scenery base.

Herve Sors keeps an updated magdec file for FSX/P3D for download on his site at: https://www.aero.sors.fr/navaids.html

Updating to that generally solves the slightly-off-centerline issues people have when using AIRAC-based nav systems.

Regards

Thanks!

I have downloaded this and it hasn't worked :(

I am now also having the issue in the 737

Trying to do a flight from Anchorage to Barrow in Alaska

 

Share this post


Link to post
Share on other sites
1 hour ago, scandinavian13 said:

Can you be more specific about the issue that you're having? I'm not convinced that what you're seeing isn't simply the plane correcting for the wind.

when I look through my route the won't be aligned with the runway

The purple line so to say is not aligned with the white dotted line

Share this post


Link to post
Share on other sites
4 hours ago, w6kd said:

The AIRAC files are built using current magnetic declination data...the stock FSX/P3D mag dec files are based on very old 2006 data.  The difference (resulting from migration of the earth's magnetic poles over time) can cause you to line up off-centerline when using an AIRAC-based nav systems with the default scenery base.

Herve Sors keeps an updated magdec file for FSX/P3D for download on his site at: https://www.aero.sors.fr/navaids.html

Updating to that generally solves the slightly-off-centerline issues people have when using AIRAC-based nav systems.

Regards

I tested another flight going to North Carolina with the 737 and its still not aligned with the runway

Share this post


Link to post
Share on other sites
3 hours ago, Zeuss_1238 said:

Thanks!

I have downloaded this and it hasn't worked :(

I am now also having the issue in the 737

Trying to do a flight from Anchorage to Barrow in Alaska

 

If you're flying into default airports using current AIRAC data it's still gonna be a problem, as the magdec file does not redefine navaid courses for default airports...most of the add-on airports incorporate magdec data current as of the date is was produced.  Some of the better AFCADs for default airports also fix the problem, but the reality is that not all scenery and aircraft data is played from the same sheet of music.  To get it right, the magdec needs to be current, the ILS course needs to be based on the current magdec, and the AIRAC data off of the same declination data.  Over time, even with high quality add-ons, there is some divergence, unless the dev updates his scenery when changes occur--the worst ones are when a RWY number changes and the markings and nomenclature doesn't any longer match the approach plates.  This happened a few years back for PANC, when 06 L/R became 07 L/R, and all the ATC still used 06.

Regards

Share this post


Link to post
Share on other sites
1 minute ago, w6kd said:

If you're flying into default airports using current AIRAC data it's still gonna be a problem, as the magdec file does not redefine navaid courses for default airports...most of the add-on airports incorporate magdec data current as of the date is was produced.  Some of the better AFCADs for default airports also fix the problem, but the reality is that not all scenery and aircraft data is played from the same sheet of music.  To get it right, the magdec needs to be current, the ILS course needs to be based on the current magdec, and the AIRAC data off of the same declination data.  Over time, even with high quality add-ons, there is some divergence, unless the dev updates his scenery when changes occur--the worst ones are when a RWY number changes and the markings and nomenclature doesn;t any longer match the approach plates.  This happened a few years back for PANC, when 06 L/R became 07 L/R, and all the ATC still used 06...

Regards

So what do recommend I do?

Share this post


Link to post
Share on other sites
Just now, Zeuss_1238 said:

So what do recommend I do?

Either live with it, or spend a lot of time in ADE tweaking navaids (doable if you only fly to a limited number of airports).  There's nothing an aircraft add-on maker can do, given the wide variety of combinations of add-ons and magdec files that would have to match with the AIRAC.

Regards

Share this post


Link to post
Share on other sites

For the 747 QOT have you checked "On" for "Correct Loc Course to Sim"?  See Introduction manual page 0.00.98 (pdf page 98).

Similar setting in 737 NGX.

The default KORD is very out of date, as to runway numbers, location of runways, etc.  Search KORD in Avsim AFCAD or scenery libraries for updates.  Pretty sure Ray Smith has an accurate one.

Mike

Share this post


Link to post
Share on other sites

Don't obsess with the extended runway center line. It means very little, just a nice reference.You said the "plane wouldn't go directly to the runway" and yet I assume you landed on the runway because you didn't indicate otherwise. I'm with Kyle, I'm don't understand the problem as explained.

Share this post


Link to post
Share on other sites
22 hours ago, downscc said:

Don't obsess with the extended runway center line. It means very little, just a nice reference.You said the "plane wouldn't go directly to the runway" and yet I assume you landed on the runway because you didn't indicate otherwise. I'm with Kyle, I'm don't understand the problem as explained.

SFO to Denver Flight




SFO to Seattle

 

 

Share this post


Link to post
Share on other sites

Are you trying to say the waypoint KLEWS is not on the extended centerline as expected?  That is what we are trying to explain to you... the waypoint is defined by a lat/lon coordinated and puts it on the runway centerline based on no magnetic deviation.  Now add a different deviation to the airport scenery than exists in the global scenery and you get exactly this.  Just a slight mag dev difference.

I often spend a couple of hours on an airport bgl file correcting things such as navaid locations, type lighting, etc., and the airport mag dev on every airport I've done this to has had to be corrected except Flightbeam.

Share this post


Link to post
Share on other sites
6 minutes ago, downscc said:

Are you trying to say the waypoint KLEWS is not on the extended centerline as expected?  That is what we are trying to explain to you... the waypoint is defined by a lat/lon coordinated and puts it on the runway centerline based on no magnetic deviation.  Now add a different deviation to the airport scenery than exists in the global scenery and you get exactly this.  Just a slight mag dev difference.

I often spend a couple of hours on an airport bgl file correcting things such as navaid locations, type lighting, etc., and the airport mag dev on every airport I've done this to has had to be corrected except Flightbeam.

So how might one correct this

Editing the bgl file?

I cant seem to open it

Share this post


Link to post
Share on other sites
3 minutes ago, Zeuss_1238 said:

So how might one correct this

There is probably no need, the ILS LOC is probably lined up with the fix and not the extended centerline... as I said earlier the extended centerline has very little value most time.  And in this case it looks like 1 deg of error, come on, there's gotta be more pressing issues to resolve.

EDIT: I should answer the question.  Open the airport BGL in ADE and in the airport propertied UI correct the mag dev number using FAA NASR data.

Share this post


Link to post
Share on other sites
Just now, downscc said:

There is probably no need, the ILS LOC is probably lined up with the fix and not the extended centerline... as I said earlier the extended centerline has very little value most time.  And in this case it looks like 1 deg of error, come on, there's gotta be more pressing issues to resolve.

Sorry :(

I was just wondering cause I usually take the thing off autopilot when established on the glide slope

Should I just select a different approach type?

 

Share this post


Link to post
Share on other sites
Just now, Zeuss_1238 said:

Sorry :(

I was just wondering cause I usually take the thing off autopilot when established on the glide slope

Should I just select a different approach type?

 

Linus, there is not a problem that you need to solve.  Fly the localizer just like you always do, you will end up at the runway.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now