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.

Locking problem at exactly 60 kts on takeoff

Featured Replies

  • Commercial Member

My first flight (BFI-DEN) was perfect. Second flight is DEN-SLC, or at least I'd like it to be. Here's my problem. I am using the same plane (Delta with WLs) for the flight. Everything is set up properly (I'm pretty sure). FMC is set up, Runway 25, ROCKI7 EKR LEAHY3 BOAGY.ILS34R. I line up and press TO/GA, everything works properly. At EXACTLY 60kts, two things happen:

  • The sim stops accepting inputs from my rudder, throttles, yoke.
  • The DUs freeze.

I cannot check for failures because the Aircraft page of the settings is blank. I have tested this about 35 times now with different variations trying to get it to work. What I have tried:

  • Different SID combination
  • A completely new flight with the same set up
  • Different 737-800 (PMDG House)
  • Restarting FS
  • Departing different runway
  • Completely removing the Delta livery using the livery manager, then re-installing the current livery
  • Departing a different airport
  • Not using TO/GA

What worked:

  • Creating a new flight, with the same aircraft, but NOT setting up the FMC. All I did was start the engines, set the flaps and took off with manual throttle control.
  • Using the same Saved flight that wasn't working, I cleared the route from the FMC

Testing the Route:Since it's apparent something in the FMC is causing this error, I was able to go through my set-up and determine that the problem is being cause when I set the approach to the ILS 34R using the LEEHY arrival. If I change the STAR to the JAMMN, then the same runway (34R), it works fine. But that particular combination is causing the problem. Also, if I simply change the runway, the error remains. I have to clear the entire route, then rebuild it with a different combination for it to work properly. Anyhow, I've been at this for 3 hours and I'd like to do my flight (now that I know what's wrong). Hopefully this helps you guys out since it sounds a lot like the issue you guys have under investigation in the stickied post. Edit: same problem with the SPANE arrival/ BOAGY.34R combination

Noah Bryant
 

  • Author
  • Commercial Member

I ended up changing my arrival RW to 34L and there's no problem

Noah Bryant
 

EDIT: Wrong Post

Patrick Hillyer

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.