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.

josch1703

Members
  • Joined

  • Last visited

Everything posted by josch1703

  1. Hello MD11 Drivers, shortly after take off (at about 800-1000 ft AGL) I engage Level change as a vertical mode. This triggers AT to change immedeately from TO Power to CL Power. Why does it do so? The manual states that whenever you engage Level change before reaching climb thrust altitude set in the FMC (e.g. 1500 ft AGL) this solely arms the system to change automatically from take off power to climb power at climb power altitude. Am I wrong? Thanks in advance, josch
  2. Hi everybody and thanks for your support. Just like Robin said, I don't think that it has anything to do with the flight plan - apart from the fact that the SID is set up correctly. The 90 degrees turn at Nezug (it's 89 degress to be accurate) is part of the Summa Seven departure at KSEA. The point is, the autoflight system used to work perfectly even without any flightplan. It is the most basic of all AP maneuvers: keeping wings levelled. And by the way: arming NAV on the ground still works fine, ap keeps perfectly track of the magenta line - even with some discos ahead. That's why I think it's a conflict with something outside the PMDG - maybe some struggle with another dll or anything like that. I reinstalled the MD11 twice, deleted all remaining folders, I tried different panel set ups - the problem still remains.The strange thing is that it came out of a sudden: No change in configuration, no installation of software which might could have provoked such a strange behavior. Kind regards josch
  3. Hi Robin, thats exactly the way it should work - and the way it worked for me until yesterday. Watch the attached files. After TO is the most interesting one. At 5 feet RA FMA has changed from Takeoff to Heading 184 - don't ask me where that particular value comes from - fcp still shows 341 one. But even more weird ist the white bowtie on the ND, indicating a selected heading of 290. Were does this thing comes from?
  4. Hi Robin, thanks for your kind and fast response. I'll check this evening and provide you with corresponding screenshots. (I'm not at my flightsim computer right now). What I can tell you is that speed is in pitch mode with V2 set in the FCP as a backup for the FMS-generated V" speed. Green box is checked.Speeds are confirmed and show up in magenta colour. All fields are in TO/APPR Page are complete, sr/V3 is shown in the the MCDU. AT is armed and kicks in shortly after 70-80 percent N1. Values for Thrust (flex mode 59, computed by Topcat) are exactly held (no spiking or errating behaviour caused by hardware) Altitude 5000 ft is armed and shown in white colour on the FCP. I do not arm prof or NAV on the ground because I practise on more basic technics. I usually switch to Flight Level change at CLIMB THRUST Altitude in order to change to climb thrust and continue to hold V2+10 until ACC Alt manually. Heading changes are flown by hand with appropriate inputs on the FCP for backup until I intercept my SID or ATC gives me vectors or a DTO to a waypoint. Anyway thanks for your support. I'll keep you updated. regards, josch
  5. Dear Md11-Drivers – I‘am helpless: Currently I’am working on my take off techniques in FS9. Everything worked as it supposed to be. But for two days now I encounter a very strange problem: RWY 34L at KSEA: Immediately after getting airborne (Radio Alt. 4-5 ft.) take off mode is automatically replaced by heading mode, on the FMA Control Window Roll Control Mode changes from Take off to a white "Heading 019" reading although heading knob on the FCP is set to the proper runway heading of 341. What’s wrong here? Did a lot of uneventful take offs before and never encountered such strange behavior. No use of external hardware (I disabled my vrinsight MCP, the bug still remains). I was able to reproduce this situation in other airports like KORD and KJFK though the divergence between the heading reading on the FMA and the heading set on FCP is only a few degrees in contrast to what happens at KSEA. I tried with other airplanes (pmdg 737 for example) – no problems at all! I even re-installed the MD11 without success. For those training flights I usually use the standard situation of FS9, choosing MD11 from the start up menu together with the Ready-to-taxi-Panel Configuration from the pmdg menu. The aircraft is properly configuered for take off, all relevant data is set in the MCDU. Thanks in advance, any help is highly appreciated! Josch/Germany

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.