Performance mod STCs for winglets, gross weight increases, and the paperwork behind the claims

What gets reviewed

• Compare structural and flutter substantiation against the claim it supports.
• Trace approved performance data and AFM performance supplements against the claim it supports.
• Challenge MTOW-increase paperwork chain including registry-specific noise and performance documents against the claim it supports.
• Reconcile AML applicability against the claim it supports.
• Confirm approval basis against the claim it supports.
• Index configuration definition against the claim it supports.

What gets validated

• The review notes that evidence link: structural and flutter substantiation fails review if the cited record cannot be tied to the current baseline.
• Limit carryover: approved performance data and AFM performance supplements fails review if the cited record cannot be tied to the current baseline.
• Source control: MTOW-increase paperwork chain including registry-specific noise and performance documents fails review if the cited record cannot be tied to the current baseline.
• Closure owner: AML applicability fails review if the cited record cannot be tied to the current baseline.
• Configuration match: approval basis fails review if the cited record cannot be tied to the current baseline.

Evidence normally required

• Test file: structural and flutter substantiation
• Analysis note: approved performance data and AFM performance supplements
• Manual source: MTOW-increase paperwork chain including registry-specific noise and performance documents
• Configuration item: AML applicability
• Closure evidence: approval basis
• Baseline record: configuration definition

Common discrepancies

• Installer issue: performance claims not reflected in any approved AFM supplement.
• Buyer concern: a gross-weight increase missing registry-specific documentation at import.
• Program risk: wing structural inspection ICA ignored at heavy check.
• Authority question: baseline does not match the delivered records.

How the work runs

What the buyer receives

• The review notes that evidence map for Performance Modification STC
• Discrepancy register for Performance Modification STC
• Applicability and approval basis summary
• Source record request list

Who uses the output

• Fleet planning leads use the map to brief the decision.
• Asset managers use the register to assign closure.
• Performance engineers use the request list to collect source records.

How the work fits into the transaction or program

The decision is what substantiation a performance or aerodynamic modification STC carries (winglets, drag reduction kits, gross-weight increases) and what buyers and installers should verify before trusting the performance claims. The evidence set centers on structural and flutter substantiation, approved performance data and AFM performance supplements, the MTOW-increase paperwork chain including registry-specific noise and performance documents, and AML applicability. The likely weak points are performance claims not reflected in any approved AFM supplement, a gross-weight increase missing registry-specific documentation at import, and wing structural inspection ICA ignored at heavy check. The output gives the fleet planning lead a cleanup register for Performance mod STCs for winglets, gross weight increases, and the paperwork behind the claims before certification package scoping.

Regulatory limits

EE does not replace the applicant, STC holder, authorized representative, or regulator. Approval, acceptance, and airworthiness decisions remain with the people and authorities assigned to those functions.

Specific to this review

• what substantiation a performance or aerodynamic modification STC carries (winglets, drag reduction kits, gross-weight increases) and what buyers and installers should verify before trusting the performance claims.
• Structural and flutter substantiation often controls whether later summaries can be trusted.
• Performance claims not reflected in any approved AFM supplement is treated as a record gap until an owner closes it.
• FAA and EASA evidence should stay distinguishable from commercial claims and installer notes.
• The scope uses the Performance Modification STC Support question as the control point, so the review stays tied to Certification package scoping and the buyer decision behind it.
• The evidence starts with Structural and flutter substantiation and follows Certification Evidence Mod Stcs references until every exception has a source location and a reason code.
• The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
• The timing matters for Fleet planning lead: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
• The boundary control keeps Winglets Gross Weight Increases questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
• The handoff value comes from Evidence map for Performance Modification STC; it gives the next reviewer a precise map instead of another broad request for a better file.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits