Hi,OK, so I'm enroute right now over El Salvador when my altimeter starting winding down like mad. Looks like station MSSS is causing the problem:MSSS 1950 19005KT 9999 F027 33/21 Q10154 A2998 HZObivously a mistake in the reported QNH. Is there any way in a future version that erroneous values such as this can be ignored so they don't cause havoc. Things seem to be setting down now, but I've been attitude flying the last 100 miles with various swings of the the altimeter, etc.Edit BTW this is B647 of ASE. Now another one is causing problems MHAM with an interpolated QNH of 1181 mb!!!

Hi,OK, so I'm enroute right now over El Salvador when my altimeter starting winding down like mad. Looks like station MSSS is causing the problem:MSSS 1950 19005KT 9999 F027 33/21 Q10154 A2998 HZObivously a mistake in the reported QNH. Is there any way in a future version that erroneous values such as this can be ignored so they don't cause havoc. Things seem to be setting down now, but I've been attitude flying the last 100 miles with various swings of the the altimeter, etc.Edit BTW this is B647 of ASE. Now another one is causing problems MHAM with an interpolated QNH of 1181 mb!!!

I'm not sure where ASE got the METAR with Q10154, as I have a source with universal weather and they report the 1950 MSSS meter as:METAR MSSS 041950Z 19005KT 9999 FEW027 33/21 Q1015 A2998 HZY=

Hi,Somewhere the trailing 4 got added onto the data. We use many different sources for the data. Interpolated data might get thrown off if the actual data is off as in your report if MSSS is one of the actual stations. We can filter things if it becomes a repeating problem.

Hi,Somewhere the trailing 4 got added onto the data. We use many different sources for the data. Interpolated data might get thrown off if the actual data is off as in your report if MSSS is one of the actual stations. We can filter things if it becomes a repeating problem.

I think the problem rests with a manual observer adding to the data from the weather station. Here are the last three hours from Fltplan.com (I think these are pulled from the US weather service) which match what ASE is downloading:MSSS 042355Z 18008KT 9999 FEW020 26/24 Q1013.8 A29.94 HZ MODMSSS 042250Z 18013KT 9999 FEW023 28/24 Q10142 A2995 HZ MODMSSS 042150Z 18012KT 9999 FEW030 30/24 Q1014 A2995 HZYWhereas, Universal Weather has METARs which I think are unedited and straight from the automated weather station. The 2355Z is messed up in both:METAR MSSS 042355Z 18008KT 9999 FEW020 26/24 Q1013/8 A29/94 HZ MOD=METAR MSSS 042250Z 18013KT 9999 FEW023 28/24 Q1014 A2995 HZ=METAR MSSS 042150Z 18012KT 9999 FEW030 30/24 Q1014 A2995 HZY=I wish El Salvador would just stick to the proper ICAO format as it would be less irritating for all. :-p

I had this happen again a few weeks ago. This time it was a station in Cuba reporting a bogus QNH, and this was messing up interpolation hundreds of miles away. I have a screen shot, but I now run FS at a different location on a new PC so I don't have it handy right now. Sorry to bump this, but I'm pleading for some sort of sensibility filter for pressure values in a future update. If the reported QNH doesn't meet some sort of check (say between 28.50 in Hg and 31.50 in Hg or whatnot), it should be rejected and discarded, or say, default to 29.92 in Hg/1013.2 mb. ThanksGraham

Hello Graham, We do indeed have several "failsafe" implementations to prevent such behavior, but we'll be the first to admit it is not (yet) perfect and doesn't always work depending on the data in question despite our attempts thus far, as we occasionally do get these reports (very sporadic and isolated, guessed to be related to interpolation of invalid METAR reports). If you can please send any information including screenshots and/or logs from a problematic session where you experience this it would be much help for us to identify and isolate, and further improve our handling.