Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

What is your PMDG story

Featured Replies

Not in a PMDG plane, but it's a good FS2Crew story and it's relevant as the same thing would happen to a PMDG plane :-)I was doing a flight more or less due north from NZAA to RJBB (Osaka, Japan), and as the plane was happily cruising and was 100% reliable I left it doing its thing and went off to have lunch. When I got back I had insufficiant fuel warnings and the plane was flying south-west, roughly towards Perth, Australia, and the magenta line on the ND was somewhere behind the plane at a 90 degree angle. I manually turned the plane around and started chasing the magenta line but no way could I catch the darn thing, no matter where I went it went just a little bit further. I felt like a puppy chasing its tail !Suddenly the fuel warning went away, everything on the ND flickered and the magenta line leapt back behind the plane again, but this time when I got lined up it stayed put and I was eventually able to intercept it and resume LNAV, this time flying north-east. Everything was back to normal and it was as though nothing odd had happened, so after a few minutes head scratching I wandered off to take care of a call of nature.When I got back the fuel warning was back and plane was heading south-west again, only this time it was also descending at 5000 fpm and the view through the windscreen had the ocean on top and the sky underneath. Not good ... Auto-everything off, levelled out (the right way up) at about 8000 feet. Auto throttles and auto pilot on, FL-CHG to cruise altitude, up she goes, all normal ... This time I thought the heck with LNAV, Japan is north so I'll just zoom the ND out and fly north-ish by the magnetic compass until I see some RJxx airports appear. That worked, after a while the fuel warning went away and by the time I got near Japan I could see the magenta line looking quite normal so I kicked LNAV back in and the plane took me completely uneventfully to RJBB.There followed a considerable amount of discussion on a couple of forums about what could have caused this, and here's what it came down to : the FS2Crew tutorial flight for that plane starts in KSFO, so those were the coordinates the FS2Crew FO seeded the nav system with. Unfortunately he seeded the nav system with those coordinates on ALL flights. On my flight north I was within range of one radio beacon or another all the time until I got up around the Marshall Islands, then the plane flicked over to INS navigation. The computers took my several thousand miles of flight north from NZAA and applied it to a starting point at KSFO and decided we were somewhere near the north pole, so turned the plane south-east towards Japan (and threw out the fuel warning). While I was blundering around chasing the magenta line we strayed back within earshot of a beacon somewhere and the system realigned itself to the actual position and all was normal again ... until it flew out of radio coverage again, and decided we were back at the north pole, and turned south ... While I had it in HDG we entered the coverage of the Japanese beacons and that cemented things firmly in place.So I learned a valuable lesson (ALWAYS check the coordinates page in the FMC to see where your nav system thinks it is before you take off), but there are 2 things I never did figure out - how the did the plane end up on its back in a dive, and how did I not notice while I was taxying at NZAA that the ND was full of KSFO airports and beacons ??

Gary Lowndes

  • Replies 34
  • Views 6.1k
  • Created
  • Last Reply

Top Posters In This Topic

After being spoiled by the ease of flying the 747 for so long I decided to try to learn the MD-11, let me tell you.......the systems are completely different. I quickly ran through the tutorial and thought I would just take her up, loop around, and try to get my first successfull landing...........I never got off the ground. I ended up in the fence and trees about 300ft passed the runway, I was wondering what that message was the whole way down the runway.................."Warning, stabilizer......Warning, stabilizer"!! Just%20Kidding.gif

Jeff Johnson

This isn't about a PMDG aircraft, but it happened in the Level D 767, which is more or less just as advanced. I was descending into MUHA, flying the approach manually and everything was going nicely until..."TOO LOW TERRAIN". Turns out I forgot to slow to approach speed and lower the flaps and gear.

  • Author

You guys please dont reply to this fourm anymore.This is because of the earthquake in Japan please if you reply please have it turn to Japan. Thank you-Brandon Danyluk

-Brandon Danyluk CYEG

The easiest part of flying is getting off the aircraft

PMDG_T7_sig.jpg

  • Author

Now you can reply again

-Brandon Danyluk CYEG

The easiest part of flying is getting off the aircraft

PMDG_T7_sig.jpg

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.