HelloI had a problem during my last flight. one hour from and to the same airportThe QNH, in finale, changed incessantly. I had to adjust it many times before landing.maybe it's due to the problem date/time error in the post below. I don't know. then, I prefer to create this new postLuc

Hi,We think it was the data issue that was causing this. Let's just have you keep an eye out and then you or anyone else can report back here.

JimTo mention, I have in both ASA & ASE (FSX non DWC in real time) had problems with the destination QNH being "inaccurate" (?).It is not unlike Luc's problem but not exactly his.In summary, on many if not all flights, I notice the QNH does not change from the departure setting (which agrees with the ASE engine at departure) so that sometimes when I arrive 4-800nm away, the FSX ATIS (& hence airport elevation) are 5mb different to the ASE forecast / ATIS (112.025) - most of the time it is a manageable smaller difference as the destination is not that different to departure.When one lands (eventually & roughly), the aerodrome elevation matches the FSX Atis (the departure QNH) - and not ASE's destination forecast.Any difference though is a nuisance and can make a hell of a mess of an approach leaving one low or high depending (?). Maybe I'm wrong, but it does seem an aircraft uses ASE's data to simulate the ILS glideslope & other altitude data, but ASE data does not input successfully / completely to the runway data (?)For now, your comments to this confusing saga would be appreciated !CheersJohn

Yep, on Sunday I was getting QNH's leaping all over the place near my destination (i.e. within 10 miles) as well despite having 'force destination weather', 'lock to closest' and d/l Vatsim weather with a full route loaded in. Hopefully it was the data issue Jim mentioned so I'll check it out tonight.

There has been problems with the QNH over the last few days both in ASA and ASE but its not their fault.I have had QNHs of 10220 and 0734 and have checked the NOAA site (http://weather.noaa.gov/weather/metar.shtml) which has shown the same QNHs so the source data is wrong.Rog

Same for me, but I always hit the b key on approach couple of times for security :)

Hi John,One question for now: After AS and FS start and load their initial data are you refreshing the AI system using the Refresh AI Aircraft icon in AS?

Me? No, I restart my UT2 after weather is loaded. Should I refresh AI and eventually UT2 after it?

No, I know you as ST! :(

Good one... T stands for Tom, but... what about refresh of Ai?PsYou lost to Canada :(

Hi ST,Yes, refresh AI.Yes, one meaningless hockey game, but like we like to say in the USA................ SCOREBOARD, SCOREBOARD, SCOREBOARD :( :(

Hi John,One question for now: After AS and FS start and load their initial data are you refreshing the AI system using the Refresh AI Aircraft icon in AS?

JimTo answer, no I didn't / don't refresh AI !However to further add to "my" confusion after another flight today on the same YBCG to YSSY route in an E190 for a 60min / 390nm flight (90min gate to gate) but this time noting a bit more detail about the weather etc.

• ASE / FSX, no DWC, dynamic rate 30%, downloads at 10mins, FS haze layer disabled
• Metars / Tafs downloaded by ASE much the same as real world data thru NOAA / Oz BOM (easterly / rain / low cloud & visibilty /QNH 1011 @ YBCG - southerly / few clouds / no rain / good visibility / 1019 @ YSSY) even given YBCG is an interpolation.
• @ Departure, all weather accurately depicted against ASE
• At TOD (100nm YSSY), RealAtis reported YSSY weather (all) matching ASE download for YSSY
• At 50nm YSSY, FSXAtis & RealAtis reported different YSSY weather and to be the same as YBCG weather.
• On final then landing, weather (wind / cloud / QNH ) all as per YBCG & as reported by ATIS
• During ILS, at outer marker, QNH was different again at 3mb higher than Atis (B push check)

At the terminal, I (immediately) closed ASE but not FSX, then restarted ASE to get correct weather @ YSSY depicted !So, are we all as confused as I - in hindsight, I must express a doubt that I saw this scenario in ASA.For nowCheersJohn

JimTo report, another flight different route but same scenario - and to confirm that I listened to destination Atis from TOD (100nm) continuously and it flip/flopped from departure to destination weather until about 20nm to run & then stayed on departure weather.

Unfortuately the QNH is still hopping around. Just did a (Vatsim) flight and at origin the QNH matched the Metar spot on, no real pressure issues during cruise but on descent into the destination the QNH was all over the place, with 'lock to closest' on, being vectored off the STAR, onto Downwind and Final I was having to constantly keeping hitting "B" to stay on path. Tisn't working quite right at all I'm afraid.