Systems

During a prolonged single-engine taxi, I noticed that the running engine (engine 2) showed 0.00 for fuel used after running for nearly half an hour. When I started the #1 engine, the fuel used indicators on both engines almost immediately jumped to 0.01. Further testing showed that with engine 2 running at TOGA and engine 1 shut down, the fuel used quantity on the running engine did not increase from 0.00 even after running at this power setting for 5 minutes. When engine 1 was started, both fuel used indicators jumped to 0.01 again. With both engines running, engine 1 was pushed to TOGA with engine 2 at idle, and both indicators increased at the same rate, even with…

Changing hdg using the TCA built in hdg knob also decreases speed in the fcu. Kind Regards

When checking the DC battery voltage, the animation of the indicator needle is jumpy - it doesn't smoothly increase and decrease as the pilot moves the selector knob.

So i seen in update V1.08 the ability to refuel while the engines are running was added as an option in the EFB settings but i've looked everywhere in the EFB settings and i cant find this option anywhere is this a bug or was it removed ? also Im on XBOX flying V1.09 of the plane

Hi first time posting. I'm having an issue where the aircraft starts to fly in circles randomly, have had this happen in both HDG SEL and NAV modes. Turning autopilot off stops this but it will resume doing loops when turned back on. Also changing between HDG SEL/NAV doesn't stop it either. Wondering if anyone else has had this issue? Many thanks Matt

When pulling the VS knob on the FCU while it is blank, it currently sets the target speed to 0 fpm, effectively causing a level off upon VS mode engagement. According to the FCOM, I would expect the autopilot to synchronize with the current actual vertical speed and continue with this speed:

Happy with the fixes for the Xbox version but got a few points: Passenger version still unflyable due to lag Engine management system doesn’t change to Auto at thrust reduction altitude when doing a FLEX takeoff Pressing TOGA on the runway for takeoff starts a very slow engine spool up that means full power isn’t achieved until you are most of the way down the runway. Is only happening on first takeoff after loading in. I did a multi leg trip and didn’t have it at the second or third takeoff Chocks toggle in EFB is inverted - turning them on takes them off

When using the clock in chronometer mode, it shows only 2 digits instead of three. I was over an hour into this flight, but it was showing only 2 digits, not three.

I'm afraid that the Sim still crashes to the desktop even with the latest update! Del

I've had a few descends lately with very strong tailwinds (>100 knots). Prior to descend, I entered the expected winds in the descend forecast page and those values later matched the actual winds quite well. However, I observed the aircraft flew way faster than predicted to chase the path and then strayed above the path, requiring the speed brake to bleed of energy. It appeared to me, that the VNAV path calculation does not consider the wind from the descend forecast page. I heard, that the real VNAV is hit and miss as well, is this the intended behavior or is this an oversight of the simulation?

I did a flight today to LTFM with INBE2B arrival. I loaded my flight plan from simbrief into the MCDU through the ACARS option. At FM758 there is an altitude restriction of 9000, then the next flight restriction is at FM764 at 9000 also. The question is, why does the MCDU automatically assign higher altitudes in-between those two flight restrictions? Like 9700 ft then to 10200 ft? Is it normal to have to go through and change each waypoint in the MCDU?

Hello, I have used AAO to map an axis to the speed brakes using AXIS_SPOILER_SET. However, even if the speed brakes are in the fully stowed position, the SPD BRAKES EXTENDED message does not disappear and I cannot arm it using a keybind. I have to manually use the mouse to drag it back and forwards again. I don't believe that I have seen this error prior to the latest 1.0.6 update. (I haven't tested 1.0.5)

Hi, after the latest update everything in the cockpit stop reacting, after i have setup the flightplan, only the flap lever is moving to my input. The plane is still going but there is no reaction from any input, neither from my mouse or my thrustmaster tca throttle. I reinstalled but didnt help, i have tried 3 times and the same thing happens. Anyone else having this issue?

After I activated my secondary flight plan and reactivated NAV mode, the FMC went into Manual mode when we reached our next waypoint. I had to input a Direct To Waypoint procedure to get us back on course. Is that how it should be?

Hello everyone. This is the second time I have this issue. Both times taking off from EDDP. Just after rotation engines throttle down and a/t disconnects. I have to manually apply full trust and re-engage auto/t + NAV + Profile. Anything I can check? I have more then 50 flights with this bird but it looks strange that same issue only twice at the same airport

It has been my experience during my last few flights to and from KLAX and KPHX that certain numeric readouts on the bottom left-hand corner of the PFD will flash on and off during the final approach phase, as if they are fighting to be visible at the same time. This always happens after capturing the ILS and engaging LAND mode.

When performing a go-around after a missed approach, I cannot seem to get the plane to hold a steady altitude, even though I've dialed in a low altitude per the missed approach instructions on the approach plate and engaged altitude hold. Is there a certain procedure I should follow in times like this?

Hi, first things first: Excellent job so far with the A306. During last flight I tried to activate the entered and prepared flight plan in the FMS. There after I can notice the following things: - FMS (that I used) went dark - 2nd FMS showed the INIT Page - alle switches indications froze in their state. - MSFS still continued to work and the plane had something like a manual mode. Maybe you can have a look on that? Kind regards Fabian

Hi, Minor thing. I have seen on several occasions where the Altitude prediction (Yellow Banana) is not aligned with the current track. If going direct to a waypoint the Altitude Prediction symbol is offset and not directly over the track line. Christian

Like in this post already talked about the rudder steering (6 degrees on ground nosewheel steering with rudder) still doesnt´t work with the newest version 1.0.8. It worked perfectly fine with version 1.0.0 and 1.0.1. Is there any update from the developement team about this?

Dear: 1. Even in v 1.0.5, ZFWCG Entry in FMC causes freeze and after some time, MSFS closes. Please note I use desktop PC. 2. During PROF descent, FMC target speed goes to zero, (at the bottom of PFD speed scale). 3. No TOD in either ND or FMC. 4. Flight from VGJR to VGHS. ILS RW 14, MIMAR transition. Regards, Haseen Ahmad.

Hello, In advance, I will say that I did not manage to capture it on video. But I was flying a 3 hour route and once I started to decend, I got notifications about engine 1 going out. I did everything it was shown to do. And after doing everything, after like 5 seconds, the engine turned off and electricity was gone aswell. Automatically, yaw dampers and etc switch off and had no more control over the plane and after 5 seconds or so the plane was overstressed for overspeeding while falling. Is this still a bug? I followed all the procedures up until it happened and I do not believe that it was for something I did wrong since for a number of flights I did everything t…

Hi, If using the AI co-pilot function within MSFS, the co-pilot can tune the radio freqs, but not the transponder code. I see a quick flash of the correct code on the pedestal and then it resets to whatever was there before. Is anyone else having this issue or is there a workaround? Thanks 😉

In the manuals I have read, there is a mention of using the DCEL mode on the Flight Plan page to slow the aircraft down to green dot speed if it has passed the TOD marker but descent clearance has not yet been given. However, I do not see this function available:

The FCOM states the following for the heading select mode: However, I noticed that the iniBuilds simulation switches direction beyond 180° and turns to the closest direction.