Hélène CIZERO

+1

Hello, the secondary PERF page gives weird F, S and O speeds. I don't remember it was the case with 1.03

Hello, looks like the 1.0.4 update introduced a bug. When I set the NORTH REF to TRUE, CAT 3 capability is lost. I may be wrong but I don't think the Fail Operational Capability landing capability has something to do with the North Reference ?

I wonder if the bug could be related with the AUTO STEP CLIMB option on the EFB. A friend has the option activated and never had pressurization issues. Mine is deactivated, cause I always set the STEP ALTS in the FMGS after reaching the TOC, and I always have my cabin altitude remaining steady during the whole flight, even after 2-3 step climbs.

Hello, the MORA indicated on the ND is quite incoherent, especially when in the middle of the Atlantic ocean.

As I said, somemes it works, sometimes it doesn’t. I flew from FACT to LSZH today and did about 10 ETPs along the route. Only 4 were displayed correctly on the ND with their position in front of the LSK 5R.

Hello, the FD is very "nervous" during the initial climb after takeoff, until about the acceleration altitude. Please fix this.

Hello, this problem is also present on the A350, but it wasn't the case in its earlier versions (I don't remember which version). After takeoff, there is always a sudden abrupt pitch movement and I think it coincides with the moment at which the FBW transitions from Ground law to Flight law. Could you please fix this on both aircrafts ? Thanks.

Hello, I like to use the DATA/ETP feature along the route to get an ETP between suitable en-route airports. However, this ETP isn't displayed along the route 90% of the time. Somtetimes it does, it don't know how. When it is not displayed, I noticed the ETP location was not displayed on the MCDU as well. ETP location along the route on the MDCU ETP Page, and pseudo-waypoint on the ND should be displayed all the time (see FCOM attached). Edit : I investigated a bit a it seems that if the two facilities used in LSK 1L and 3L are along the flight plan route, the ETP Location (LSK 5R) and (ETP) pseudo-waypoint are well displayed on the MCDU and ND respectively. However, if one of the facilities is away from the flight plan track, the system struggles and doesn't display ETP location (LSK 5R) neither the (ETP) pseudo-wayoint on the ND. Congratulations and encouragements to the team. I encourage you to fix this bug and port the code to the A350. Despite this bug, the overall ETP calculations looks very accurate on this aircraft, so please port this to the A350 which still has a very buggy ETP page.

My apologizes. I checked the FCOM and I had to write the time without the "Z" so I tried to set "0822" and it worked perfectly.

Hello, did a FAOR -> FACT and return without powering down the aircraft. Everything fine during the first flight. However, during return flight preparation, the FMGS displayed a weird total FPL distance (screenshot attached). Distance went back ok during initial climbout.

Hello, please review the Flight Directors ground engagement logic. First, as I said in a previous post, they should be always ON when the FMGCs are powered up. Also, in normal "managed" conditions, before applying takeoff power, the FMA should display "CLB" blue instead of V/S 0 green. The FCU windows should all display "dashes". See FCOM 1.22.30 for more details. SIM : REALITY:

Hello, after a 10 hours flight, it is impossible to get 0 GS displayed on the NDs. There should be a residual 2-3 Kts because of the IRS drift. So I investigated further and checked the DATA / POSITION MONITOR page and it shows 0.1 NM error for the 3 IRSs which is also totaly impossible after 10 hours of flight. Could you add some drift to the IRSs to reflect more reality ? Below is a table of the acceptable drifts vs flight time.

Hello, during a HOLD, pressing LSK 1R "IMMEDIATE EXIT" should turn the aircraft directly to the Holding Fix while remaining within the protected area. Instead of doing this, the aircraft continues the Hold normally and exits when reaching the fix. See the below screenshot taken after pressing IMMEDIATE EXIT. I draw in blue what the aircraft SHOULD do and draw on the ND, but instead it continued to fly the HOLD until the fix.

Hi Eddie. I can confirm no assistance options here

Got the answer from the FCOM. I should have verified first.. Direct insertion into the active FPL is taken into consideration without opening the Temporary F-PLN. Only adding a WPT via the LAT REVISION / NEXT WPT triggers the Temporary F-PLN.

I investigated a but further. Looks like the bug is more complex. I have been able to display a user waypoint in the FIX INFO page. So, why does the page accepts "ETP1" and not "LHR27RX" ? One precision which may be important for debugging, when trying to display "LHR27RX" I was on the ground, when displaying "ETP1" I was in flight.

Hello, I flew today from LFBO to FAOR. Started my trip at FL310, then 330, 350 and finally 370. I noticed that whatever the cruise altitude was, the cabin altitude remained constant at 5320ft. So consequently the Delta-P raised at each step climb. When reaching FL370, the Delta-P value appeared amber. Shouldn't the cabin "climb" at every step climb to maintain the Delt-P within limits ? Also noticed that the CAB V/S always shows +/-50ft/min even if the CAB ALT remains steady. Below is a screenshot taken at FL370. I also send you the latest autosave file. 1762880859.bin

Hello, I noticed the FDs are always OFF after powering the aircraft from a Cold and Dark state. According to the FCOM 1.22.30 it should not be the case.

I agree. I am not a big fan of the moving nacelles. In reality they just follow the wing flex, obviously because they are attached to them. But the movement of the nacelle regarding to the pod itself is quite limited IRL. I think the "issue" with this flight model is the wing flex itself, which don't flex from the root, but only on their 3rd part, after the outward engines.

Hello, I find the wing flex very basic. Only the outer part of the wing is moving. No movement from the root, and no nacelles movement.

Hello, inserting a waypoint in the Active F-PLN in flight is immediately added instead of triggering the temporary F-PLN. Is it normal ?

Sorry I didn't notice the subject was already discussed. Thanks @Swisspilot1986

Hello, creating a time marker creates a "weird" waypoint at hundred miles away. Is it normal ? Does the simulated firmware allow Time Markers to be created ?

Hello, the aircraft doesn't respect the acceleration altitude when entered manually in the PERF / TAKEOFF page. It always accelerate at the same time as the thrust reduction. In the following case, it accelerated at 2000ft instead of 3500.