Hey guys,

Huge fan of what you’ve built bringing Airbuses into MSFS! I did want to mention a bug I’ve noticed regarding Flaps behavior on everything from the A320 to the A380.

I’ve seen this issue since the A350 in MSFS20, and it’s still happening in MSFS24 on the A350 and A380 (I usually depart using Config 2 on IniBuilds jets). See the picture below:

Whenever you set Config 1, the plane defaults to Config 1+F instead of standard Config 1. During heavy takeoffs or direct Config 1 departures, this drives S-speed way past flap retraction speed and right up against VFE. It happens on approach/landing too. Looking at the FCOM snippets for ARS and AES below:

• Picture 1: Automatic Retraction System (ARS) ===>

• Picture 2: Automatic Extension System (AES) ========>>

It mentions 'When Needed', so when is 'when needed' actually supposed to apply? For this context, we refer back to A320 FCOM:

=> =>

Looking at the green highlights and diagrams, 100 knots is basically the boundary. During acceleration at acceleration altitude, Config 1 behaves in two ways:

1. Taking off in Config 1 engages 1+F, which ARS then retracts to pure Config 1 as speed approaches VFE. OR

2. Taking off in Config 2 or 3 and retracting to Config 1 sets standard Config 1 right away (not 1+F) because ARS sees speed is already above 100 knots.

So how do you actually get 1+F in-flight after Takeoff, Holding and Approach? It requires two things:

1. Selected or constrained speed is below VFE, AND

2. You recycle the flap lever from Flaps 1 to 2 and back to 1.

This applies across the entire Airbus family, all the way from the A318 to the A380. Getting this flap logic simulated accurately would make flying these jets in MSFS so much more realistic and enjoyable!

Thank you for your attention, guys. Cheers 🍻

HaveASafeFlight!!

Edited 2 hours ago2 hr by OxkyGThaib

2 minutes ago, OxkyGThaib said:

Hey guys,

Huge fan of what you’ve built bringing Airbuses into MSFS! I did want to mention a bug I’ve noticed regarding Flaps behavior on everything from the A320 to the A380.

I’ve seen this issue since the A350 in MSFS20, and it’s still happening in MSFS24 on the A350 and A380 (I usually depart using Config 2 on IniBuilds jets). See the picture below:

Whenever you set Config 1, the plane defaults to Config 1+F instead of standard Config 1. During heavy takeoffs or direct Config 1 departures, this drives S-speed way past flap retraction speed and right up against VFE. It happens on approach/landing too. Looking at the FCOM snippets for ARS and AES below:

• Picture 1: Automatic Retraction System (ARS) ===>

• Picture 2: Automatic Extension System (AES) ========>>

It mentions 'When Needed', so when is 'when needed' actually supposed to apply? For this context, we refer back to A320 FCOM:

=> =>

Looking at the green highlights and diagrams, 100 knots is basically the boundary. During acceleration at acceleration altitude, Config 1 behaves in two ways:

1. Taking off in Config 1 engages 1+F, which ARS then retracts to pure Config 1 as speed approaches VFE. OR

2. Taking off in Config 2 or 3 and retracting to Config 1 sets standard Config 1 right away (not 1+F) because ARS sees speed is already above 100 knots.

So how do you actually get 1+F in-flight after Takeoff, Holding and Approach? It requires two things:

1. Selected or constrained speed is below VFE, AND

2. You recycle the flap lever from Flaps 1 to 2 and back to 1.

This applies across the entire Airbus family, all the way from the A318 to the A380. Getting this flap logic simulated accurately would make flying these jets in MSFS so much more realistic and enjoyable!

Thank you for your attention, guys. Cheers 🍻

HaveASafeFlight!!

Thank you as always for the detailed report!

I will log this with the team to review.

Appreciate your continued support!