Good evening,

I was on a normal flight, following the same procedure I usually do,I started Engine 1... and it didn't start. N2 oscillated around 4.5%, while N1 remained at 0%.

I tried to restart it by turning the engine off. This time, as I moved the Engine Master switch to the OFF position, N1 climbed to 10%. I moved the Engine Master switch back to the ON position to inject fuel, but nothing happened, as I noticed that the fuel flow was at 0.

I switched the left fuel pumps off and back on, and the fuel flow increased to 850 kg/h, but N1, N2, and N3 remained unchanged.

I then tried starting Engine 2, but I encountered the same problem.

I can confirm that the engine mode selector was in the IGNITION/START position during the start sequence, and that the fuel pumps, APU, and APU bleed were all ON. I even tried switching the PACKs OFF, but it made no difference.

I've done more than 150 flights with the A359, and this is the first time I've ever encountered this issue.

Thank you in advance

Edited Friday at 09:44 PM3 days by Antoine G

25 minutes ago, Antoine G said:

Good evening,

I was on a normal flight, following the same procedure I usually do,I started Engine 1... and it didn't start. N2 oscillated around 4.5%, while N1 remained at 0%.

I tried to restart it by turning the engine off. This time, as I moved the Engine Master switch to the OFF position, N1 climbed to 10%. I moved the Engine Master switch back to the ON position to inject fuel, but nothing happened, as I noticed that the fuel flow was at 0.

I switched the left fuel pumps off and back on, and the fuel flow increased to 850 kg/h, but N1, N2, and N3 remained unchanged.

I then tried starting Engine 2, but I encountered the same problem.

I can confirm that the engine mode selector was in the IGNITION/START position during the start sequence, and that the fuel pumps, APU, and APU bleed were all ON. I even tried switching the PACKs OFF, but it made no difference.

I've done more than 150 flights with the A359, and this is the first time I've ever encountered this issue.

Thank you in advance

Hi,

I'm not entirely sure what could be causing this. Could you please try on a default or iniBuilds livery?

Thanks!

Hi,

I have same issue, I manage to startup but cannot start the engines with APU on, also tried L & R pack off though it was not required before, as well as changing to default livery. All are with no help. I'll fall back to v1.2.6

Thanks.

I just tried using the default livery, but the problem persists.

I've taken some additional screenshots to show you the issue.

I can confirm that the engine mode selector was in the IGNITION/START position during the start sequence, and that the fuel pumps, APU, and APU bleed were all ON.

I set Engine 1 Master to the ON position, and the engine started to spool up briefly before stopping, as shown in screenshot #1.

I then moved the Engine Master switch back to the OFF position, but the engine continued the starting procedure and stopped , as shown in screenshot #2.

I then moved Engine 1 Master back to the ON position, and N1 climbed to 10%, as shown in screenshot #3.

I even tried the manual start procedure, but without success.

Thank you for your help

Hi confirmed this has happened to me as well. ENG1 master selector set to on, ENG START selector to IGN and FF essentially zero hence no ignition. Fuel Pumps all on.

Hello, I am encountering this issue as well after the new update. Engines failed to start and N2 froze at 3%. I recycled Engine bleed master for engine #1 and it started randomly, but I couldn’t replicate that after. I am on 2020 as well and no luck with the default livery

Good evening :)
I just made a new clean install, launched the sim, started the engines immediatly without preparing the flight... and It worked normally !
I then started a normal flight, prepared the flight... and I got the exact same issue as described above...
I tried @SeanDarren method to recycle Engine bleed master, and it worked for ENG 1 , but impossible to do the same for ENG 2
While ENG 1 was running, APU bleed & Engine mode sel NORM, I noticed that PACK 1 was in the fault mode.
The start sequence is really really strange, to get the N1 climb up to 10%, you have to make a combinaison with the engine mode selector and the engine master
But without the method (that work "only "for eng 1), impossible to start the engines




Clean install done at 1830z, If you did any updates before :)
Good luck resolving this

Please check the "maintenance" menu at OIS panel, sometimes the engine needs to be maintained :-) (Not saying this was the case, but sometimes...)

1 hour ago, klusik said:

Please check the "maintenance" menu at OIS panel, sometimes the engine needs to be maintained :-) (Not saying this was the case, but sometimes...)

Maintenance was one of the first things I checked. Servicing both engines still did not resolve it.

2 hours ago, SeanDarren said:

Maintenance was one of the first things I checked. Servicing both engines still did not resolve it.

Okey, okey, hmmm, interesting then :-)

Same issue as reported above (rel. 1.2.7) None of the suggested workarounds let the engines start up.

Is there an option to switch back to previous release of A350 for MSFS2020?

Same here with 1.2.7 the only thing work with 1 eng was turning packs off but, it didn't work for the second.

The only workaround is the panel state opt.

Hi everyone,

Thanks for your reports. I have forwarded this to the team marked urgent.

Appreciate your patience!

In the meantime, if any of you are willing to troubleshoot with me;

• Make sure the simulator is completely closed.

• Locate your Community Folder.

• Rename your Community Folder to Community1.

• Relaunch the simulator. This should create a new Community folder.

• Once you reach the main menu, close the simulator.

• Move the A350 from Community1 into the newly created Community folder.

• Launch the simulator again.

Let me know if that helps, thanks!

Hello Kyle,

I followed your suggestion regarding the Community Folder. For now, the problem seems to fixed. Engines are starting as expected. Tomorrow I am going to conduct some more tests. Thanks.

Forgot to mention: MSFS 2020, A350_900 , rel. 1.2.7 with default livery

Edited 59 minutes ago59 min by Norbert Schwarz

2 minutes ago, Norbert Schwarz said:

Hello Kyle,

I followed your suggestion regarding the Community Folder. For now, the problem seems to fixed. Engines are starting as expected. Tomorrow I am going to conduct some more tests. Thanks.

Great news! This most likely means there is a corrupt or outdated folder in your community folder causing issues.

Best practice, start adding 1 by 1 until you find the culprit.

Thanks!

9 minutes ago, iniKyle said:

Great news! This most likely means there is a corrupt or outdated folder in your community folder causing issues.

Best practice, start adding 1 by 1 until you find the culprit.

Thanks!

Sounds like a compatibility issue then. I hope the team is able to provide a fix because the workaround is way too cumbersome.

I just closed and relaunched Flight simulator and repeated my test. Sorry, but problem is back. Engine 1 working as expected, engine 2 doesn’t start.

3 minutes ago, SeanDarren said:

Sounds like a compatibility issue then. I hope the team is able to provide a fix because the workaround is way too cumbersome.

None of our 2020 testers are reporting this issue. Apart from the few in this thread, nobody else is having issues.

Everyone runs their sim differently, with countless combinations of hardware, settings, and third-party add-ons that can lead to different outcomes. This makes it difficult to pinpoint the root cause of an issue without more specific information.

My guess is it comes down to a 3rd party livery or cabin mod causing the issue. If the above is deemed too cumbersome, try removing all 3rd party liveries/mods for the A350.

Thanks

1 minute ago, Norbert Schwarz said:

I just closed and relaunched Flight simulator and repeated my test. Sorry, but problem is back. Engine 1 working as expected, engine 2 doesn’t start.

So, worked on initial load, not working on your second load in.

Thanks. Taking notes for the team!