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.

Fenix Update Released

Featured Replies

  • Commercial Member
28 minutes ago, threegreen said:

reason for the automatic nose down inputs

“Consequently, to flare the aircraft, a gentle nose-up action by the pilot is required.”
by FCOM .

A Flight By Wire mind trick. 

  • Replies 131
  • Views 20.8k
  • Created
  • Last Reply
  • Commercial Member
45 minutes ago, threegreen said:

@Aamir or @Tom_L What's the reason for the automatic nose down inputs anyway? To counter float tendencies?

Pilots are taught from day 1 that during flare you're supposed to have some form of consistent backpressure on the stick, whereas in full normal law you would not have to do this, you would pitch the nose up and it would more or less stay there. This is quite unnatural to someone coming out of any other conventional airplane, so the Airbus forces you to do this too, it's a "fix" to the unnatural behaviour you can see in normal law, during the landing phase. Aircraft usually pitch down as they enter ground effect too. Interestingly, the A321Neo first had modified flare law, at 100RA with a pitch down input at 50RA instead of 50RA and 30RA, and then they further revised it to actually remove the nose down tendency just on that aircraft because it seemed to do it on its own due to the characteristics of the airframe. Frankly, I find it a dark art, all this stuff. 

Aamir Thacker

737Driver is a bore. Humourless, nitpicking and dull. Maybe it's the 18 hours a day he spends obsessively churning out YouTube videos that prevents him from actually getting any enjoyment from using the sim? I simply couldn't care less about what he thinks about the Fenix. I love it!

Edited by jarmstro

1 hour ago, Aamir said:

Pilots are taught from day 1 that during flare you're supposed to have some form of consistent backpressure on the stick, whereas in full normal law you would not have to do this, you would pitch the nose up and it would more or less stay there. This is quite unnatural to someone coming out of any other conventional airplane, so the Airbus forces you to do this too, it's a "fix" to the unnatural behaviour you can see in normal law, during the landing phase. Aircraft usually pitch down as they enter ground effect too. Interestingly, the A321Neo first had modified flare law, at 100RA with a pitch down input at 50RA instead of 50RA and 30RA, and then they further revised it to actually remove the nose down tendency just on that aircraft because it seemed to do it on its own due to the characteristics of the airframe. Frankly, I find it a dark art, all this stuff. 

I was suspecting it was to make it behave like it's supposed to or expected to when it otherwise wouldn't.

This reminds me a lot of MCAS in the 737 MAX, actually. Instead of steadily increasing back pressure on the yoke all the way until full deflection to keep the nose rising until stall you would have to release pressure on the yoke at some point to keep a consistent increase in AoA because the aircraft starts pitching up on its own at very high (abnormally high) AoAs due to the lift from the bigger engine nacelles. So MCAS cancels out that tendency by the use of trim so that the pilot has a force to work against and make it fly conventionally in that situation.

Apart from what you said, the A321neo also has an inherent tendency to go nose up very quickly at certain weights during a go around, so Airbus added some dark art here too to make that pitch up trap go away by having the FBW counter it.

This is all pretty much the same stuff; having software make up for or enhance for airframe characteristics.

29 minutes ago, jarmstro said:

I simply couldn't care less about what he thinks about the Fenix. I love it!

Then why are you here attacking him again?

5 minutes ago, threegreen said:

Then why are you here attacking him again?

Attack? Ahh.. I see what you mean. Nowadays words are physical violence.😀

Just now, jarmstro said:

Attack? Ahh.. I see what you mean. Nowadays words are physical violence.😀

Erm... right, whatever floats your boat.

O prefer to watch these forums, as to watching Days of our Lives. TBH i don't know which is more entertaining.

Mike

Intel 12700k No over clocking 32GB G-Skill 3600 Ram MSI RTX3080

 

9 minutes ago, Riah069 said:

Days of our Lives

OMG is that still running.

Yeah it is LOL

Mike

Intel 12700k No over clocking 32GB G-Skill 3600 Ram MSI RTX3080

 

Perspective from a Real A320 pilot. 

 

I didn't get anything from briefly skipping through that video other than the pitch is flat and he needs more testing. I also haven't flown with the latest update yet, so how is it with regards to floating? I've always felt like it needs just a tiny tap of backstick to flare, otherwise I constantly end up floating down the runway. I've set up my stick according to Fenix's recommendation for a VKB and it feels good. Watching them A320s land at work there is a good amount of pitching up in the flare and there's still no floating, but for some reason I end up floating with just a small pitch increase in the Fenix.

Coming from a real world A320 Captain (V1 Simulations) posted in his Discord. 

"He thinks the new flare etc is pretty good. He believes the problem actually lies with the glides slopes being mis-aligned and papis being stupid to follow. These anomalies cause the pilot to react this way and "destablizing" the aircraft. More often than not this leads to a nose low or low pitch across the numbers, throwing the flare feeling "off"  but not necessarily wrong." You can find the rest of what he says on the discord or the stream where he did test the new model. 

Judging by what he is saying I take it he finds it more realistic now. 

Edited by carlanthony24

5 hours ago, jarmstro said:

737Driver is a bore. Humourless, nitpicking and dull. Maybe it's the 18 hours a day he spends obsessively churning out YouTube videos that prevents him from actually getting any enjoyment from using the sim? I simply couldn't care less about what he thinks about the Fenix. I love it!

He clearly believes in quantity before quality. 

// 5800X3D // RTX 3090 // 64GB RAM // HP REVERB G2 //

Ignoring the ILS / Glideslope and PAPI inaccuracies, and with me not being a real pilot and kind of word not allowed about what I am about to say...  :laugh:  Which runway markings should we be aiming for to touch with the main gear?

I always thought when people said the 'piano keys', they meant the numerous white stripes right at the end of the runway, but I have come to realise that comes with a serious risk of 'under-shooting'.

Does anyone have a diagram?  I tend to think now that it should be the two thick white blocks.  That would seem to be about right but I am not sure.

I still can't wait to try this bird when I am up and running again.  I know Fenix will keep tweaking it in, with the improved flaps 3 setting they are working on etc.  It is also good to hear the feedback / communication from Aamir - takes the guesswork out of it! :smile:

Edited by bobcat999

Rob (but call me Bob or Rob, I don't mind).

I like to trick airline passengers into thinking I have my own swimming pool in my back yard by painting a large blue rectangle on my patio.

Intel 14900K in a Z790 motherboard with water cooling, RTX 4080, 32 GB 6000 CL30 DDR5 RAM, W11 and MSFS on Samsung 980 Pro NVME SSD's.  Core Isolation Off, Game Mode Off.

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.