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.

smike33

Members
  • Joined

  • Last visited

  1. The missed approach point (MAP) is actually at OEV 6.3, 5.1, or 3.8 DME, depending on the aircraft climb capability. This is where the missed approach procedure begins. The missed approach procedure then instructs you to continue on the LOC with a best-angle climb until OEV 1.0 DME, at which point you make the tight left turn back onto the LOC outbound. That is the significance of the the OEV 1.0 DME fix...it does not "exist" in the actual approach, only the missed approach procedure.
  2. Reduces workload... You're not constantly fiddling with the MCP
  3. You can still use VNAV to step down to the LNAV MDA, you just wont have the glideslope and there will be no incentive ie lower mins for doing so
  4. Concerning the approach speed, its correct that while Vref+5 is recommended when landing with autothrottle on, as wind/gust protection is provided, if your landing without A/T or plan to disengage before landing, you need to use the wind additive to find Vapp which IIRC is Vref + 1/2 the headwind component + the gust factor.
  5. Ok yea the procedure must have been updated with different waypoints since the AIRAC cycle used in the tutorial
  6. Volume levels configured as per pg 78 of the NGX Introduction?
  7. This is probably because you selected the LOC/DME EAST procedure, whereas in the tutorial, they fly the SPECIAL LOC/DME EAST. Its very similar, but has specific requirements for aircraft performance and crew training, and has the different DME fixes that you point out. Just enter the restriction yourself using the appropriate LSK-R
  8. It's not out yet...but the A320 from FSLabs will be perfect for you. The systems depth the developers are describing on their forums is very impressive
  9. Well if you use the quick disco button on the yoke, by double clicking it you get the minimum 2 sec disconnect warning
  10. Actually try max sensitivity and zero null zone first, I think that's what fixed it for me, if not it was maybe a 10% null zone (I use FSUIPC for controls now)
  11. If you have Realistic Autopilot Engagement enabled, the aircraft has to be in trim with minimum control surface deflection, attitude near the FD command, and elevator trim not moving, for CMD to engage.
  12. Your toe brakes are engaged. Try setting a null zone, and maximize the sensitivity in the FSX options
  13. Sweet! Been waiting for this one
  14. PMDG NGX, JS41, MD11, 747-400 Level-D 767-300ER Feelthere E-Jets 175/195 Flight1 ATR, Mustang Coolsky MD80 RealAir Scout, Piston Duke, Legacy Carenado King Air C90 CaptainSim 727, 757, 767 Awaiting: PMDG DC-6, 747v2, 777, Dash-8, FSL A320, Majestic Q400, RealAir 172 I have a few more, but those are the ones currently installed. Flying mostly the NGX, Legacy, Duke, and C90 recently. Like others, I've also been somewhat spoiled by the NGX and now find it difficult to take out other airliners...

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.