I am trying to fly into Big Bear City, CA (KL35), a mountain airfield which is not a TAF/METAR reporting facility. The nearest facility is Ontario, CA, about 45 miles away, but at a significantly different altitude (944 ft MSL at KONT versus 6748 ft MSL at KL35). If I lock the destination at KONT, I am getting very strong winds on final and on the ground at Big Bear, presumably because the program is giving me winds aloft rather than surface winds, due to basing the winds off the elevation at KONT.Is there a way to make the program aware of KL35 and its elevation? What would adding the facility to the icao.txt file do if there is no TAF/METAR reporting there?RegardsBob

Bob,Sorry to say but adding KL35 would do nothing because it's not a METAR station or a WMO station. Try to lock your destination airport at KONT and set a distance lock greater than 45 miles. I really don't know what results you'll get.Hope this helps,JimActiveSky Support

Bob,I have a potential solution you can try:Add a SECOND KONT entry into the icao.txt file. The lat/lon/elevation should be for KL35. The ICAO ID remains KONT. This should work! It will still retrieve and display KONT but the elevation figure should match for KL35 and properly handle wind transitions for your approach. Let me know..In the future this will be solved via additional processes to determine closest AIRPORT elevation even if it isn't a METAR station.Thanks!-Damian[table border=0" cellspacing="30" cellpadding="0][tr][td align = "left"]Damian ClarkHiFi Simulation SoftwareDeveloper of ActiveSkyThe next-generation weather environment simulation for FS2002!http://hifi.avsim.net/activesky[/td][td]http://hifi.avsim.net/activesky/images/wxrebeta.jpg][/td][/tr][/table://http://hifi.avsim.net/activesky/ima...[/tr][/table

Thanks Damian...I'll give that a try. I think your long-term solution will be barking up the right tree, too.CheersBob