It has been at least 4 years since Aerosoft stated that their Airbus A330 series would come to Microsoft Flight Simulator. In that time, hundreds of add-ons have been released, and even a brand-new version of the simulator has been announced. The landscape of the simulation world has shifted massively since Aerosoft’s original announcement, including the news that an A330 will be included as part of the standard edition of MSFS 2024.
This is a written version of our first flight video – which you can watch here.
So, when my emails pinged whilst I was out having lunch on Friday I saw the subject “A330 CEO Base Pack – Your personal key!” I was very surprised. Aerosoft’s team gave me, along with others, a copy of the plane with the news that it would be available on October 7th, 2024. I rushed home, installed and was ready to fly the plane that had been years in the making.
A bit of context before we jump into this first look. Firstly, this is version 1.0.0rc2, meaning that it’s a release candidate. There may be some quirks here and there, but for the most part, this is considered a near-final build. Secondly, Aerosoft didn’t give us much information to work on – no indication of what bugs may be present, what will be implemented for the final release, etc. With Frankfurt, Aerosoft gave us that detail, so it was a little surprising not to find it here.
All that aside, let’s take a look at the Aerosoft A330 on one of my first flights from the Dominican Republic (Puerto Plata Airport – MDPP) and Puerto Rico (Mercedita Airport – TJPS).

What immediately struck me was just how nice the visual model is. Panning around the external model, I loved the intricate detail. The gear itself was full of details like the hydraulic lines, whilst the cargo bay was full of little details like placards and decals. Speaking of the decals, throughout the external model, they are detailed even up close meaning you can read even the danger signs. Stepping inside to view the virtual cabin, though… let’s just say it’s bare bones. Very bare bones.

But redeeming that is the cockpit, with its true Airbus-blue tones throughout. The modeling is really nicely done and, again, the texture work is crisp and clear. The displays were rendered to a good resolution, with you being able to get really close to the screens and still easily read the displays. Some parts like the tray tables and windows are animated, but it’s pretty basic compared to what we see from other add-ons these days in MSFS.




The onboard EFB, even with a few minor issues, is one of the nicer parts of the plane. It has a pretty modern-looking UI, it is pretty fast and has many features you would expect to find in an EFB. There are some changes I would make (e.g. a specific tab for performance), but once you find your way around, it works well. You can add your SimBrief profile, adjust settings, control your doors, and more. However, when trying to connect the ground power unit when running GSX, something was borked so the GPU would never connect and would stay ‘pending’ yellow.




During the process of loading my plane, my internet connection dropped without me realising. I clicked the import SimBrief button on the EFB and it endlessly spun searching for it. No timeout message or anything. I therefore had to reset my flight in order to reset the EFB. A little bit of an unusual problem, but frustrating all the same and something I do fear is too commo for some. One thing I did notice, semi-related, is how there is a full ATSU page, but when you click on an item, it says NOT IMPLEMENTED. Something I soon would find out happens quite a bit. More on that later.
[Editor’s note: When content creators/media got this preview build prior to release, no notes on the INOP functions were given until hours before release].
With the plane now loaded, I used the automatic import tools to load my fuel and payload. You can also run some performance calculations on the EFB, which is a nice touch and is easy to do. With that now done, and performance added to the MCDU, I was ready to push and start. I will commend Aerosoft for the sounds on this plane. The iconic engines in the A330 are here in their full glory and start-up was just delightful.
Moving the aircraft required quite a lot of thrust input. Considering most of my flights were light, it felt unnatural to put in as much energy as I was, but that said, we were underway. Taxiing felt fine with my tiller controls on my separate control input and I was able to keep the aircraft’s momentum up once I did gather speed. Taking off sounded great, but you could tell she was slow to reach her take-off speeds.




Most of the bugs or problems on the ground are mild inconveniences. It’s not ideal, but far from being detrimental to the experience. Once airborne, that changes. Following the initial climb out, I began approaching the first turn on the SID. My aircraft just flew right over the waypoint before then starting the turn. This then meant you completely overshot the turn on the ND causing the plane to S-turn back and forth to get back on track. Thinking maybe it was just this specific departure out of the Dominican Republic, I kept my eye on further waypoints en route. The same thing happened again, again, and again. Even at cruise with light winds. If you are flying a specific approach or get instructions from an online network to proceed directly to a waypoint, this will cause you serious problems.

