Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

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.

Autopilot still struggling to follow non-INS courses, especially localizers and ILSs

Featured Replies

The L1011 autopilot still needs a lot of refinement. In my last few flights alone I have experienced:

  • The autopilot struggles to hold altitude during a turn, especially when low and slow, where you may lose as much as 1,000 feet in a deep turn.

  • The autopilot struggles to capture VOR radials and localizers, even when the intercept angle is less than 30 degrees. I have set up to intercept localizers at a very modest intercept angle at places with parallel runways like ORD and ATL, and the autopilot consistently turns so late to capture the ILS that you fly through the approach path of the parallel runway and then it curves back around to try and track the intended runway and may even overshoot that turn, too.

  • When a radial or localizer is captured, the autopilot fails to track it and keep the course needle fully centered. This is especially problematic for ILSes. This behavior is especially bad when there is a crosswind.

  • Sometimes even when centered on a radial/localizer per the course needle, you are off course. I flew the ILS 27L into ATL the other night and when tracking the localizer with the needle centered, with no crosswind and no crab angle, looking straight out the window it looked like I was lined up on 27R until I was maybe a mile out. It is not an offset approach, and if it was, it wouldn't be offset into the approach path of a neighboring runway.

  • The autopilot and PMS routinely struggle to connect to each other. Even when the PMS is properly configured -- I have been through the documentation and know what it needs to work -- the autopilot and TM mode of the autothrottle can sometimes take 5-10 minutes after takeoff before they'll recognize each other and go into EPR mode for TM and VNAV mode for the autopilot to climb via the PMS speed plan.

As myself and others have been noting on the forum recently, the L1011 still needs -- and deserves! -- significant attention from iniBuilds so that the add-on can live up to the high potential that it has.

Create an account or sign in to comment

Account

Navigation

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.