Can’t stop laughing. Between the insistence on the FBW and the complete lack of will to actually test something, this has to be one of the best misunderstandings ever.
Don’t worry please, the community is big enough. I was actually expecting you to test a departure with constraints and see what happens, like “let me try a departure and I’ll check and report”. I mean, that’s the community idea right? But we’ll, to each their own. Don’t worry, I’m sure someone else can also test, thanks anyways!
So, in case anyone wants to test, I’ll clear up the issue I’m referring to:
- Stock A20N seems to not follow constraints on departure. Expected behaviour is to climb to the altitude set in the AP following the altitude constraints in the flight plan.
- The constraints button shows them correctly so they are correctly present in the flight plan. Regardless of that, the aircraft will climb to whatever altitude is set on the AP as fast as it can no matter the altitude constraints
- So far this seems to happen only on departure, apparently it doesn’t happen on arrival.
- Looks like an issue on the behaviour of the plane because other A20N like FBW do follow constraints both on departure and arrival. Don’t have the Fenix A20N so I can’t test but a friend of mine has it and apparently there are no issues. So, all in all could be an error on the behaviour on the stock A20N
- If someone tests a departure with constraints on the stock A20N and it follows the constraints, would be great to know how the flight was loaded into the FMC (directly from MS, manually in the FMC, etc.), I guess that could be a difference too.
Thanks in advance and best!
Seb