October 15, 2025Oct 15 3 hours ago, thepilot said: You can tell it‘s literally not standard when you have to press a button on the overhead panel for a flaps 3 landing. That's however only the case in the A320 family. The 340-80 don't have that button.
October 15, 2025Oct 15 I find Flaps 3 does improve my landings. Don't know what it is with the Fenix but I am rock steady on the approach but once I'm at around 400', I start to drift laterally and by the time I'm over the threshold I'm often banking, trying to get back on centerline. At that point I touch down and then wildly overcontrol on the rudder (I'm curious what people think about the Fenix rudder - to me it seems way to sensitive). To me, the iFly 737Max is much easier to hand fly (and RL pilots have said the same thing).
October 16, 2025Oct 16 Don't feel bad, I witnessed an airline pilot struggled to land Cessna 172. Yep! His initial training was in Bonanza's and then straight to the right seat of airliner. He never flown 172. Small or big airplane one still have to spend some time to become proficient and discover all bells and whistles that comes with that! Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASELMy System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSDPut my hands on (pic/dual/given)7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22
October 16, 2025Oct 16 According to a real world A32x captain there seems to be a push by Airbus to use F3 as a standard setting for landings. Similarly as to how they recommended starting 2 then 1 (in Europe), which is now reversed and the accepted start sequence is 1 and then 2. He explained the reasoning behind this suggestion but I don't remember what it was. Naturally you'll be coming in hotter than usual so brakes cooling have to be factored into turn-around times. MSI Pro Z690-A DDR4 | i5 13600KF | G.Skill Ripjaws V 32GB 3600MHz | RTX 3080 (12GB) | Samsung 980 M.2 NVMe 500GB | Samsung 980 M.2 NVMe 1TB | Samsung 850EVO 500GB | Crucial P3+ 2TB NVMe | 2TB Seagate HDD | Deepcool AK500 CPU Cooler | Thrustmaster T16000M HOTAS | CH Yoke | Various Winctrl hardware | 21:9 1440p UW monitor | Win 11 23H2 build | MSFS2020 | Tony K.
October 16, 2025Oct 16 2 hours ago, 11bee said: I find Flaps 3 does improve my landings. Don't know what it is with the Fenix but I am rock steady on the approach but once I'm at around 400', I start to drift laterally and by the time I'm over the threshold I'm often banking, trying to get back on centerline. At that point I touch down and then wildly overcontrol on the rudder (I'm curious what people think about the Fenix rudder - to me it seems way to sensitive). To me, the iFly 737Max is much easier to hand fly (and RL pilots have said the same thing). Are you using Realturb by any chance? MSI Pro Z690-A DDR4 | i5 13600KF | G.Skill Ripjaws V 32GB 3600MHz | RTX 3080 (12GB) | Samsung 980 M.2 NVMe 500GB | Samsung 980 M.2 NVMe 1TB | Samsung 850EVO 500GB | Crucial P3+ 2TB NVMe | 2TB Seagate HDD | Deepcool AK500 CPU Cooler | Thrustmaster T16000M HOTAS | CH Yoke | Various Winctrl hardware | 21:9 1440p UW monitor | Win 11 23H2 build | MSFS2020 | Tony K.
October 16, 2025Oct 16 I agree. Had to create a custom AAO elevator sensitivity curve just for this plane to make it manageable.
October 16, 2025Oct 16 19 hours ago, Speedbird 217 said: 200 fpm is perfectly acceptable and not a firm landing. 400+ is when you start getting into trouble. * looks at his Volanta flight history and takes a biiiiiiiiiiig gulp 😬😱 i9-13900K | 6400MHz DDR5 (32GB) | GeForce RTX 4090 24GB MSFS 2024 | PMDG 777-300ER | FBW A380X | Fenix A320 | ini A350
October 16, 2025Oct 16 22 hours ago, Farlis said: Config 3 is standard on ALL Airbus types. You only use flap full when performance necesitates. oh my days Edited October 16, 2025Oct 16 by fluffyflops
October 16, 2025Oct 16 10 hours ago, speedyTC said: According to a real world A32x captain there seems to be a push by Airbus to use F3 as a standard setting for landings. Whatever "push" is to land I'm pretty sure he can handle full flaps landing. Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASELMy System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSDPut my hands on (pic/dual/given)7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22
October 16, 2025Oct 16 A few tips from someone who struggles to get consistent landings with this model, gleaned from when I’ve nailed it: - concentrated practice helps: commit an hour a day to doing a dozen or so, one after the other. FSI Panel makes this achievable and also provides a readout of how far the centreline you land, touchdown FPM and how much runway you’ve consumed. - mentally, you need to focus super-hard from about 100ft AGL and be meticulous in observing the closure rate, as manifested by the ground coming towards you, scanning the full length of the runway and making the most of peripheral vision. - Don’t laugh but with enough practice you find that those fleeting seconds before touchdown seem to expand: you realise that there IS enough time to NOTICE the closure rate and relate it to the inputs you apply to the sidestick. Being able to make “time (seem to) slow down” in this way only comes with experience but it’s crucial imo. - until you develop that level of awareness, it’s hard/ impossible to judge how to “squeeze” the stick from the point of view of timing and also amount of travel in the stick - for this to work best, you do indeed need a linear or near-linear sensitivity curve and minimal dead zone : you are looking for a predictable, smooth response from your inputs in the final seconds - a big monitor also helps: 55” is a different league from 32” and helps massively in training your brain to recognise closure rate/ distance from centreline / approach course - usually, DO NOT commence the flare until you have heard the 30 feet call out - as exceptions to that rule, you might do a tiny “pre-flare” at about 40 feet if you have a tailwind and / or are coming in a bit hot (glance at your descent rate as you cross the threshold: if it’s over 750 fpm you might need a pre-flare) and/or if you’re coming in heavy (eg, I’ve found that if I’m above c61000kg, I’m more likely to want to do a tiny pre-flare) - throttles to idle comes AFTER initiating the flare, never before. As a rule of thumb, expect to snap the throttles to idle as you hear the 20 feet call out - but experience will let you refine this (and everything else!) Edited October 16, 2025Oct 16 by tfm 14900ks, RTX4090, 64Gb@6000-30-36-36-T2, Samsung 990Pro 2Tb , Dell G3223Q 32" 4k Gsync + 27" secondary monitor. Thrustmaster Airbus Edition throttles etc, TPR pedals, MiniCockpit FCU, WinWings FCU, WinWings Orion 2 F15E, WinWings A320 sticks.
October 16, 2025Oct 16 I can't emphasize enough how much shifting your focus to the very end of the runway (even on a screen) helps to judge the flare. A hard landing usually comes from being focussed too close to the windscreen. By adapting to this method I went from averaging 250fpm touchdowns (often higher) to nailing 120-180fpm, in the touchdown zone and on centre. As said above as well, don't be tempted to pull the power off early. Leave the thrust levers where they are (assuming AT is engaged) right up until you hear the retard call at 20ft. Oddly the bigger Airbuses (the A330 and A340) are easier to land softly than the A32x. I don't know if it's the bigger wing or more inertia but those you can give quite big stick inputs and still settle it on nicely. The A32x needs a bit more of a delicate finesse. Edited October 16, 2025Oct 16 by Tom Wright Tom Wright, UK PPL(A) SEP + Night Rating + IMC/IR(R) Microsoft Flight Simulator 2024 | AMD Ryzen 7 7800X3D | 32GB DDR5 6000MHz RAM | 16GB RTX 4080 Super | 2x 2TB Samsung 990 PRO M.2 | Thrustmaster TCA Airbus Sidestick + Quadrant | Logitech G Saitek Pro Flight Rudder Pedals | WinCTRL Airbus FCU + EFIS + MCDU
October 16, 2025Oct 16 1 hour ago, tfm said: a big monitor also helps: 55” is a different league from 32” and helps massively in training your brain to recognise closure rate/ distance from centreline / approach course And VR helps exponentially more than that 55" pancake screen. 😉
October 16, 2025Oct 16 4 hours ago, PlumCrazy said: And VR helps exponentially more than that 55" pancake screen. 😉 Sounds logical! But on the other hand, I like using the WinWings FCU and MCDU to minimise use of the mouse: presumably this is foreclosed with VR? 14900ks, RTX4090, 64Gb@6000-30-36-36-T2, Samsung 990Pro 2Tb , Dell G3223Q 32" 4k Gsync + 27" secondary monitor. Thrustmaster Airbus Edition throttles etc, TPR pedals, MiniCockpit FCU, WinWings FCU, WinWings Orion 2 F15E, WinWings A320 sticks.
October 16, 2025Oct 16 Just be aware, its not necessarily you or the Fenix. The G/S and PAPI are very broken in most airport since MSFS till now. Most times it will bring you much higher than you need to be, so you are coming at an incorrect angle. This makes landing harder. If you will come in the correct angle as supposed to be, you will find flare much easier. Edited October 16, 2025Oct 16 by roi1862 MSFS2020, 24, Fenix A320, Ryzen 9 9950X3D, ASUS TUF RTX 5090 ,G.SKILL 64GB 6000MHz CL28
Create an account or sign in to comment