Altimeter+Airspeed Indicator Failures not called by anything, yet they occured

[Icedragon]

So I take my 737 up to a nice altitude of 25,000 feet en-route to KLAS, at 18000 I set my altimeter to 29.92. About fifty minutes in, my altimiter
starts jumping all over the place until eventually reading a negative, shortly after my Airspeed indicator starts doing the same before getting stuck
at 400 KIAS. I declare an emergancy because I have no idea how fast I'm going or where I am, and look for a good airport about 100NM out. My ground
speed according to my GPS system is only 165 knots, so I assume that my Airspeed indicator has gone screwy and ignore the overspeed warnings. Two more
minutes in, and my aircraft breaks into many small pieces and everyone aboard dies. Apparently I declared an emergency without any problems on board,
and I have nothing else but FSP set to give me random failures on my aircraft. This really sucked because I have instant record on and lost my pilot,
my plane, and essentially my company for no apparent reason.

[olseric]

Do you have FS2004 Failures Turned on?

If so, FSPAX won't recognize them as failures.

[nem]

Do you have FS2004 Failures Turned on?

and I have nothing else but FSP set to give me random failures on my aircraft

[Slaghead]

You know what's funny, is this just happened to me a little bit ago. I was flying from Portland to Las Vegas in my shiny new Bravo and all
of the sudden my altimeter started going crazy. I kept hitting 'B' to reset it but it kept saying that I was dropping like a rock. I could see
outside so I knew I wasn't. Weird.

In the flight report it said my max altitude was FL180 but my plane is not pressurized (I'm pretty sure from what I've read in other posts on
this forum) and my passengers weren't freaking out. My airspeed was maxed out and the alarm was going off but I was flying straight
and level. My ground speed in my GPS was still at 192 Kt so I couldn't figure out what was going on until I got the message that I had
crashed (plane breaking up into a million pieces message).

I, as well, do not have any failures turned on outside of FsP. I was flying the default FS Bravo for the record. The co-pilot never mentioned
a failure that I could tell and my flight report also stated that there were no known issues at the time of the crash. Maybe that's only
because I never declared an emergency though.

I was really bummed 'cause I was ~30 minutes from completing a four hour flight. *sigh* My end report didn't say anything about a
failure either though. Luckily I don't have auto-report turned on so I didn't record this one. I didn't lose my 2nd company on a failure that
really isn't one this time! Only 3½ hours.

[Ryanamur]

Do you guys have the registered version of FSUIPC? This could be a problem with the windsheer. If you do, make sure that you enable
the smoothing of windsheer. I've had a similar problem where my Airspeed Indicator droped to zero... turns out it was iced up in a clear
sky using the default clear sky weather from FS2004. Turning the pitot heat on fixed that problem.

The altimiter/airspeed problem is not caused by FsP so you don't need to declare an emergency.

Phil

[Icedragon]

Out of coincidince Slaghead I was flying to Las Vegas as well, perhaps we flew over some spent nuclear fuel rods in the navada desert or something.

As the checklist tells me, I leave pitot heat on the entire time the engine's on, so I don't think that's the problem. Is windsheer generated by FS04
on a rolling basis? If so, shouldn't Idling at straight and level drop me below 340 KTS?

I guess since I'm not quite sure how to fix this at the moment, can anyone at least give me any tips as to how to best manage this kind of situation
in-air?

[Slaghead]

I was only at 10,000 ft over the desert in the middle of the day and it's Summer time. I doubt icing was involved and I don't see how icing
would affect the altimeter anyway.

And what the heck is FSUIPC?

I noticed the altimeter going crazy before my airspeed shot off. It was really strange. I had indeed just passed through the military base
airspace corridor. Maybe it's an evil Microsoft easter egg. haha

Really bizarre. But probably not caused by FsP like Ryan said. I doubt there is anything you can do to fix that problem. I can only imagine
that it may have been a bad download in the real world weather. Typo in the transfer that created an area of some really strange
barometric pressure (really high or reallly low - I don't know which) since we were in the same area at presumably the same time. I
started hitting the 'B' key which would temporarily (for <1 second) the altimeter reading so that's the only evidence I have against that
theory.

You were using the real world weather right? And over Nevada when it happened? A really super high barometric pressure value would
be my guess. Impossibly thick air will shoot the speed through the roof on the IAS readout while GS in the GPS wouldn't be affected
much. I can't think of which direction the altimeter would go in that case. I'll have to go check on that one.