[A319, A320, A321] Fenix High-Fidelity Aircraft

I presume the question was for me then.
Yes, of course. Getting real doc isn’t an issue, I have this.
What I didn’t have, is what is specific to Fenix’ simulation that is necessary to get me going. For example, I won’t find on an FCOM that out of Hong-Kong I can’t access the livery manager without a VPN (yes I know, it is mentioned somewhere on their website, I overlooked it, hence the questions here and the nice response I got).
Same with the cabin announcements, the FCOM won’t tell me how they’re being triggered in Fenix’s simulation.
Etc etc.

As far as real docs are concerned, I’m now covered and reading. All good :+1:

2 Likes

Correct, my bad. That was to @Marklar666 comment on manuals.

Guys, when I perform an Autoland, after landing, at some point I will disconnect the AP.
Normally, I should have a red warning light and audible alert indicating that the AP has been disconnected.

In my case, the warning light and audible alert will not go off immediately after I disconnect the AP, but quite a long time after, may be 30 seconds.

Am I doing something wrong ?

Don’t use the common “AP toggle” binding for that. Use “AP disconnect” instead.

1 Like

Could you clarify your suggestion ? Below (circled in red color) is the button I press to disengage the AP after landing. I use the mouse for this.

I meant the binding for a hotkey or your controller button. In RL you don’t use this button on the FCU (from your screenshot), that’s only for AP engagement. There’s AP disconnect button on the sidestick which you use for AP disconnection:

5 Likes

Struggling a bit flying RNAV-Z approaches. When selected during preflight from the FCMU, they don’t match the Navigraph chart. The plane only has the initial approach fix followed by the runway. The Navigraph approach chart typically has multiple downwind waypoints, followed by a 180 degree turn to the initial approach fix. I end up having to “build” the full approach by manually entering the downwind waypoints and their altitudes. This can’t be the way it works in RL. What am I missing here?

1 Like

Do you have navigraph data installed in the plane? It’s a separate action to installing it in sim.

Did you select the VIA when entering the approach?

RNAV Z isn’t a type of approach, it’s the name of a specific approach. RNAV is the approach type and Z is the identifying letter to name it, there can be multiple RNAV approaches at the same airport. RNAV (AR) is a slightly different approach type, that the Fenix also simulates.

1 Like

Yes to all. I think I’m doing it by the book. Flew another RNAV-Z approach into KPVD Rwy 23 last night. Same thing. The Navigraph chart showed multiple waypoints on the downwind leg, followed by a 180 degree turn onto the final approach fix and final approach. As programed in, there was nothing for waypoints between the last waypoint of the STAR and the final approach fix. I had to enter the three missing downwind waypoints and their altitude constraints. Rather annoying (unless this is a RL “feature” of the actual aircraft).

Could you provide some screenshots of how you’re configuring the approaches in the MCDU?

EDIT: Here are some screenshots of how I set up the WIPOR STAR into the RNAV-Z (AR) into 23. The piece you might be missing is hitting the <VIAS button after selecting the STAR and then selecting SEABE (for example). SEABE is the termination of the STAR and also one of the IFs into the RNAV approach, so it’s a seamless transition between the two. When done this way, it properly loads in all the waypoints starting with SEABE all the way through the final approach waypoint.




Edit 2: better plan view

1 Like

Hey, thanks for taking the time to post those shots. You were correct. I was neglecting the “Via” selection. I just loaded the STAR and the approach. Never even paid attention to Via, assumed with both those steps, there would be a seamless transition from the end of the STAR to the RNAV approach. Thank you!!

2 Likes

Via was not selected. That was the issue. Thank you!!!

1 Like

Anyone else notice the speed brakes closing after disengaging reverse thrust? Shouldn’t the spoilers stay up and active until I manually close them?

But they do stay up and armed until I manually close them.

They disarm if you put little power on engines after landing

1 Like

For some reason when I move my thrust levers back to the idle position it closes the spoilers, without adding thrust.

Try recalibrate throttles via fmgc I realize that autobrakes disarming after landing without touching pedal for manual braking deccel light doesn’t show on autobrake button

I actually think what happens is, I have to move the throttles forward just a bit to stop reverse thrust, just moving the levers to idle detents doesn’t shut off the reversers. Is there an assignment within the FMS throttle calibration to make this happen so I don’t have to move them forward to dis-engage the reverse thrust?

Recalibrate your reverse idle and check if has enough tolerance between reverse idle and normal idle.

2 Likes

That seems to have worked. I adjusted the reverse idle to be just below the detent, and the detent itself as the normal idle, now the spoilers remain up, thanks.

3 Likes