I'm not sure if this is really an AS2004 issue or not... but it's only started recently and I just bought AS2004. :)First off, here's my setup. Athlon 2100+, 512 MB, 40 GB, GF4 Ti 128, Win98 SE.Last week, after stalling long enough :) I got AS2004 (previously I've always used AS wxRE v1.91). I also licensed FSUIPC and WideFS at the same time. I've got a laptop that I network with my desktop, so I put WideFS and AS2004 on there. Not sure if this matters, but there ya go... :) FWIW, I don't use ActiveRadar so I didn't bother with all the extra setup to get it working across WideFS.Now, I know this particular question has been raised before but so far no one has offered any real solutions or even hypotheses.Flight 1, Saturday: default 747 IND to LAX. At some point during the approach my IAS suddenly and absolutely dropped to zero. I was approximately 10 miles from the airport and at ~3200, preparing to intercept the GS. The autothrottle immediately kicked in. Now, here's another weird thing. You know how the 747 panel has a Mach number in the lower left corner? Well, it remained active and (as far as I could tell) accurate. Anyhoo, in the process of getting everything cleaned up I went missed. At some point soon after I went missed, the IAS suddenly came back. Second approach went fine. Now, weather-related stuff. OAT was +21C, winds were reasonable - 280 @ 15, no real shear or anything to speak of. Nearest clouds were about 10 miles beyond the airport - I flew through them after the miss. So icing and wind shear shouldn't have been issues. The skies were fairly crowded but no traffic within 3 or 4 miles and nobody landing ahead of me.Flight 2, Sunday: reloaded the previous flight - I'd saved at about the point of initial descent. At approximately the same place in the approach, the IAS again dropped to zero. This time it only lasted for a few seconds before coming back, but the approach was still borked.I'll check if I still have that saved flight - I think I may have deleted it in disgust. I do have the FP and WX, however.Flight 3, Monday, default C172 VFR CGX (I haven't gotten around to carving up the runway yet...) to ORD. I wasn't paying close attention, but somewhere around the turn from base to final, IAS dropped to zero. This time it never came back. I managed to get the plane on the ground, but it wasn't pretty. Even as I taxied to parking, the IAS and GS remained zero. Do you have any idea how hard it is to taxi a light aircraft when you're not sure how fast you're going? :) I made a few turns on two wheels, I'm sure. Wind was much more brutal on this flight. I was getting thrown around a lot, though still fairly manageable. 275-285 @ 20-30. Again, OAT was good, +17C and no nearby clouds - except for the wind, good VFR weather. I was "behind" an MD-80, but he was on the ground before I made the turn to final.I used the same WX file for all three flights, and likewise the same configuration for AS over WideFS. I did a few short flights just using the built-in "Fair Weather" theme and had no problems. Last week I also flew 737 IND - BWI, again with no problems. That was before I had AS2004 and registered FSUIPC, however.Any ideas? Like I said above, it's hard to say exactly what the problem is. Just because it happens concurrently with AS2004 use doesn't mean it's a bug in AS2004. Could be FSUIPC, or WideFS, or maybe just a fluke - something in FS itself that only manifests itself under certain conditions.

Despite the fact that your OAT was way above freezing, it sounds like the icing issue. Make sure you have the latest FSUIPC version 3.201, which relieves some of the ice problems in FS9. Make sure you have Pitot heat on - best to use shift-H to turn it on, as some aircraft panels don't model the switches correctly. Finally, check the "prevent all icing" option in active sky. Maybe this should solve your problem - let us know!Best,sg

First off, I mis-spoke above... :) The Cessna panel shows the temp. in degrees F, not C... so it actually was pretty dang cold. I've always heard, however, that icing is normally not a clear-air issue... :-roll BTW, has anyone else noticed that the C208 panel doesn't have an OAT display?So I get the issue to reproduce, ON the GROUND, while taxiing after initial startup. Interesting... I also observe that TrafficLook, running on my other PC, is correctly showing my speed. So I shut down TrafficLook, and within seconds, my flight PC begins correctly showing my IAS. Hmmm.... :D