Wobbles aside, I continued with my flight experimenting with other functions in the MCDU. Now for me, here’s my biggest gripe with the plane. I am completely aware that this plane is designed for A-B flying, and that is fine. But one function, I feel is crucial to any simulation of a modern jetliner is the use of HOLDs. If you’re flying online, your controller will expect you to be able to hold at any waypoint. I mentioned earlier the dreaded ‘NOT IMPLEMENTED’ and low-and-behold, I witness it when I try to enter HOLD data. Seriously!?
I will change the above if on Oct 7th it is implemented, but without communication from Aerosoft at all (it’s Sunday at 12:05pm), I’m unsure if this will be the case. If this is the release build, VATSIM/IVAO controllers you had better watch out.
Other issues I noticed on my flights included the aircraft overspeeding when on the descent, no deceleration point on your MCDU/ND, and the plane not telling you to add drag when you clearly need it. Then when you add it to maintain the descent profile, it tells you to put the speed brakes away. What happens when you do that..? You approach the overspeed markers again. You really need to manage your speed because it is a slippery plane.

Using the DCT functionality also gave me weird issues. It would initially induce a micro-stutter in the simulator, and start banking the wrong way before correcting itself and flying to the new waypoint. Again, I’ve had limited time with this, but I had this happen a handful of times in my first few flights.
My approach to Puerto Rico is the RNAV to runway 12. Not really filled with confidence at this point, but I figured I would continue. Now, when I selected the approach mode in the MCDU, the speed indicator changed and the plane decelerated. Not only that, but the appropriate markers appeared on the PFD to indicate the RNAV approach. The issue, though, was that regardless of my altitude or lateral profile, the plane said I was on target. For whatever reason, I put my faith into the system and when I took a glance outside, I was still at 5,000ft and about 10nm from the runway. Yikes, time to circle and try that again.
If this sounds like some sort of comedic experience, and I’m making this all up, you can watch the video of the flight I did that shows this all off. But it gets funnier…
On three occasions, I had landing gear issues where by using the gear lever in the cockpit. Simply put, the gear didn’t come down. The animation worked, but the gear didn’t come out. Pressing G did work, but that’s far from the point. There’s a running joke within FSElite that I am notorious for not putting down my gear in time (it happened once on a group flight and I’ll never live it down), but this most certainly wasn’t user error!

I am okay with bugs being present in a product when it’s first released. There’s only so much testing that can be done and there will always be some kind of weird edge case that only happens in certain situations. In my example of the gear, anyone else I’ve spoken to has not encountered this issue, but I have multiple times.
Flying the plane on finals felt pretty nice, if a bit too light on the controls. I will say that the aircraft kept having thrust fluctuations on the final 5 miles. It meant that as I entered the final few hundred feet the engines were spooling up, meaning I had to retard them sooner in order to bleed off the speed. On touchdown, the sounds were the saving grace and it put a smile back on my face after a disastrous approach.
So what now? Where does Aerosoft go from here?



It’s hard to say. I am a firm believer in that products need to be looked at in an as-in state, not what is promised in the future. That future may or may not happen and this product is available to purchase. My immediate impression is that this has been pushed to get it out before Microsoft Flight Simulator 2024 hits the market next month. The A330 included in MSFS 2024 and developed by iniBuilds is seemingly giving Aerosoft some pause for thought and trying to get this into the hands of simmers now.
I don’t believe rushing this right now to market is a wise move if that is the fear. We have seen plenty of examples where even if something is part of the base sim, there is still a huge market for those wanting something better, fancier, or with more fidelity. We haven’t seen what the base A330 will be like in MSFS 2024 yet (not even me who was at the Global Preview Event), so it’s not exactly easy to say how they will compare.
What I can say is that in the state this build is in, this plane is a nightmare. I had such high hopes that despite the murky development period this plane has had, Aerosoft would surprise us all. I am disappointed that this is the result of 4 years, multiple project managers and countless delays. What was supposed to be a crowning achievement has left me underwhelmed and fearful that this aircraft will never see the improvements it so desperately needs.

Additional Info:
Whilst I never experienced it myself, other people who have access to the planes also said that the following happened to them:
- WASM crashes when changing panel states (and other scenarios)
- ILS issues on the glide path
- Plane falling out of the sky after hitting an invisible wall when changing weather (in fact, it goes nuts)
At the time of writing, this is from version 1.0.0rc2 and a statement was shared saying “I don’t think a lot is going to change from now until Monday.” If anything is fixed or updated, we will update the article accordingly.
If you want to watch my video on this experience, you can do so below.






