Hi guys,

i know this data is provided by Navigraph randomly, but i always try if it's available.  Because of different gate info between charts and addon-scenery (in that case ZBAA data). I checked different gate data format inputs

to get knowledge if just my chosen gate wasn't stored in Navigraph database or they were generally missing. I found one working, which gave out gps position reading. After that i wanted to clean this info, but it wasn't possible to find a proper way.

I also tried the digit "0" This replaced the input before, but was represented by a different gps position again. But i wanted to solve this but I didn't want to close the sim and start it again. So i decided to reload the cold & dark profile.

And then something strange happened. The "wrong" input "0" in the field of gate-positions was still there and kept.

 

And that's the reason why i write this post. Is this intentionally behaviour?

 

As far as i remember PMDG did some "hardening" back in the MD-11 years to avoid  wrong user-inputs which led to crashes sometimes.

Please correct me if i understood the concrete logic on this topic wrong!:

It needs a proper Navigraph database readout to replace a wrong gate number input. But we all know they aren't complete, which makes corrections difficult.  And there is no other option to clean this field.

You can't replace the wrong GPS data itself by input of the correct GPS-position taken from airport charts. (i checked this too)

also a C&D panel state reload keeps wrong gate data.

 

Maybe i missed something, but as user i would be happy to be able to clean this Gate-Numbers line as every other parameter in CDU in every aircraft withoud closing the whole sim.

 

Edited March 4, 20188 yr by PGBosak

Once you have set the INS alignment, your only option to reset the alignment is to turn the units off and then back to NAV and let them align and be sure to set the correct position the second time.

I am aware that Navigraph provides gate data for European and some Asian locations but discussions here seem to be on the side of ignoring the gate entry altogether.  You have a good GPS location so use it, it will be more accurate than a gate coordinate where often there are multiple gates with the same position.  The gate entry was used in the days before GPS was common, and the gate was all you had to set the INS.  Those days are gone.

4 hours ago, downscc said:

Once you have set the INS alignment, your only option to reset the alignment is to turn the units off and then back to NAV and let them align and be sure to set the correct position the second time.

I am aware that Navigraph provides gate data for European and some Asian locations but discussions here seem to be on the side of ignoring the gate entry altogether.  You have a good GPS location so use it, it will be more accurate than a gate coordinate where often there are multiple gates with the same position.  The gate entry was used in the days before GPS was common, and the gate was all you had to set the INS.  Those days are gone.

Good reply, Dan. 

Going back even further before Gate positions became available, the Nav position the crew normally used was the airfield reference Lat and Long. It still pays to do a gross error check of the GPS position  - just in case!

Bertie Goddard

Edited March 4, 20188 yr by berts
amendment

4 hours ago, downscc said:

Once you have set the INS alignment, your only option to reset the alignment is to turn the units off and then back to NAV and let them align and be sure to set the correct position the second time.

I am aware that Navigraph provides gate data for European and some Asian locations but discussions here seem to be on the side of ignoring the gate entry altogether.  You have a good GPS location so use it, it will be more accurate than a gate coordinate where often there are multiple gates with the same position.  The gate entry was used in the days before GPS was common, and the gate was all you had to set the INS.  Those days are gone.

Hi Dan,

 

forgot to mention, i also tried to reset the INS alligment first. the input zero was being kept.