Instructions for Continued Airworthiness support for installation approval

When this review is needed

• A modification is nearly approved and its ICA was drafted early, before the design settled into its final configuration.
• The safety assessment produced airworthiness limitations that have to appear in the ICA and be maintainable by an operator.
• Parts and consumables introduced by the modification need to be reflected in the maintenance and illustrated parts data.
• A reviewer is expected to check that the ICA covers the installation and carries the required limitations, and the team wants that confirmed first.

The problem

The ICA is written for whoever maintains the aircraft after the modification is approved, but it is usually drafted while the design is still moving. Tasks get written against an early configuration, limitations that emerge late from the safety assessment do not always make it into the limitations section, and parts introduced near the end of the design never reach the parts data. The result is a document that describes a slightly different modification than the one being approved, which the operator inherits.

What gets reviewed

• Maintenance tasks checked for coverage of every serviceable item the modification introduces
• Airworthiness limitations from the safety assessment confirmed present and maintainable
• Parts and consumables data reconciled to the approved configuration
• The configuration the ICA addresses matched to the design being approved
• Task intervals and access requirements checked for consistency with the installation
• A closure plan for tasks, limitations, or parts data that lag the approved design

What gets validated

• Every serviceable item the modification adds has a corresponding maintenance task in the ICA
• Airworthiness limitations from the safety assessment appear in the limitations section verbatim in intent
• Parts and consumables referenced by tasks exist in the parts data at the approved configuration
• The configuration the ICA describes matches the modification being approved, not an earlier draft
• Task intervals and access provisions are consistent with how the installation is actually built

Evidence normally required

• The draft ICA, including maintenance tasks, limitations, and parts data
• The approved modification design and configuration
• Airworthiness limitations produced by the safety assessment
• The parts and consumables list for the installation
• Any operator maintenance program the ICA has to integrate with

Common discrepancies

• A maintenance task written against an early configuration the design later changed
• An airworthiness limitation from the safety assessment absent from the limitations section
• A part introduced late in the design missing from the illustrated parts data
• A task interval or access provision inconsistent with the installed hardware

What is at stake

An ICA that lags the approved configuration leaves the operator maintaining the installation against instructions that do not match it, which surfaces as tasks that reference absent hardware or limitations that were never propagated. At review, a missing airworthiness limitation or an uncovered maintenance task is a direct finding, because the ICA is a condition of the approval and its adequacy is checked, not assumed.

How the work runs

What the buyer receives

• A coverage view of the ICA against the approved modification
• A gap assessment naming where instructions lag the configuration or omit a limitation
• A closure plan for the ICA before the package is submitted

Who uses the output

• Certification project managers confirming the ICA is adequate for approval
• Engineering leads reconciling late design changes into the instructions
• Compliance staff presenting ICA coverage and limitations to the reviewer

How the work fits into the transaction or program

The ICA is the modification's hand-off to the operator and a condition of the approval, so it is reconciled to the design after the configuration settles and the safety assessment closes. Confirming its coverage before submittal keeps a late design change or an unpropagated limitation from becoming both a review finding and an operator problem after the aircraft returns to service.

Jurisdiction-specific considerations

FAA and EASA both require Instructions for Continued Airworthiness with an approved modification, and both require an airworthiness limitations section, but the format expectations and the acceptance route differ between the two systems. The coverage check works to the structure the certification basis for this installation calls for rather than assuming an ICA accepted in one system transfers unchanged to the other.

Regulatory limits

The work checks the ICA for coverage of the approved configuration and for the limitations the safety assessment requires. It does not author the maintenance program, does not set airworthiness limitations, and does not make a compliance finding or grant an approval. The limitations and the compliance determination rest with the applicant and the authority.

What this review does not cover

• Authoring the operator's maintenance program
• Setting the airworthiness limitations or task intervals
• Any compliance finding or approval on the ICA

Specific to this review

• The airworthiness limitations section is the highest-stakes part of the ICA, because a limitation the safety assessment required but the ICA omitted is a direct approval finding.
• ICA drift almost always runs one direction: the design moves late and the instructions, drafted early, are left describing the prior configuration.
• An ICA gap outlives the approval, since the operator maintains the installation against whatever instructions shipped, whether or not they match the aircraft.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits