Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update cg for ELAC 103 #7906

Merged
merged 13 commits into from
Apr 2, 2023
Merged

fix: update cg for ELAC 103 #7906

merged 13 commits into from
Apr 2, 2023

Conversation

donstim
Copy link
Contributor

@donstim donstim commented Mar 26, 2023

Summary of Changes

ELAC 103 resulted from an Airworthiness Directive (AD) highlighting a possible unsafe condition at aft CG due to reduced efficiency of angle-of-attack protection in certain configurations in combination with certain maneuvers. The initial issuance of the AD severely restricted the aft CG envelope for the A320NEO. Airbus developed and incorporated ELAC 103, which regained most, but not all of the aft CG envelope.

This PR incorporates slight changes to payload loading stations to bring the CG for typical loadings forward by about 1.5%. This change is both to retain aft CG loading margins under ELAC 103 and in response to comments that PR #7691 moved the loaded cg a bit too far aft. The amount the CG can be moved forward is limited by need to comply with the forward CG envelope at 79T.

The CG envelope shown on the payload page of the EFB will be updated separately (and already has been in the experimental version).

Screenshots (if necessary)

This is the new CG envelope as incorporated into the experimental version:
Screenshot (2702)

References

This is the official reference for the ELAC 103 CG envelope. This figure is for weight variant WV053 (MTOW 77T). The A32NX is WV055 (MTOW 79T). For WV055, the CG envelope lines can be linearly extrapolated to 79T.

ELAC 103 Updated CG limits extended forward cg WV053 diagram

Additional context

Discord username (if different from GitHub):

Testing instructions

Confirm that reasonable loading distributions (for example, loading via the EFB payload manager result in CG values within the CG envelope. Confirm that the airplane can still be loaded to 79T and be within the takeoff CG envelope. Loaded CG value can be found either on the MCDU fuel prediction page with correct ZFW entered, or on the MSFS Fuel and Payload UI.

How to download the PR for QA

Every new commit to this PR will cause a new A32NX artifact to be created, built, and uploaded.

  1. Make sure you are signed in to GitHub
  2. Click on the Checks tab on the PR
  3. On the left side, click on the bottom PR tab
  4. Click on the A32NX download link at the bottom of the page

@donstim donstim changed the title fix: update cg for elac 103 (moves cg forward about 1.5%) fix: update cg for ELAC 103 Mar 26, 2023
@2hwk
Copy link
Member

2hwk commented Mar 27, 2023

Note that the CG Envelope in the EFB will only be correct in the development build when #7715 is merged

@2hwk 2hwk added this to the v0.10.0 milestone Mar 28, 2023
@2hwk 2hwk added the QA Tier 1 label Mar 28, 2023
@donstim
Copy link
Contributor Author

donstim commented Mar 30, 2023

Note that the CG Envelope in the EFB will only be correct in the development build when #7715 is merged

That's okay. These changes can be made independently.

@2hwk
Copy link
Member

2hwk commented Apr 2, 2023

QA Report

Testing:

  • Confirm that reasonable loading distributions (for example, loading via the EFB payload manager result in CG values within the CG envelope.
  • Confirm that the airplane can still be loaded to 79T and be within the takeoff CG envelope. Loaded CG value can be found either on the MCDU fuel prediction page with correct ZFW entered, or on the MSFS Fuel and Payload UI.

image

Negatives:
N/A

Result:
Passed

@2hwk 2hwk merged commit d9585cc into flybywiresim:master Apr 2, 2023
@donstim donstim deleted the fix-update-cg-for-ELAC-103 branch April 2, 2023 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants