Other

My aircraft enters a roll on its own (reaching a significant bank angle) as soon as I take control. The problem isn't the sidestick; I’ve never experienced this with other aircraft

Hello, After each startup of my MSFS2020, I need to rescan the QR code to enable the connection with Navigraph. Is this normal???? Regards, Eric

Everything went perfectly until just before landing. Even captured the ILS how I expected it to after reading up on it. The main issue was that the AP wouldn't shut off so I could land manually. Autoland worked perfectly, then the FMS crashed. But other than that, my first flight went great. It's a beautiful aircraft!

Good day everyone, i really enjoy this aircraft, but non the less I unfortunately experience some bugs. The first bug I’ve encountered are my flaps. The flaps extend and retract normally during taxiout, takeoff and climb. During approach, my slats are extending as they should, but my flaps are visually stuck into the “0“ position. After rollout while retracting the flaps, they move to position „4“, but not shown as it in the status page. The second bug is the more frustrating. During the whole flight (powerup-shutdown) my pfd keeps flickering black. My AMD RX7900XT is using the most recent driver. Also the aircraft and simulator are up-to-date.

I've got my SB defaulted to a flat 20 min taxi. This gives me 400lbs taxi fuel for the A220. I'm routinely overburning on my taxi (probably by about 2-300lbs). Is this an aircraft issue or can someone confirm this is a simbrief problem. I'm using the Simbrief profile provided by inibuilds via the forum.

I would like the map server to automatically load when the sim starts. In the instruction It says that it should modify the exe.xml, But it hasn't done that.

Hi, First off, I appreciate the hard work of both the Synaptic and Inibuilds teams on this project The extent to which you both reply to inquiries and follow up with updates is amazing!🙌🏽 The A220, while an absolutely gorgeous and cool aircraft still suffers from some critical bugs on 1.0.4 on Xbox. I am using Xbox series X, with no addons except aircraft/airports, and during A220 testing I have been flying out of default non-handcrafted airports. Performance Framerate in single digits during flight, which makes handflying - takeoff and landing near impossible. This performance degradation happens from turning the DUs on, and gets progressively worse throughout a flight.…

Here is screenshot. autopilot airspeed hold var locked in 180, I select 199kts on panel. I tested default plane, Cessna CJ4. then autopilot airspeed hold var same as my selected airspeed.

FMS Route/Legs page & Graphical Flight Planning. 1. What is the correct syntax for entering P/BD WPT and ALONG TRACK WPT? 2. In the map, what to do after selecting INSERT AFTER? How to create an Latitude Longitude waypoint in the map by clicking on the map and insert it in the active flight plan? 4. Is there any complete comprehensive tutorial on custom waypoint creation in the map and in the FMS CDU? Regards, Haseen Ahmad.

twice my aircraft turn off totally during the fly. engines, all off.

In version 1.04 the framerate seems to got somewhat better on Xbox. However, now there is another problem: Simbrief Flightplan uplink is not working. In the Tablet importing the plan as well as W&B works, but in the FMS it gets stuck at pending. After two weeks, still not usable ... come on guys!!! And before you ask: Yes, I did deinstall and reinstall the plane already.

I am a non-Navigraph user. To import a SimBrief plan to FMC, after clicking the SEND button. The screen shows PENDING, and nothing can be done after PENDING, as the attachment shows. The button turns gray. Meanwhile, EFB import SimBrief works perfectly. If I turn off using DATA to old Navigraph and delete the WASM folder. Then I can import SimBrief. Then I switch to using MSFS DATA it all works. But this solution only works once. I have to redo everything after a flight.

When selecting terrain the map server crashes with this error

When using Beyond ATC, after landing, and only with A220; BATC prematurely switches from ground handling to waiting for input for the next flight (as if you have parked at a gate and turned off the engines). This happen when coming to a stop for the first time after landing. For me this means when vacating the runway and coming to stop for further taxi instructions from BATC. I brought this issue to the BATC support staff first, and found the A220 isn't correctly setting the engine sim vars.

Please accept my apology if this is covered elsewhere. I've checked the manual and other sources online. How do you set the trim for takeoff? It seems to be permanently set at 5.0. I can't see a knob or dial. Or perhaps unlike the A320 family I don't need to do this? I just saw on the takeoff calculator for my last flight it said 4.2 nose down but I wasn't able to input it. Many thanks all for your generous help.

After have done three flights yesterday, in none of the flights I could perform an ILS Approach. Following the step in the Airbus-A220-Pilot-Guide, as you can see in the image below, when I check the Arrival data, the ILS frequency can not be displayed. Even if I place the ILS Freq in the Control Tuning Panel (CTP), the aircraft does not recognize it. Is It an issue / bug ?

noticed something that might be a performance calculation issue with the A220. During my flight, the FMS showed: CRZ ALT: FL360 OPT ALT: FL370 MAX ALT: FL370 After about 3 hours of flight, the aircraft had burned a significant amount of fuel and become considerably lighter. However, the FMS was still showing exactly the same values: CRZ FL360, OPT FL370, MAX FL370. I understand that the OPT altitude may remain the same, but shouldn’t the MAX altitude be recalculated as the aircraft gets lighter? Interestingly, SimBrief was predicting a step climb to FL380 about 150 NM later. Could this be a bug where the MAX ALT calculation is not updating dynamically with aircraft weight…

Good morning I have experienced violent shaking in the cockpit no turbulence though. When outside view show the plane flying completely normal. The shaking stops if I hover the mouse over a dial or something in the cockpit, however it does not stop if trying to click on EFB

I've downloaded the terrain map via the INI manager, and put it in a community folder name "A220 terrain" I clicked the EXE and it runs for a split second and then nothing. It does not work in game. The log says this. 2026-08-05T22:57:13.274347Z INFO a220_launcher: C:\Users\rargu\AppData\Roaming\Microsoft Flight Simulator does not exist, skipping 2026-08-05T22:57:13.296261Z INFO a220_launcher: Updating C:\Users\rargu\AppData\Roaming\Microsoft Flight Simulator 2024\exe.xml 2026-08-05T22:57:13.321081Z INFO a220_launcher: Updating C:\Users\rargu\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml 2026-08-05T22:57:13.322112Z ERROR a220_launcher…

Hello, I tried searching the forms, but how do you get the aircraft to apply reverse thrust. I do not have a fancy throttle. I just have the Saitek X52. I understand the FADEC ignores under 55 knots, but this is on every landing that I test it. Thank you for any guidance

Hi, I’m experiencing strange nosewheel steering behaviour with the Synaptic A220 in MSFS 2024. During rollout, I was applying only a small rudder input for directional correction, but the nosewheel suddenly deflected to a very large angle that was completely disproportionate to my rudder input. I was not commanding a large tiller input at the time. Synaptic’s A220 steering guidance says the rudder pedals are intended for gentle corrections and straight taxiing, while large steering angles are commanded through the tiller, so this behaviour appears abnormal. Simulator: MSFS 2024 MSFS version: 1.7.35.0 Aircraft: Synaptic A220-300 A220 version: 1.0.3 Platform: PC I have a vi…

Hi, I’m experiencing an issue where the Synaptic A220 does not capture the ILS localizer. I had the correct ILS frequency and course tuned, was established on an intercept heading in HDG, and had APPR armed. The aircraft approached and then crossed through the localizer without capturing it. The FMA remained in HDG and never transitioned to LOC guidance. I also did not capture the glideslope afterwards. Simulator: MSFS 2024 MSFS version: 1.7.35.0 Aircraft: Synaptic A220-300 A220 version: 1.0.3 Platform: PC Airport/runway: [CYUL/ILS 24R] Navdata: [Navigraph] I have attached a screenshot showing the aircraft with APPR armed before localizer intercept. Is this a known issue,…

I am mystified by the message spoiler mismatch (in blue) which appears at seamingly random point in each flight. When it does, the spoilers stop responding (except for roll control and after landing) when the spoiler handle is actionned. Any suggestion on how to address this issue? Thanks Paul

Since the 1.0.3 update was released, I’ve been having this issue with the aircraft. It doesn’t matter whether I start from cold and dark or ready for takeoff—the aircraft immediately reports these system failures. I’ve already tried uninstalling and reinstalling it (which fixed the pink textures issue), but I still can’t figure out why the batteries are overheating, the hydraulic systems are failing, and the engines are losing so much power that it’s basically impossible to fly the aircraft.

Hi, Noticed that the date on the pfd shows always the actual date + 1. Is this a general finding?