Field approval, continued airworthiness
Field-approval instructions for continued airworthiness support
This support readies the Instructions for Continued Airworthiness that a field-approval installation has to carry into service. It checks that the maintenance tasks, airworthiness limitations, parts data, and applicability in the ICA match the approved configuration and cover everything the modification introduces. An ICA-focused engineer runs it before submission. The result is a gap assessment of the ICA against the approved configuration, a trace from each limitation back to its source, and a plan to close the tasks and limitations that trail the design.
When this review is needed
- A modification adds equipment that needs its own maintenance tasks and the ICA has to reflect them.
- The design changed after the ICA was drafted and the instructions still describe the earlier build.
- Airworthiness limitations came out of the safety assessment but never made it into the ICA.
- An operator has to maintain the installation and the ICA is the document that will govern that work.
The problem
The ICA is often the last document written and the first to fall behind, because the design keeps moving after the instructions are drafted. Airworthiness limitations that come out of the safety assessment have to land in the ICA intact, and a limitation that is analyzed but never published is a limitation nobody will follow. The operator inherits whatever the ICA says, so a gap between the approved configuration and the instructions becomes a maintenance gap in service.
What gets reviewed
- Maintenance tasks covering the equipment and systems the modification introduces
- Airworthiness limitations traced from the safety assessment into the ICA
- Parts data, including part numbers and interchangeability, for the installed items
- Applicability and effectivity so the ICA reaches the right aircraft and configuration
- Consistency between the ICA and the approved configuration the package establishes
- Format and integration so the instructions can be used in the operator's program
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Identify what is missing against the means of compliance.
What gets validated
- Every system the modification introduces has a corresponding maintenance task in the ICA
- Each airworthiness limitation from the safety assessment appears in the ICA intact
- Parts data in the ICA matches the approved configuration's part numbers and revisions
- Applicability and effectivity direct the ICA to the correct aircraft and configuration
- The ICA describes the configuration the package actually approves, not an earlier build
Evidence normally required
- The draft Instructions for Continued Airworthiness
- The airworthiness limitations from the safety assessment
- The approved configuration definition and parts data for the installation
- The maintenance tasks and intervals proposed for the modification
- Applicability and effectivity for the covered aircraft
Common discrepancies
- A system introduced by the modification with no maintenance task written for it
- An airworthiness limitation analyzed in the safety assessment but absent from the ICA
- Parts data in the ICA that references a superseded revision of the installation
- Applicability that does not match the effectivity of the approved configuration
What is at stake
An ICA that lags the approved configuration leaves the operator maintaining the installation to the wrong instructions, and a missing airworthiness limitation can put the aircraft outside its approved envelope without anyone noticing until an audit. A reviewer who sees the ICA does not cover the modification will hold the field approval until it does.
How the work runs
Map the modification to tasks
Confirm every system the change introduces has a maintenance task in the ICA covering it.
Carry the limitations across
Trace each airworthiness limitation from the safety assessment into the ICA intact.
Reconcile to configuration
Check parts data and applicability against the approved configuration the package establishes.
Close the lag
Sequence the tasks and limitations that trail the design so the ICA matches what is approved.
What the buyer receives
- A gap assessment of the ICA against the approved configuration
- An evidence map from each airworthiness limitation to its source in the assessment
- A closure plan for the tasks and limitations that lag the design
Who uses the output
- Engineering leads confirming the ICA covers everything the modification introduces
- Compliance managers submitting an ICA consistent with the approved configuration
- Maintenance leadership who will run the operator's program from these instructions
How the work fits into the transaction or program
The ICA is where the field approval hands off to continued airworthiness, so this review sits at the tail of the package and pulls forward from the safety assessment and configuration work. It confirms the instructions match what was approved before the operator inherits them, closing the seam between certification and in-service maintenance.
Start with a single asset
Reduce finding cycles by checking the package first.
Jurisdiction-specific considerations
An installation later carried onto an EASA register has to satisfy continuing-airworthiness requirements the FAA ICA was not written against, so the review notes where the instructions would need rework for the receiving system rather than assuming they transfer as written.
Regulatory limits
The review confirms the ICA covers the modification and matches the approved configuration, and flags the places it falls short. Approving the ICA, accepting it into an operator's program, making a compliance finding, and ruling on airworthiness all remain outside its scope.
What this review does not cover
- Authoring the maintenance program the operator will run
- Approving the ICA or its airworthiness limitations
- Judging whether the modified aircraft is airworthy
Specific to this review
- An airworthiness limitation analyzed but never published in the ICA is a limitation no operator will actually follow.
- The ICA is usually the last document drafted, so it is the one most likely to lag a design that kept changing.
- The operator maintains the installation to whatever the ICA says, so a gap here becomes an in-service maintenance gap.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
Frequently asked questions
Why review the ICA separately from the rest of the package?
The ICA governs how the installation is maintained after approval, and it lags the design more often than any other document because it is written last. Reviewing it on its own confirms the airworthiness limitations and maintenance tasks reached the operator intact, rather than being lost between the analysis and the published instructions.
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.
Talk through the aircraft, records, evidence, deadline, and next useful step.