matsparky99

I had something similar on a one engine inop departure that basically whatever I was doing there was no way to take the fuel from any other source than the main tank of the relative engine. It looks like the fuel system is either not modeled completely or is very bugged. Here is the link to my post about that which never received a response:

I tried yesterday as well, another engine out takeoff, but this time I failed ENG 1. The fuel issues were there again, the engine 2 was taking fuel only from its wing tank with every possible configuration(pumps off, pumps on, xfeed open, closed). On top of that the FMA never displays a flashing THR MCT at EO accel alt, and the managed speed goes to 250 kias iso green dot. I took off with Eng A/I on but WAI off, nevertheless while doing the ECAM actions for the engine shutdown, it got stuck at the sensed item for the WAI to be off for 15 sec, which I solved by turning off Eng A/I, but to my understanding it should only be there if WAI is in use. I checked WAI later on during the climb and this time it wasn't triggering a Bleed fault and WAI fault like in the post above. Another thing I can't find on the FCOM I found online is about the ECAM limitation under all phases: APU BLEED : DO NOT USE. I have a version of the FCOM from 2020 so for sure it's not very updated but I couldn't find any procedure that had this limitation, and specifically speaking, ENG 1 FAIL according to FCOM doesn't have any ECAM limitations, while ENG 1 SHUTDOWN have only limitations on APPR & LDG (LDG DIST AFFECTED; GA THR : TOGA ONLY; *If spoilers are partly extended: FOR LDG: FLAP LVR 3; FOR GA: FLAP LVR 1). So is this APU BLEED : DO NOT USE an update to the procedure since 2020 or is it something that wasn't supposed to be there?

Yes, I didn't include in my post why I explained how to load fuel. The reason why APU didn't start is because FOB so fuel on board is 0 kg in the aircraft. Basically APU is fuel starved and won't start until you load fuel. It was only set on the loadsheet page of the OIS.

Hi The fuel you see in the loadsheet is the fuel that you plan to have until you press set fuel, which then fills the tank. If you see on the system display, below the APU info, you can find different info. Last to the right contains Ground Weight (GW); GW center of gravity (GWCG) and Fuel On Board (FOB) which in your case is displayed as 0 kg, so it means you don't have any fuel loaded. So basically after you import your ZFW and Fuel from simbrief or you insert it manually remember to press set ZFW and set Fuel next to their number to transfer your plan to the aircraft.

Hi, I'm pretty sure that's not a bug as ILS 05 for Hamburg IHHE is not an ILS DME but just an ILS, so also in real life you don't get any distance information. I'm just not sure that it's supposed to show 0.0 NM but rather not show anything.

Hi all, I tried to perform a OEI departure in ZRH and had a little bit more challenges than expected that precluded me to continue and do a OEI approach. After I finished my OEI departure I was in a holding pattern waiting to burn around 10 tons of fuel. Here I came across a couple of bugs: First one that came was the fuel burn, with the flaps retracted and the CTR TK FEED pb-sw set to AUTO the center tank fuel pumps should supply the engines, even though all this conditions were on, the operative engine was fed only by its side wing pumps, which created an imbalance as warned as well in the ECAM actions of ENG SHUTDOWN. No issues, I tried to perform a fuel imbalance corrective procedure which didn't work out. Even turning off the wing pumps of the ENG 1(the still operating engine) didn't work as they were still feeding the ENG 1, next step I used the XFEED valves and turned off also the CTR TK pumps, but still the fuel was getting lower on the left side and was not lowering on the right side or center side, which as well can tell that there is no leak. So with my understanding of the system this is a bug. Second issues: At some point during the holding while dealing with above mentioned fuel issues I got the autopilot disconnect and an very fast descent to the ground(I was around 4000ft AGL in the holding pattern) I managed to recover and while doing so I got severe icing master caution which then I thought was the trigger to a stall at a higher speed than usual. I turned on WAI and ENG A/I and managed to get back into a climb, now it's true that I was holding in visible moisture with TAT less than +10°C but during the holding when I turned on ENG A/I I got an ECAM MEMO ICE NOT DETECTED so I turned them off and forgot about it. Never got any ICE DETECTED alert. Here instead I think that the issue the speed in the PFD got frozen, which I noticed because after the open climb to an altitude above the cloud, I selected a speed of 250 kts iso green dot to make the fuel burn faster but the speed in level flight with thrust all the times at MCT never moved from 210 kts. And after a while I checked and the plane reached a TAS of around 450 kts and was displaying mach 0.67 or similar numbers, and here I understood that the speed indication was not working. I checked the ISIS and the F/O PFD were all showing 210 kts, so the only thing I could try to unfreeze the situation was to manually turn on the probe and window anti ice push button(anyway in AUTO they should be already on in flight) but even that didn't solve the issue. Third issue: While trying to understand why the plane was not accelerating I thought that even though we were out of clouds, maybe I still had some ice on the wings that was not allowing me to accelerate. (note: after 30 sec I went out of cloud I turned off Wing Anti Ice, previously turned on to recover from the stall) So, during my almost ground crash due to the stall described above I turned on the wing anti ice and it worked as expected, now instead when I turned on the wing anti ice I got a L BLEED FAIL(the only bleed left with the right engine being off) and the wing anti ice fail, which also in the ovhd panel had a fault light for the respective pb. I managed to resolve the L BLEED FAIL by switching off the WAI. So now I waited a minute and tried to turn it on again, but this failure kept coming back. From what I read from the available documents online the WAI is supposed to work even in a single bleed configuration. Overall if I had only issues 1 and 3 I could have tried a landing but without an IAS indication I decided to stop the simulation. Before doing so I recorded a video of the issues which is available at this link: And here also screenshots of the issue: This first image shows the speed being stuck at 210 kts on the PFD while TAS is 257 KTS which is a TAS around 20 kts higher than it should be(but as I said it even reached more than 400 kts with a mach number indication with the IAS stuck at 210) On this second image the Wing anti ice was on but it failed the bleed and as a result also the WAI itself.