Four ways the Airbus might catch you out.

[@gelb-und-schwarz]

Thank you for the very useful insights! Since the time is slowly approaching, I believe a video on cold weather and winter ops would be very interesting.

[@fsclips]

@@gelb-und-schwarz Already done it. 😉 You can find it in this playlist

[@gelb-und-schwarz]

@@fsclips This was a great video (that I probably have to rewatch), I was referring more to the things you did not mention there, like fluid types, procedures when de-icing etc. Even though they are not simulated, I believe it's an interesting topic and who knows, maybe they will be simulated in MSFS2024! Nevertheless, keep up the great work, the community really needs these insights!

[@Ms12Rock]

I really love and enjoy reading the Airbus Safety First so much. It is very detailed. Glad to see it being visualized by you. Thank you!

[@yooturboo]

The goat has dropped another one 🔥

[@Aviationishere]

Love the infos, thank you so much!

[@hansson2723]

Thank you so much, very informative and interesting video as always. And also good to have such aircraft like fenix)

[@ProfessorJohnB]

Very cool! I have had all of these situations one time or another with the Fenix A320. Now I know why they occurred. I am so impressed that the Fenix is programmed so realistically. A big shout to them. And a huge thank you to you! I learn something important with every video.

[@iiBus]

7:49 I've done this a few times (in game) and then occasionally realized only after executing a missed approach..

[@ehrendudus9607]

Great video with infos about what to watch out for! Actually didn't know the phrase to catch out yet. Very nice

[@ItsLafar]

Wooow, what a video, I didn't know any of this things! Thank you so much for the insight, it really helps getting to know a little bit better our beloved Airbus!

[@sinicodaniel]

Cool! 😊

[@pong_sim]

amazing video!!❤

[@A32NPilot]

beautiful

[@christianseefu5944]

im a huge fan of changing managed speed in the DES Perfpage depending on where i fly into and the inbound traffic situation. usually a bit slower (270-290kts on conversion) when heading somewhere with a steep approachpath to have more headroom for controlling your descent without the need to use excessive speedbrakes. A bit faster (290-310kts on conversion) when flying into more dense traffic airports where i expect to get vectors, so atc can slot me in easier and i can ask for est trackmiles.

[@peteallennh]

Thank you for covering these gotchas! I was flying to Chicago recently and got vectored to final. I encountered the exact problem that you demonstrated. Even though I was able to get back into APPR mode, every time I set managed speed the plane would start speeding up and ruin my VLS. I was able to land by manually setting speed, but I am clearly doing something wrong when it comes to vectored approaches. Perhaps you could provide a more in-depth explanation of this crucial situation.

[@fsclips]

If you go into managed speed and the plane speeds up that probably means you haven´t activated the approach phase in which case the plane will accelerate to 250kts. The second possibility is that you are flying to slow for the current flap setting. Make sure the approach phase is active before manging speed on approach. Hope this helps

[@bakhtyarzafar4208]

Means excellent) 😉

[@iPatrickDesign]

About the 3rd scenario and the original configuration which you have started with. I thought that in that case if you push LOC (or APP but now let's just assume LOC), the aircraft will continue forward and turn onto the LOC the right direction and ignoring lingering waypoints like that one in the example, is that not the case, or did I miss something? In the sim I used LOC many times before for technically a shortcut of DIR+course. Was I just lucky all the time? :D

[@fsclips]

yes, you could fly the approach with a To-waypoint behind you, but this is not done in the real world because in case of go around you have no guidance. In order for the Bus to guide you through the go-around the waypoints not to be flown one by one. Airbus has actually addressed this now. On our sharklet and NEOs if you initiate a go-around and you fly past the runway the aircraft will automatically sequence the flight plan and therefore fly the go around procedure. However, this is not implemented in the Fenix A320.

[@iPatrickDesign]

@@fsclips Very interesting. Thank you for sharing us these interesting details! Love your channel!

[@Xtr3m3Sp00f3r]

in the last case is it wrong to just use the speedbrakes? i'm only a gamer and played msfs a bit, so not a pilot, but in my mind if we are so high and need to descend so fast it is not only a problem of the high cost index but planning mistake, so a little bit of speed brake would allow for a slower steep descent right? since you want to achieve FL150 by a waypoint and the thrust was already idle so the plane could not achieve a slower airspeed without affecting the rate of descent, busting the required altitude at the required waypoint.

[@fsclips]

Yes, of course the speedbrakes are one of the tools that you can use in this case, but the autopilot would still fly right at the max speed, so I would combine it with a selected speed.

[@ilkerismail1690]

⁠​⁠​⁠@@fsclipsor simply OP DES because the actual managed speed will be followed without the tolerance band and it will never be higher and probably be even less than (in this situation/approximate altitude) 340kt since that is even the limit in case you have a expedite button (“EXPED”) in your FCU which is specifically there to max things out, but its use is certainly discouraged. You can accomplish the same by selecting 340kt and pulling for open descent, speed brake is allowed for sure. But full speed brake deflection is actually only possible if you go manual flight in the Airbus logic (as a pure precaution), so in an emergency (a scenario which I cannot think of right now) you would (even as a flight sim pilot, quite instinctively) disengage A/THR, AP, FDs, engage TRK/FPA to get a visual reference on the PFD of how steep your descent is in terms of angle by using the “bird”, maybe activate “terrain on ND” display mode and fly towards Vmo. You can even exceed it slightly, but at some point (in normal law, that is) some protection mode will counteract that by automatically pulling up (which may in turn be harmful to your desired “falling brick” profile). But beware you will intermittently be in access of ROD limits that guarantee a fully functional TCAS operation (around ca. -6000/7000fpm) and overall experience nuisance (e.g. GPWS) alerts. It is like a terrain escape manoeuvre, just the other way around… well upsidedown mountains don’t exist, but think of “volcanic ash encounters”, for which you as a pilot are simulator trained or something similar, combined with IMC, busy traffic and an ATC instruction to descent as fast as you can, and doing so safely is very difficult if you have the typical energy situation of an airliner! You can’t simply fly into a stall and controlled spin like an aerobatic aircraft and not descent on the spot like a helicopter either. Also it’s very stressful if the crew cannot accurately judge the elevation of terrain surrounding them (loss of GPS signal or whatever) but still has a very urgent reason to lose altitude. For long stretches of cruise flight above mountain ranges with far away suitable landing sights terrain escape routes are planned beforehand, but that is rather tailored for explosive decompression events at cruise with subsequent descents down to (at least) the FL100-FL140 block of altitude. But that would rarely require descents that require the pilots to exceed any airframe limits and probably even require them to keep a more sensible vertical speed until notifying ATC or being established on the particular mountainous terrain escape route (alignment turns, slight deroutes, directs, offsets, thunderstorms in the way) given the high values of the various types of minimum altitudes (MEA, MSA, MGA, MEF, MTCA, (grid) MORA, MOCA… have I forgotten anything? Not a real pilot, so i don’t have to know which one is most limiting here hehe :D) which can be bust quickly.