Airbus A320 MCDU Setup Manual Setup and Simbrief

In this Microsoft Flight Simulator video, we setup the MCDU in the FlyByWire A32nx for a flight from Gatwick to Munich using a flightplan generated in Simbrief, we use the Simbrief integration feature for the A32nx and then we setup the MCDU again doing everything manually for those of you who don't use Simbrief.

Use the link for an extra 10% discount over and above their current promotions!!

Check out my A32nx tutorials here:

Join us on Discord:https:

If you enjoy this video please give us a thumbs up and then subscribe here:

Join this channel to get access to perks:

Also if it has helped you in any way please consider buying me a coffee at:
Your support is truly appreciated.

Social Media:
TWITTER:
INSTAGRAM:
DISCORD:

#A32nx #MicrosoftFlightSimulator #flybywire #FS2020 #airbus #A320neo #beginner #turorial

[Airbus_AAX]

Amazing tutorial! I recommended it to my beginner cousin too and he loved it too! Super simple and easy to understand if you know the basics.

[janwrede]

I just finished the MCC course on the A320, FI was an A320 examiner and we actually used to feed it with the calculated trim by typing "up" or "dn" directly followed by the value for instance "UP1.2".
So when rotating the pitch trim is already where it should be, from there on autotrim managed the trim of course.

[henrikolsen]

Tip: Use Airport key to jump to DEST in flight plan. Saves some scrolling.

[DP-xzxr]

Recently discovered your channel and decided it was time to download the a320 and replicate your flight from Manchester. Absolutely loved it and lost a whole weekend trying to get my head around this fabulous plane.

One thing that totally confused me though was the Navigraph chats. Not so much reading them, but just how you flicked around all the different types of charts and screens! Be awesome if you could walk through SimBrief and Navigraph charts a little and how to use them in your flying. Awesome job though. I’m going to replicate this particular MCDU setup over the coming days!! ❤

[aliumohammednurudeen]

Thank you very much, I appreciate the MCDU tutorial

[aceforexacademy]

Thank you for making it simple - I wanted to up my game in the sim 👌👌

[roblindsay]

Another great video but I did notice you changed the takeoff runway. I was following along so I set my flight plan up as I saw it in your simbrief plan. Not a big deal but just thought I would mention it. I really learned a lot so thanks for that.

[paulmason]

Thanks for the great video/update. The FBW set up changes so often it's so helpful you do these videos. Thanks once again

[StoryTime.vm]

Thx for makeing it simple and it helped Me so much

[pascalbangratz]

Thank you very much. I learned a lot of things and will implement them.

[raywalsh]

Nice clear explanation, thanks. I needed that refresher guide !

[chrisgoddard]

Brilliant for someone learning this - thanks

[dr.aviator]

Once again. Thanks a lot sir! You’re my guy!

[gmdmango]

great video! quick question though:
when you completed the mcdu with the simbrief integration, it gave you the altitudes and speeds for all of the waypoints, however when you did it manually, i didnt see them. do they also have to be filled in manually?

[adonisaseem]

Thanks. Please also create a video explaining how to select STAR.. what VIA and TRANS to select. Another question, if you messed up flight plan on MCDU, how to clear current plan and re-fetch from simbrief?

[Topcat]

Appreciate the review. It helped confirm the process in my mind from your earlier version, and those of others.
One question that perplexes me: I set up a flight in SimBrief from KBWI to KPIT. On the STAR of runway 10L at Pittsburgh (DEMME 5), there is an altitude constraint of 10, 000 feet at NESTO which shows correctly in the MCDU. However, when I look at the next waypoint in the STAR (DEMME) the MCDU still shows my initial cruising altitude of FL250 (25000). It does not show the next constraint waypoint (GRUNZ). It also has a constraint of 60000. I would have exxpected to see it listed. The next waypoint in PENGN which, again, shows the FL250 altitude. I am confused. I thought that if the MCDU indicates a lower altitude (such as the 10, 000 at NESTO) it should show the same altitude at the next waypoint, not the initial cruise altitude. I am also confused why GRUNZ and its >6k altitude constraint did not show at all. I do have a Navigraph subscription and using the correct AIRNC in SImBrief and the sim.
My concern is whether this behavior will mess up my descents during the STAR phase of the flight as well at the ILS approach.
Any ideas why this might happen? Or do I just have to manually "correct" the inerrent altitudes in the MCDU before I begin the flight? Or do I just ignore and use Selected altitudes instead of Managed?
Many thanks.

[leerose]

What a great video ! Really helpful ! Thank You 👍🙏🏻✈️👨‍✈️

[FredrickII]

Excellent primer on programming the MCDU. I followed along in FlightSim and tried to enter the information exactly as you did. Everything was working great except that at around 18:20 you jumped back into the MCDU from Navigraph and seemed to start DIFSRIP from scratch. Is this an alternate route?

[RomanVideos]

Is there a way to insert flaps for approach? I only noticed i can do that just for take off. There is such option on a310 by the way

[leonardwebber]

thank you its working now /just subscribed