Lol, I may or may not have don’t this before myself. Well, forgetting about my plane. But sometimes I forget about it so late, it’s just doing circles over the airport. Sucked when it happened on my recent 5+ hour flight to Hawaii and I had fallen asleep. I had to redo the whole flight the next day .
But yeah, that makes sense. That’s kind of what I did but not really. I called it a go-around, but it was actually more of a missed approach where I just turned 180 degrees the opposite direction and then once I got my altitude correct and was stabilized, I re-entered my approach and made a much more successful landing attempt.
I guess this begs the next question though. What is a realistic/normal rate of descent? Is 1,500 FPM normal?
IRL the aim is to descend it idle thrust, at 250kts that’s around -1500ft/min in an A320.
At high altitude and/or high speed the ROD is of course higher.
@TechyCentipede6 If you don’t ‘overtake’ the pressurization on the way down, there’s no uncomfortable ROD for the passengers.
I think he was referring to the negative G-force being exerted when descending. But I always think that it’s something to do with the acceleration coming from 0 - 1500 fpm and not the static descent rate which doesn’t exert a different G-force to the body.
0 - 1500 in 1 second is very uncomfortable compared to accelerating the descent from 0 - 1500 in 10 seconds even though both are -1500 fpm
Okay, so then 1,500-2,000 FPM is normal then. I was just wondering. I didn’t know if 1,500 FPM was too gradual and not steep enough or if IRL aircraft descended quicker than that.
With speedbrakes even 5000ft/min and more are possible. If you dial in the ROD slowly in e.g. 300ft/min steps, the passengers will not even notice this steep descent.
On the real A320 you can even rapidly dial in a high ROD and it will increase the ROD nicely.
(there’s a special case where it can setup a high rate very fast)
Sometimes I did descend at Vmo/Mmo, extended the speedbrakes and then called a flight attendant into the cockpit.
I told them that this was the maximum ROD we could achieve during an emergency descent.
They were always very surprised that this was really a non-event and not a movie like desaster.
The mode DES is from guidance point of view - as noted in the README - exactly the same as OP DES. So it puts thrust to idle and controls speed by elevator. So the descend rate is completely dependent on drag. What it already does differently than OP DES is the respect of any constraints.
This is not always realistic, bc the real plane chooses the sub-mode dependent on descend planning. There might still be phases where it’s being used. This is in contrast to CLB where CLB is always using the same guidance as OP CLB with the difference that constraints are respected.
Hi @FearlessTiara18 just my two cents - it’s been quite painful reading through this thread! Save yourself some grief and refer to 320 Sim Pilot’s videos on YouTube. He’s a real world A320 pilot who explains things really well! He’s collated all his beginners instruction videos here: X Plane 11 Tutorials — 320 Sim Pilot I think you will find it most useful..
As for descent. Take last 3 digits off current and target altitude, and x by 3. If target is below 10,000ft then add extra 10 for slowing down. So for example if you are at 38,000ft and you want to get down to 7000ft, then the difference between 38 and 7 is 31. 31 x 3 = 93. +10 is 103 so just start an open descent 103m before you need to be at 7000 and you’ll be OK No need to limit yourself to 1500-2000 fpm.
I’ve said this many times before, I do watch videos such as 320 Sim Pilot’s, EasyJetSimPilot’s, and NEO’s just to name a few.I watch them daily tbh. However, sometimes I’m still left a little confused so it’s nice to be able to come onto the forums here and seek further help and guidance. Sometimes you can’t learn everything from just watching a video without asking some specific questions and I feel like this is kind of a reason that the forums exist here is to talk about things and issues and to ask questions when you don’t understand something. And sometimes you discover that some people have the same questions as you.
No harm in that, look at literally all of the other forums and you’ll find similar cases.
The reason I ask about the descent rate is because I’ve for whatever reason just always descended at 1,500 FPM, but I really didn’t know if that was realistic or normal or not.
Sorry if it was “painful” reading through this thread. Some of us are still trying to learn new things everyday.
Does nobody have issues with the flight plan disappearing? In the last versions the flight plan vanished when I initialized the FMC from Simbrief in 2D mode and put on the VR headset afterwards. In the latest experimental version the flight plan is gone, when I reach approach without switching vom VR to pancake mode or vice versa. Sometimes the MCDU does not display waypoints anymore, but the plane follows them nonetheless. Nobody else experiencing those effects of loosing the flight plan? On Github somebody mentioned the plan disappearing after initializing and switching to VR, bt I can’t find anything about disappearing approaches.
If anyone having issues with getting the liveries working on the new A32NX mod, you can message me directly and I can send you a compatible livery pack that you can use as a starting point to get flying again.
So far I havn’t had a disappearing approach. The FMS can skip some waypoints during approach from time to time (cause even in experimental, we still use the default flightplan manager > until we have our own). But that’s it. If you can reproduce the problem, make a video and file an issue on github.
Yes what is this about?? I have been having the same issue since the FBW mod forked and the calibration of the throttle was done in the EFB. Even after creating a 10% deadzone. No matter where the trottle is (in CLB detent) it constantly still flashes LVR CLB. Its starting to annoy me..
Any solutions?
I use the Thrustmaster quadrant btw
I have tried recalibrating quadrant and also recalibrated with the EFB
It seems that no possition on the trottle will stop LVR CLB from happening
This sometimes happens to me. I have my throttle settings calibrated correctly, but I notice I have to be very careful and move the throttle gradually after takeoff from FLX/TOGA to CLB because sometimes if I move it just a bit too far it goes out of the CLB detent and I get the constant LVR CLB flashing for the whole flight.
It’s almost as if the “click” sound is delayed slightly when you move the throttle from an actual detent, so I have to advance my throttle very slosly and gradually.
If you’re using thrustmaster tca quadrant, make sure you’re on firmware 1.61 or later and you’ve done the full recalibration process on the hardware level. There’s a few post about how to do this in this forum so it should be easy to find using the search function.
Then, use these values in your EFB calibration:
Reverse on Axis = On
Full Reverse : Start -1.00 End -0.95
Idle Reverse : Start -0.75 End -0.65
Idle : Start -0.55 End -0.45
CLB : Start -0.05 End 0.05
FLX/MCT : Start 0.45 End 0.55
TOGA : Start 0.95 End 1.00
Your sensitivity curve needs to also be reset to neutral and linear on everything, do not put deadzone in the sensitivity curve because we’re assigning the deadzone in the EFB calibration instead. I do this and all my detents are lined up properly every time.
I have the same hardware and I use it every day for development. No issues at all. Have you checked that your actual position of the lever is between start and end of the detent range you specified?
On top you know that the TCA has not that hard detents and so you need to take that into account when you specify your range.
Did you program the INIT page and the Take off PERF page properly in the MCDU? It doesn’t look like the MAN FMA is triggering correctly, which suggest that your MCDU take off perf page isn’t fully configured yet. See how I set up the MCDU and my take off on my flight yesterday.
I also noticed a few key differences in your Upper ECAM compared to mine, namely in the Switching PNL message. Did you switch it to anything other than NORM?
You’re definitely not on flx, cause the autothrust doesn’t arm and the FMA doesn’t say it. But on the other hand you are on flx, cause the thrust % is correct. Strange. Some questions to find out what’s going on there.
Which flight model (MSFS settings) do you use?
Are there any assistant settings (MSFS) activated?
Do you have any custom livery in your community folder (also non A32NX ones)?
Do you have any other mod installed?
And: see @Neo4316s’ questions.
.
No need to limit yourself to 1500-2000 fpm.
