A recurring misconception in aerospace certification is that an engine carrying a valid Type Certificate automatically satisfies the fire-protection, safety and compliance requirements of every aircraft installation in which it is used. In reality, aviation certification has been deliberately structured to prevent this assumption. The regulatory framework separates engine approval from aircraft approval because each product introduces different hazards, operating environments and compliance obligations. This distinction sits at the heart of many aerospace fire-testing programmes and explains why installation-specific evidence continues to be required even when substantial engine certification data already exists.
Why Separate Certificates Exist
Aircraft and engines are certified under different regulatory frameworks because they represent different products with different safety objectives.
For FAA programmes, transport-category aircraft are typically certified under 14 CFR Part 25, while turbine engines are certified under 14 CFR Part 33. Under EASA, the equivalent frameworks are CS-25 for large aeroplanes and CS-E for engines. Although the numbering and technical objectives are often similar, the product boundaries are fundamentally different.
The engine Type Certificate focuses on the engine as a standalone product. It addresses issues such as:
- Engine fire protection.
- Rotor integrity.
- Engine controls.
- Fuel systems.
- Lubrication systems.
- Endurance requirements.
- Bird ingestion.
- Mechanical reliability.
The aircraft Type Certificate, by contrast, focuses on the complete aircraft as an integrated system. It considers:
- Structures.
- Flight controls.
- Powerplant installation.
- Electrical systems.
- Fire detection.
- Fire extinguishing systems.
- Crew interfaces.
- System interactions.
- Continued airworthiness.
This separation allows an engine manufacturer to develop an engine that can potentially be installed on multiple aircraft types without requiring complete engine recertification for every programme.
What Does an Engine Type Certificate Actually Approve?
An engine Type Certificate approves the engine type design and associated certification data.
Typically, this includes:
- Approved design drawings (BOM).
- Performance limitations.
- Operating limitations.
- Installation assumptions.
- Approved manuals.
- Continued airworthiness information.
- Associated certification findings.
What it does not approve is every future installation of that engine.
This distinction is critical because certification evidence is generated against a defined configuration and a defined set of assumptions. If those assumptions change when the engine is installed on a particular aircraft, additional compliance evidence may be required.
For example, an engine may demonstrate satisfactory fire resistance during engine certification testing. However, the installation may introduce:
- Different airflow patterns.
- Different nacelle geometries.
- Alternative firewall arrangements.
- New electrical routing.
- Additional fluid systems.
- Different extinguishing-system architectures.
Each of these factors can influence fire behaviour and therefore require separate assessment.
Why Installation Compliance Exists
Installation compliance exists because neither the aircraft Type Certificate nor the engine Type Certificate alone proves that the installed propulsion system is safe.
The engine certification programme demonstrates that the engine complies with engine regulations.
The aircraft certification programme demonstrates that the complete aircraft complies with aircraft regulations.
The installed propulsion system sits at the interface between these two worlds.
This interface often includes:
- Engine mounts.
- Pylons.
- Nacelles.
- Firewalls.
- Drain systems.
- Ventilation systems.
- Electrical harnesses.
- Fuel lines.
- Hydraulic systems.
- Control systems.
The certification challenge is therefore not simply validating individual components but understanding how those components interact when assembled into a complete aircraft installation.
The Importance of Fire Testing at the Installation Boundary
Many fire-testing enquiries arise because organisations recognise a fire-protection requirement but have not yet determined whether the requirement originates from the aircraft certification basis, the engine certification basis or both.
This distinction matters because similar fire-test equipment may support very different certification findings.
A burner capable of producing a severe fire environment may be used to generate evidence for:
- Aircraft fire-protection requirements.
- Engine fire-protection requirements.
- Equipment qualification.
- Installation validation.
- Special-condition compliance.
The equipment may be identical.
The certification objective may be completely different.
This is why successful programmes begin by identifying:
- Product type.
- Certification basis.
- Applicable authority.
- Means of compliance.
- Installation boundary.
- Required certification finding.
Only after these factors have been defined can a suitable test programme be developed.
EWIS as a Practical Example
Electrical Wiring Interconnection Systems (EWIS) provide one of the clearest examples of certification-boundary challenges.
An engine manufacturer may possess extensive fire-resistance data for engine-mounted wiring.
However, the aircraft installation may include:
- Additional harness routing.
- Different support structures.
- Alternative connector arrangements.
- Larger bundle configurations.
- Different fire-zone classifications.
The engine evidence may remain technically valid.
Nevertheless, a documented gap analysis is typically required to determine whether the existing evidence fully addresses the installed configuration. Additional testing may be necessary if installation-specific conditions have not previously been demonstrated.
Why Commercial Responsibility Is Not Regulatory Responsibility
Another common source of confusion occurs when commercial ownership is mistaken for certification ownership.
A supplier may design a component.
An engine manufacturer may purchase it.
An aircraft manufacturer may install it.
None of these facts alone determine who owns the certification obligation.
Regulatory responsibility is established through:
- Certification plans.
- Compliance matrices.
- Interface control documents.
- Installation manuals.
- Authority agreements.
Consequently, understanding who physically supplies a component often provides less value than understanding who owns the compliance requirement associated with that component.
The Role of Gap Analysis
One of the most valuable activities during programme planning is a structured gap analysis.
The purpose of gap analysis is not to prove that existing data are inadequate.
The purpose is to establish whether existing evidence already satisfies the applicable certification objective.
Questions commonly include:
- Was the original test representative?
- Does the installation match the certified configuration?
- Are operating conditions equivalent?
- Have airflow conditions changed?
- Have electrical loads changed?
- Are additional hazards present?
Only after these questions have been answered can the existing evidence be confidently reused.
Conclusion
The separation between aircraft Type Certificates and engine Type Certificates is not an administrative detail. It is a deliberate safety architecture that ensures each product is assessed within its intended operational context.
An engine Type Certificate demonstrates that an engine complies as an engine.
An aircraft Type Certificate demonstrates that an aircraft complies as an aircraft.
Neither certificate alone demonstrates that the complete installed propulsion system is safe.
That is why installation compliance exists. It is also why aerospace fire testing is frequently a traceability exercise before it becomes a burner exercise. The critical question is not simply whether a component can withstand fire exposure. The critical question is whether the resulting evidence supports the specific certification finding being sought under the applicable certification basis.
