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.

FBW A320 + latest beta

Featured Replies

Hi Bryan,

I have set the videos to Public and reposted them here together with my own video of Go Around without FS2Crew:  

Easyjetsimpilot (Real World A320 pilot) Go Around video             Go Around with FS2Crew                 My own video of Go Around without FS2Crew 

The 'with FS2Crew video' clearly shows that FS2Crew is disengaging the autopilot on Go Around.

This is a copy of the GA page from an actual A320 Manual - A320 Manual - GA Page provided by an A320 Pilot on FBW Discord

He has also confirmed that 'Neither APs need to be engaged to do a go around as you can do one manually, but you can do with just AP1 engaged'

Hope this helps 🙂

                        

 

Edited by Glyn907

  • Replies 54
  • Views 4.6k
  • Created
  • Last Reply
  • Commercial Member

Code wise, when Go Around is triggered in FS2Crew, all the FO does is raise the flaps one notch, then the FO will say "Positive Climb" when positive rate established.  We're not shutting off the autopilot.

If you're using a hotkey for the "Secondary" command used to trigger Go Around, ensure that the hotkey command is not shared with the autopilot disconnect button.


Let me know if the secondary button assignment offers a clue.

 

Hi, have checked that already and it is not shared

Yes that is heard. You can hear it on the video with FS2Crew and a second or so later AP1 disconnects. Will you keep me in the loop please about the outcome? If you want me to do any more checks I am happy to do so 🙂

No. With AP1 engaged and by carrying out the laid down GA procedure there is no need to touch the stick

Glyn & Bryan,

I attempted to reproduce this issue by simulating the same approach into Manchester runway 23R, as Glyn had shown in the video.

I am not having the issue with the AP turning off during the Go Around procedure.  

 

AP1 only was on during approach (No AP2 autoland).

  1. At minimums called for Go Around Flaps
  2. Manually moved throttles to TOGA
  3. FO moved the flaps up one notch
  4. Called for landing gear up
  5. Aircraft leveled and accelerated to climb
  6. Throttles to LVR CLB
  7. Climbed to missed approach altitude and leveled off

Sidestick was not moved during the procedure.

The Go Around process in FS2Crew operated perfectly and I followed the missed approach path for another landing attempt, successful.

Result:  AP1 remained on the entire missed approach procedure. 

Glyn, I cannot reproduce this.  What was different in your steps, if anything?   What hardware are you using for throttles?

 

Steve

 

Hi Steve,  That's interesting.  Did you watch the videos I posted which showed what happened to me? I have the Thrustmaster TCA Officer Pack Airbus Edition.

I actually moved the flaps myself not the FO.  I wonder if that is the issue? I will give it another go now and let FS2Crew move the flaps and post the video. 

You said FO moved flaps up one notch. Is this done automatically by Fs2Crew or do you have to press the main FS2Crew key? I am using button control.

Appreciate your input  

Edited by Glyn907

Hi Steve/Bryan, I carried out another approach to EGCC Rwy 23R and the result is exactly the same as before.  I followed your guidance but autopilot still cut out. See video Go Around Test

Edited by Glyn907

  • Commercial Member

At Go around, you'll call "Go Around Flaps" as the PF.

The FO / PM wil retract the flaps one notch.

However, if you're using hardware, obviously the FS2Crew FO can't retract the flap handle on your hardware.

 

Are you pressing the "Secondary" button when triggering the G/A?

 

H Bryan,  I am using button control and press the secondary button to select GA. That is when the autopilot disengages. During the flights with FS2Crew I follow the checklist and select the main key to allow the FO to select the flap position etc when required. 

The issue is as soon as I select GS by pressing the secondary button and select TOGA the autopilot disengages.

Edited by Glyn907

I'm using Voice Control so there is a difference there, no other hardware inputs from me other than pushing the throttles to TOGA manually and then back to LVR CLB.  I am using the Thrustmaster TCA pack as well.

The FO moves the flaps up one notch, from Full to Flaps 3.  

Do your hardware bindings for the GA and TOGA have any other flight control selections, such as trim?  

 

Steve

Archived

This topic is now archived and is closed to further replies.

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.