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.

Still having problems landing

Featured Replies

A few days ago i posted a problem, thinking my F.O. was turning off my Autopilot on final approach. Well if he isn,t doing it, then it must be something to do with interaction between Fs2Crew and NGX. Of course it could also be the Captain.

 

As i posted before, after Localizer capture, then sel. APP, then CMD. B, i lose my autopilot,LOC and G.S. and have to quickly take over and manually take the aircraft in. I normally do this at about 1200ft AGL, but by choice.

 

If after the approach check list, i do not communicate with my F.O. and just follow my star and perform all of the flaps settings, gear down etc., everything goes as planned until i take over at around 1200ft AGL.

Try using my F.O. exactly as the tutorial reads and i lose LOC and GS and my A.P. (A & B) are off.

 

Have tried reinstalling SP1C, Fs2Crew (v 1.2), different runway. Still the same.

 

Any Ideas?

Rick Hobbs

Boeing777_Banner_Pilot.jpg

 

  • Commercial Member

Hi Rick,

 

1. Check your CVR log to ensure the speech system is not hearing "autopilot off" or any voice command that would disconnect the autopilot.

 

2. Ensure your Joystick is not sending out any "noise" that could result in an autopilot disconnect.

 

3. Lastly, try re-installing SP1c and FS2Crew.

 

Cheers,

  • Author

Hi Rick,

 

1. Check your CVR log to ensure the speech system is not hearing "autopilot off" or any voice command that would disconnect the autopilot.

 

2. Ensure your Joystick is not sending out any "noise" that could result in an autopilot disconnect.

 

3. Lastly, try re-installing SP1c and FS2Crew.

 

Cheers,

 

1. Nothing from me after 'FLAPS 30

 

2. Not exactly sure how to check for Joystick noise, but wouldn't this happen regardless of whether i use Fs2Crew F.O. for my approach or when i just fly without the assistance of Fs2Crew, when things work as they should.

 

3. Already done this twice.

 

4. Stumped on this one.

 

Regards,

Rick Hobbs

Boeing777_Banner_Pilot.jpg

 

  • Commercial Member

Hi Rick,

 

I'm afraid I don't know. Unless you make a voice command FS2Crew doesn't automatically touch anything on the autopilot.

 

Please also ask the PMDG forum or PMDG support.

 

Maybe they have some ideas.

 

Also try clearing all "system failures" via the FMC... maybe you have a failure set.

  • Author

Hi Rick,

 

I'm afraid I don't know. Unless you make a voice command FS2Crew doesn't automatically touch anything on the autopilot.

 

Please also ask the PMDG forum or PMDG support.

 

Maybe they have some ideas.

 

Also try clearing all "system failures" via the FMC... maybe you have a failure set.

Well it turns out the Captain is a dummy. When i re installed SP1C the first time before installing Fs2Crew, it for some reason changed my set-up in my FMC and had the setting to allow GS capture be for LOC. switched it back to 'DENY' and everything works.

 

Regards,

Rick Hobbs

Boeing777_Banner_Pilot.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.