Engine certification
Part 33 engine certification data support
Part 33 engine certification support helps an engine or accessory supplier line up the substantiation behind the airworthiness standard for aircraft engines against the certification basis the program claims. It is used by teams whose endurance, vibration, and containment test data was generated over a long campaign and may no longer map cleanly to the applicable amendment level. The work reviews the basis, the test substantiation, and the life-limited part declarations. You receive a requirement-by-requirement gap read keyed to the standard and a prioritized list of the data to close.
When this review is needed
- An engine program is heading for review and the substantiation has to be checked against the amendment level the basis names.
- A derivative or rated change reuses prior test data and the credit carried forward needs to hold against the current basis.
- Life-limited part lives were set early and the analysis behind them no longer matches the configuration that ran the tests.
- A rotating-component redesign changed the disk or spool geometry and the cyclic life calculation has to be re-traced.
The problem
An engine certification campaign runs across years of test cells, and the configuration that ran the early endurance block is rarely the configuration the type design freezes. Block tests, bird ingestion runs, and fan-blade-off containment work get dispositioned in test reports and correspondence, then the build standard moves underneath them. By review, the substantiation reads as a stack of credit claims tied to a configuration the data no longer fully describes.
What gets reviewed
- The certification basis and the applicable Part 33 amendment level for the engine
- Endurance, vibration, and containment test substantiation against the requirements they answer
- Each life-limited part declaration and the analysis and test behind its declared life
- Bird ingestion, hail, and rain runs against the ingestion requirements they support
- Type design data and the configuration the substantiation actually exercised
- Instructions for continued airworthiness traceable to the substantiated configuration
What gets validated
- Each airworthiness standard requirement maps to substantiation that currently supports it
- Test substantiation reflects the engine configuration the type design now defines
- Declared life-limited part lives trace to the analysis and test that set them
- Cyclic life claims for disks and spools rest on stress and mission spectra consistent with the rating
- Reuse credit from prior programs is justified against the basis the current program claims
- Derived requirements from test findings are captured and fed back to the design substantiation
Evidence normally required
- The certification basis and the amendment level it cites
- Endurance, vibration, ingestion, and containment test reports assembled so far
- The life-limited part analysis and the declared lives
- The mission and rating spectra the life analysis assumed
- The type design configuration and any change records since the tests ran
Common discrepancies
- Substantiation generated on a configuration that the type design has since superseded
- Declared part lives recorded without the full analysis trail behind them
- Cyclic life carried from a prior rating without re-running the mission spectrum the new rating implies
- Reuse credit carried from a prior engine without justification against the current basis
- Test findings dispositioned in correspondence but never reflected in the substantiation set
What is at stake
When test credit is tied to a superseded build, an examiner asks for re-test or re-analysis on the rotating hardware that is most expensive to repeat. A single unsupported life-limited part declaration can hold up the whole type design, because the engine cannot enter service against a part life the analysis trail does not carry.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Confirm the basis
Establish the certification basis and the Part 33 amendment level the program claims for the engine.
Anchor the configuration
Identify the build standard each test exercised and where the type design has since moved.
Trace the lives
Follow each life-limited part declaration back to the analysis and test that set it.
Read the gaps
Produce a requirement-by-requirement gap read and a prioritized closure list before review.
What the buyer receives
- A requirement-by-requirement gap read keyed to the Part 33 amendment level
- A substantiation map tying each test to the requirement it answers
- A life-limited part trace showing the analysis and test behind each declared life
- A prioritized list of the data to close before review
Who uses the output
- Certification leads preparing the engine submittal
- Stress and lifing engineers closing the life-limited part trail
- Program management sequencing any re-test against the configuration
How the work fits into the transaction or program
The work supports the engine supplier's own certification program. It strengthens the substantiation ahead of review and leaves the team with a configuration-anchored evidence set that a second examiner can follow without re-deriving the build standard.
Start with a single asset
Confirm requirements trace through verification.
Aircraft-specific considerations
Engine records sit apart from the airframe they hang on: the same type can power several airframes, and the life-limited part stack moves with the engine module rather than the aircraft. Substantiation has to follow the module and rating, so the review anchors each life and test credit to the engine build standard rather than to any installation.
Regulatory limits
Endeavor Elements supports the applicant's engine certification data. It does not issue a type certificate, make compliance findings on the authority's behalf, or determine that an engine is airworthy. The applicant and the authority keep their roles.
What this review does not cover
- Issuing any type certificate, approval, or design approval
- Performing the engine test campaign or rig testing itself
- Setting or approving life-limited part lives on the authority's behalf
Specific to this review
- Part 33 substantiation is tied to the engine configuration that ran the tests, so a later type-design change can quietly invalidate test credit the program still relies on.
- Declared life-limited part lives are only as defensible as the analysis trail behind them, which is why partial trails are a recurring finding on engine programs.
- Cyclic life depends on the mission spectrum assumed, so a rating change can move a disk life even when the hardware geometry stays the same.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
International Civil Aviation Organization. International standards for the airworthiness of aircraft and the framework states use for type and continuing airworthiness.
Frequently asked questions
Can reuse credit from a prior engine carry to a rated derivative?
It can, but the credit has to be justified against the basis the current program claims and the configuration the new rating runs. The review checks whether each carried claim still holds rather than assuming the prior credit transfers.
Do you set the life-limited part lives?
No. The applicant declares the lives and the authority accepts them. The review traces each declared life to the analysis and test behind it and flags the declarations whose trail is incomplete.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Walk through your situation with an engineer who has done this work.