the MSFS HUD gives an AOA reading, you can turn it on in the settings

Or a VR headset! ;)

Hi, on which landing did I do that? I just reviewed them both and in both cases I pulled the power off just below 20ft, which is normal procedure according to the FCTM.

With all due respect, you make a fool of yourself when you qualify your criticism of an ATP-rated pilot with "I'm not a pilot."

@@A330Driver for example at 17:48 , 15ft RA, your engines are still in CLB detent and start spooling up to maintain speed with your increasing pitch, you move the levers to idle, by 10ft, you still have nearly 60% N1 as the engine begin to spool back. Once the engines drop below 40% N1 and speed starts bleeding off you can see it begin to nicely set down while you are holding pitch. Of course the controls, indications and readouts are not instantaneous. In the first pattern you are as high as 64% N1 as the engines once again started spooling up to maintain Vapp. In your flaps 3 video yesterday, your technique was very similar. It just seems, you are repeatedly putting excessive amounts of energy into the aircraft during flare by going idle after finishing the flare and not taking into account the spool down time of the engines and their thrust output during that time.

@@jrod_pilot_miami Except he's not wrong? He's retarding the throttle after the flare and is surprised to float. In both trials NGDriver does the same tactic, flare then retard the throttles which is going to cause you to float. You're going to get different flaring profiles depending on the point at which you retard the throttles. Due to how the FADEC functions when you go idle, the spool down behaviour is gradual, not instant which is exactly why NGDriver floats everytime. I don't know if this is a habit he picked up from the A330 training or from the 737 but it's a different tactic for the 320.

@@kerrow That's an increase of about 1% N1, that'd hardly have any effect at all, wouldn't you agree? I just recorded a video of the same patternwork, but with the ToLiss, using the exact same technique and it lands just fine of it. So does the FS Labs and for what it's worth the Fly By Wire. 1% N1, which isn't even there for longer than a split second, would not have any noticable effect here. I just confirmed it with an active A320 pilot I know from an earlier beta I was involved in. According to him I could retard the thrust levers a tad earlier, but it shouldn't have any excessive effect as it does in the Fenix. That totally matches my experience on other types as well.

Sure, insights like this are always good to have!

Yes, i would love to see a side by side same pitch on landing to give visual feedback to fenix. Including a sidestick cam in game or something

I think Xplane has a lot to do with the toliss flight model as well. Which is why they are so good.

yea, biggest difference in the handling i've noticed. More dynamic i would say

They flare differently, the A330 goes into more or less direct law at 100ft. However that's not what I based my judgement on for this vid. By now other pilots have confirmed it, like Blackbox711, but I do tend to say I got ample time in all kind of different Airbus Sims, from the A320 full flight sim, to the FSL, to the ToLiss, to my experience working with Aerosoft and loads of A320 pilots on their Airbus flight model back as early as 2014 so that I can spot a flare that doesn't behave as it should. When I first said something it was easy for certain people (who later on said themselves that they aren't happy with the model... Just as a side note) to start shooting at me #notana330. But ultimately look at things how they are now: Fenix made an official statement that Flaps 3 should currently not be used for landing. Then you have plenty of rated A320 pilots who confirm that the FSL and ToLiss Airbusses Land correctly, which implies that the Fenix currently doesn't since they simply Land different. True, I'm not a rated A320 Pilot, so I surely couldn't say whether the FSL or the ToLiss is better. But without being a rated A320 Pilot I can safely say there's something currently wrong. I can spot the gross error, though not the small one.

I couldn't agree with you more, something is missed on the flare. I know a pilot IRL who works for the "orange" and told me that the FSL is the one he thinks is very good, but he doesn't know the Fenix.@@A330Driver

Also tobii head tracker it’s better for those who don’t like flying VR

Try to set your sensitivity to -20 😊

thought so too

TOGA first then "Go around flaps" which is landing config minus one. For flaps full landing, go around flaps is flaps 3

@@MergedSimulations that’s for a go around. For touch and go it’s typically something like bring thrust levers forward about 50%, select flaps 2, when in position then TOGA and rotate at VAPP

For a touch and go Tom is right, it was unplanned and thus I did the go around procedure. Note that it says "when climb is assured retract Flaps" in there for cases where you'll touch down. In my Company we interpret that as "when actually climbing".

On the first landing I let go after the initial flare to see the planes reaction. Normally however you're meant to apply a slowly increasing back pressure as the plane applies automatic nose down input. So in an ideal case you'd see a slow but constant backwards movement of the stick during the flare until touchdown.

Aerodynamics certainly aren't as good as Asobo says and that's something we came across already in the 737 on multiple occasions, including the flare. The good thing though is with a fully automated flight control system like the one on the A320, where there's no direct input from the stick to the control surfaces, developers should be able to correct for limitations in flare behaviour. In the 737 with its direct mechnical connection to the flight controls you have to rely on Asobos flight dynamics (or create an artifical fly by wire hidden to the user), but with an A320 you can actually work around that.

Or maybe artificial reduce the angel elevator can move like FBW have done. Not use the real values so to say. Or reduce the lift elevator can create. Maybe it will change in 2024. At least the Cessna 172 G1000 feels quite good in elevator and flare.

That's a known issue which they plan to fix at a later point.

Hi, I did indeed. Main thing that happened is that since I moved to a new flat I have a smaller desk and now have my joystick standing in the way, blocking the eye trackers view. I still have to find a solution for that.

@@A330Driver Awesome. I use the TrackIR. It's really helpful looking around for runways. :)

Hi, I'm still geathering experience with it, but my initial impression is much nicer than Thrustmaster. Smaller inputs can be done in a much nicer manner. I'll do a full video on the topic in the future, when I have enough experence with the WinWing that I feel comfortable with it.

@@A330Driver thank you very much!

Îf it's basic physics, why doesn't it happen on any other plane? Why doesn't it happen on other A320 simulations? Tomorrow I'll make a video on the ToLiss A320 to show what it looks like with exactly the same flare technique used in here - and you'll see it works perfectly.

Except 320SimPilot has a higher tailwind on landing while also a lower AoA during the flare. The technique and circumstances applies by 320SimPilot are not being replicated by NGDriver. I didn’t look but I’m going to guess GW was also higher.

@@TheSAfreak A higher tailwind would actually be a reason to retard earlier, not later, as you want to prevent the plane from floating in that situation.

@@animatedchristmascollector3754 Where would it say that in the book though? Can you give me a quote or a page?

What line?

Once they get the approach attitudes right things will improve instantly. I'm experimenting with deliberately flying it too slow now in order to get the target pitch.

tried it on the toliss and you're right, there's defiantly something going on in the fenix on landing. kzfaq.info/get/bejne/jcWZiqqTtJOop5c.html

@jacobwiqvist1760 Maybe due to the fact that in this video pilot did not wait for "retard" call and moved leavers all the way back at 30ft.

Try the same in other Addons like the Toliss or FSLabs and you'll see the throttles aren't the problem. Or at least they shouldn't be. Also it says nowhere in the A320 documentation to IDLE at 30ft, but rather around 20 as I did.

@@A330Driver The A320 FCTM explains that the flight crew can rapidly retard all thrust levers to IDLE either earlier or later than the 20 ft “RETARD” auto callout reminder depending on the conditions. However, the thrust levers should be at IDLE by touchdown to ensure that the ground spoilers will extend and keep the aircraft on the ground. - from airbus safety first page - tried linking here but comment was removed

Haha, to be honest I'm quite happy with the A330, I probably would not even want to trade it for a 777 😅😂

So you wouldnt traid a computer with wings, for a airplane with a computer in it? 😅 Just kidding... They are both lovely birds. But please tell me you will make T7 content when it's finally here 😳

@@matness8879 Ooh that would be so cool. Looking forword to the 777!