After watching the movie, I thought I would duplicate Amelia's around the world flight, hopefully without disappearing as she did.Everything went swell through the first 17 legs all the way from Oakland to almost Karachi, Pakistan. Then everything turned into something that smelled bad. HHMS to OPKC. I bypassed the airports in parenthesis and my planned flightpath navigating NDB's was as follows:HHMS > KRY (OYAA) > SYN (OYRN) > GDA (OYGD) > SAN (OOSA) > OA (OONR) > HMA (OOHA) > OL (OOGB) > NSB (OOMS) > JI (OPJI) > GD > PI > OR > (OPOR) > MR354 > KC > OPKCEverything went flawlessly until somewhere between OPJI and OPOR. I started to loose manifold pressure and my altimeter went crazy. Resetting barometric pressure was also all over the place progressively. I make an emergency landing at OPGD (after a few bounces). I saved the flight with my location on the Apron at OPGD, restarted my computers, FS9, and ASE. When I pressed my assigned altimeter reset button, barometric pressure went to 14.99"I then started to check locations with ASE. The following was the progression for barometric pressures:OOGB: 29.91"OOMS: 29.97"OPJI: 21.39"OPGD: 14.99"OPOR: 14.98"OPKC: 0.00"OPMK: 7.47" (First airport in my next leg which I have not flown yet)VADS: 23.91"VAJB: 29.90"I tried this both with FS9 running, and with FS9 shut down. Same results.I then tried a continuation of my flight from OPGD where I made the emergency landing with the live default updating weather option in FS9. No problem all the way.I then tried to see what would happen with ASA. Another problem I will describe in another post.Anyone ever seen anything like this and have any ideas for a solution?Thanks:RTH

Hi,There was a report of this in the last 36 hours around that same area, so it could have been some bad data. ASA/ASE use the exact same data sources so no changes there.

Thanks for the prompt reply Jim:I just cranked up ASE again a few moments ago, OPKC, the previous location with a barometric pressure of 0.00" now reads, 29.94". Glad to know that it was a hopefully a unique temporary and rare quirk.Respectfully:RTH

Hi,There was a report of this in the last 36 hours around that same area, so it could have been some bad data. ASA/ASE use the exact same data sources so no changes there.

I find it a constant problem when flying over Pakistan, I remember this happening to me a couple of weeks ago and if my recollection serves me well it used to happen a lot when I used ASA.I used to disable some of these stations as flying the PMDG was near enough impossible with the QNH shifts.Another place I used to find trouble was east of Singapore stretching down to Jakarta.Like Jim has pointed out I think these areas suffer a lot from bad data.

Yep. Things were not as good as I thought they were this morning. Somewhere between OOMS and OPJI things started to smell bad again. Barometric pressure at OPJ1 was 25.96". At OPOR it had declined to 22.91". Better than 0.00" which I had in this region last night but it obviously varies below a pressure nowhere near high enough to remain in the air. Manifold pressure reduces to the point that one cannot maintain enough power to hold altitude.My solution was to immediately switch to the 15 min. updated default weather in FS (Yea, I know, aint it the pits). Be sure to turn ASA or ASE off if you do this or the next time it updates it will take FS default weather away from you and put the bad stuff back in.For what it is worth, a Google search came up with the following as the lowest pressure ever recorded. I am surprised that the reconnaissance aircraft was able to stay in the air."The lowest pressure ever measured was 25.69 inches, set on Oct. 12, 1979, during Typhoon Tip in the western Pacific Ocean. The measurement was based on an instrumental observation made from a reconnaissance aircraft."Happy flying.RTH