On two flights, one into KABQ w/o a flight plan (from the south) and one out with a flightplan (to the south) I seem to be receiving conflicting METAR info. Just south of ABQ down almost to ONM I receive KIKR as the closest station. The KIKR data seems out of synch with the rest of the area:KABQ 012156Z 00000KT 10SM FEW060 SCT120 SCT250 11/M01 A3013 RMK AO2 KIKR 012153Z AUTO 21014G23KT 10SM OVC031 05/M02 A3015 RMK AO2 SLP199KONM 012153Z AUTO 23017KT 10SM CLR 11/M09 A2999 RMK AO2 SLP109 I realize this is probably for Kirtland AFB, but since KABQ and Kirtland are in essence the same field I do not understand why there would be such conflicting METAR data (temp, winds, sky conditions). It makes for a suprising flight since KIKR does not show in the enroute planning either, and everything else is pretty clear. My cfg file is below. Thanks.Joe LorencVice President, Carolina Operations, VN7 Networkhttp://www.vn7network.com///AS2004 configuration file[General]WindowPosX = -15WindowPosY = 3585DefaultWeatherFolder = C:Program FilesActive Sky 2004ModulesActiveSky2004SuppressionCeiling = 10000SurfaceWindLimit = 40CloudLayerLimit = 5LocalSuppressionRange = 50OnlineUpdates = TrueExtendedDestinationWindsForce = FalseGlobalWrites = TrueVoicePlayback = TrueLocalSuppression = TrueStartupSound = FalseUseProxyServer = FalseFogLayerGeneration = TrueUpdateSuppression = TrueOvercastEnhancement = TrueRouteWindSmoothing = TrueLimitSurfaceWinds = FalseLimitCloudLayers = TrueDisableUpperLayerGeneration = FalseVisibilitySmoothing = TrueDisableMessages = FalseAutoTimeZoneDetection = TrueUpdateInterval = 15VATSIMData = FalseZuluConversion = -7TAFProcessing = FalseWakeTurb = FalseStartPaused = TrueUseSystemTime = TrueDisableCAVOKClouds = FalseProxyAddress = NONE

Joe,Winds: 230 at 17 VS. 210 at 14. Pretty close to meTemps: 5 VS. 11. Pretty close to me.Vis: 10 VS. 10. Same.Sky: Different, yes.I don't know the physical area, but could be some physical landforms in the area causing the slight difference?Hope this helps,JimActiveSky Support

KABQ and Kirtland are the same airfield, so the winds are really not too close (000 vs 21014G23KT), nor are temps (11 vs 5 on the same field), and the sky as you say. It makes for an unrealistic experience since the transition occurs almost right as you leave the field going south, then clears up as you approach ONM.I am familar with the area, and the base does sprawl some, but I believe that most of the civilian and AFB ops would be within the given confines of the field (alot goes on elswhere with a separate base - no airfield and national labs etc).Also, it seems that KIKR can not be "fetched", so there is no way to know what to expect. Comes back no match or ID on Custom Station Report. In the NOAA METAR pages KIKR does not come up either. Makes for for a bad experience when you suddenly hit IMC just a mile or two south of the field that is neither seen, nor reported.Would there be some way for a user to ignore or eliminate certain stations?Thanks.Joe LorencVice President, Carolina Operations, VN7 Networkhttp://www.vn7network.com/

Joe I have noticed this other places also. I kinda would like to have the option to force the weather like WXRE had. But maybe the update will fix some of the small details.

OK, I understand better now. I was comparing the wrong 2 METARs. Right now I am not even sure how to add or subtract a station due to the private weather server. I am going to wait for Damian to come along.Hope this helps,JimActiveSky Support

Looking to see if anything has been done on this - been out of touch for awhile.Joe LorencVice President, Carolina Operations, VN7 Networkhttp://www.vn7network.com/

Ok, been waiting for Damian to "come along" now for almost a month.Can I please get some help on this issue?????Joe LorencVice President, Carolina Operations, VN7 Networkhttp://www.vn7network.com/

Does it still happen on every flight?Edit: And you have updated to Alpha1?Hope this helps,JimActiveSky Support

Hi all,I am working on it, sorry for the lack of recent update. I have tested it with the in-dev MR1 code and note no problems in that area, which may be related to other changes/fixes or something else entirely. I will have a chance to spend more time testing and may release a new beta version of MR1 soon, so you can confirm the fix as well. Hope that helps..Damian ClarkHiFi Simulation SoftwareDeveloper of ActiveSkyhttp://www.hifisim.comhttp://www.hifisim.com/images/as2004betateam.jpg

Yes it still happens, although for instance right now the two seem to match, so there is not an issue today. But I found now that if I delete KIKR from wx_station_list it seems as if it is just never read in, which is a better solution, I guess. If I leave it in I will have to count on those two matching, which seems may not happen. KIKR doesn't come up as a valid station still in 1.01a2.Thanks to both of you for replying.Joe LorencVice President, Carolina Operations, VN7 Networkhttp://www.vn7network.com/