An aerospace validation strategy is the plan that shows how a programme will demonstrate, before certification and entry into service, and that its airborne electronics meet the requirements in real-world conditions. It sets out which evidence is needed, who produces it, where it is produced and in what order. Planning early can reduce rework, retesting and laboratory rescheduling. If the evidence plan is left until the formal campaign, gaps may emerge when the design is harder to change.
This post closes Ignitec’s Aerospace series. It follows the Aerospace Design Assurance Documentation post and brings together the layers covered in the related posts: the certification basis, environmental qualification, component selection, test rigs and design assurance records. It is written for two readers. Engineers will find a sequence for planning evidence and a way to identify what the combined evidence still does not demonstrate. Programme managers and buyers will find the cost and schedule risks, the supplier boundaries that decide who owns which evidence, and five questions to put to a design partner.
What does an aerospace validation strategy cover?
The word validation is used in two senses. In development assurance guidance such as SAE ARP4754, verification and validation are separate activities. Verification checks whether the design implementation meets its specified requirements, while validation considers whether the requirements and resulting system meet intended needs and operational context. In programme conversations, validation is also used more loosely for the work linking requirements, qualification and evidence. This post uses the broader sense for the overall strategy and identifies the narrower development-assurance meaning where it matters.
A validation strategy can sit above the individual plans as a working integration document. The system safety assessment, Plan for Hardware Aspects of Certification (PHAC), software plans, environmental test plan and laboratory procedures each cover part of the evidence. The strategy shows how they fit together: which requirement is addressed by which evidence, who owns it, which baseline it applies to, and what depends on what. A document specifically called a validation strategy is not required under every certification basis, so confirm the required plans and data items with the customer or certification contact.
Evidence layers in an aerospace validation strategy
The related posts cover different layers. The table summarises the question each layer addresses, the evidence it can produce and where to read more. The certification guide is included as the foundation for the five specialist posts in this synthesis.
|
Certification basis and environment |
What must be shown, to whom, and for which installation? |
Agreed standards and revisions, installation and environment assumptions, certification plan |
Aerospace Electronics Validation: An Engineer’s Guide to Certification |
|
Environmental qualification |
Does the unit perform under the defined environmental conditions? |
Test plans, procedures, reports and qualification forms |
DO-160 Electronics Testing for Engineers: Scoping Environmental Qualification; Aerospace Vibration Electronics: Designing for Vibration and Shock Qualification |
|
Component and sensor selection |
Will critical parts perform in the installed environment, and can they be supplied? |
Installed-environment data, qualification evidence, integrity and failure-mode information, export and supply information |
Aerospace IMU Selection: How to Choose an Inertial Measurement Unit for Airborne Systems |
|
Test rigs and laboratory |
Does the set-up represent the installation and produce traceable evidence? |
Fixture and monitoring records, calibration records, accreditation scope, configuration records |
Test Rigs for Aerospace Validation |
|
Design assurance records |
Was the design developed with rigour appropriate to its safety impact? |
Plans, requirements and design data, traceability, verification results, accomplishment summaries |
Aerospace Design Assurance Documentation: Planning the Evidence for Airborne Electronics |
The table is a planning aid. The layers a programme needs depend on the equipment, certification basis and agreed means of compliance. DO-160 is one environmental reference among several; some programmes use customer specifications or another environmental standard.
Environmental qualification shows how a unit performs under defined laboratory conditions. It does not replace the safety assessment, system-level integration evidence or design assurance records. The 2013 Heathrow transmitter fire, discussed in the DO-160 post, illustrates why environmental test evidence should not be treated as a complete assessment of every hazard associated with a product and its installation.
Sequencing an aerospace validation strategy: From certification basis to change control
Decisions about the certification basis and installed environment inform later design and test choices, although the strategy needs to accommodate iteration as the programme develops. A programme can work through six connected steps:
- Define the certification basis and the installed environment: Record the aircraft type, installation location, equipment function, applicable standards and revisions, and the assumptions behind them. Agree these with the customer or certification contact. Environmental categories, the assurance approach, and the test scope follow from this record and may need review as the design develops.
- Allocate assurance and plan the evidence: Use the system safety assessment to inform the development assurance approach, including the objectives and independence that apply under DO-178C or DO-254 where they are in scope. List the plans and data items required by the agreed approach and when each is due.
- Select architecture and critical components against the installed environment: Compare candidates on installed performance rather than datasheet figures alone. As the IMU post showed, vibration rectification, integrity monitoring and qualification evidence can change a shortlist. Export classification and supply constraints also affect procurement planning, although they are separate from technical suitability. Replacing a sensor late can reopen interface, calibration, software and test work.
- Run pre-compliance work on representative hardware: Resonance searches, emissions checks and fixture surveys, where relevant to the equipment and installation, can show whether the design behaves as predicted before the formal campaign is booked. They do not replace the agreed qualification programme.
- Plan the rigs, laboratory and records, then run the formal campaign: Confirm that fixtures and mounting represent the relevant installation features, that the laboratory’s accreditation scope covers the planned methods and tests, that calibration records are valid for the test dates, and that acceptance criteria are defined before testing starts. Accreditation alone does not establish regulatory acceptance of every report; confirm the applicable scheme and customer or certification arrangements.
- Control change after qualification: Record the baseline to which the evidence applies and assess each change against affected requirements, the safety assessment and dependent tests. The extent of reassessment or retesting depends on the change and the applicable certification arrangements; agree the review route with the customer or certification contact.
|
🛠️ DESIGN CONSIDERATION Keep the strategy short enough to be read by the programme manager, the test engineer and the certification contact. A single table that maps each requirement to its planned evidence, owner, laboratory and baseline lets gaps be seen early. Review it whenever the requirements, the installation or the applicable revision change. |
Where gaps appear between layers (and how to check the interfaces)
Different teams, suppliers or specialist laboratories may contribute to the evidence, and a single organisation may own several layers. Gaps can emerge when one team’s output becomes another team’s input. Four interfaces are worth checking in a strategy review:
- Environment and test scope: Test categories are selected from the intended installation and operating environment. If the assumed environment changes after design decisions are fixed, the categories, design margins, or evidence needed may also change.
- Design and test rig: Mounting, board support, connector retention and harness clamping can shape the vibration response. A rig that replaces the bracket, isolators and harness with a rigid plate and short cable may test a different configuration from the installed one.
- Component data and installed performance: Datasheet figures are measured under defined conditions. Compare the available data with a spectrum and operating conditions relevant to the installation, and consider testing a shortlisted sensor on a representative mount before the selection is frozen.
- Evidence and baseline: If the product changes and the records do not, the documentation may no longer describe the configuration being built or assessed. The programme needs a way to identify affected evidence and decide whether analysis, additional testing or formal review is required.
A practical evidence-gap check
For each important system requirement or safety-related assumption, ask five questions: (1) What requirement or operational need must be demonstrated? (2) Which evidence addresses it, and what does that evidence actually prove? (3) Does it cover the relevant hardware/software baseline, installation interfaces and operating conditions? (4) Are acceptance criteria, anomalies and limitations documented and resolved? (5) Which assumptions, dependencies or failure responses remain untested or supported only by analysis? If an answer is unclear, record the gap, its owner, the proposed closure method and the decision deadline. This check does not require every question to be answered by a physical test: analysis, simulation, inspection and test may contribute different parts of the evidence.
|
⚠️ CRITICAL ALERT RTCA’s current DO-160 page still identifies DO-160G as the current version, but its listed DO-160H publication target of March 2026 has passed. Confirm directly with RTCA whether DO-160H has been issued or the timetable has changed before publication. FAA AC 21-16G identifies versions D through G as acceptable environmental qualification references and encourages DO-160G for new articles. SAE has published ARP4754B, while FAA AC 20-174 continues to recognise ARP4754A as an acceptable development assurance method. Publication of a newer revision does not by itself establish acceptance for a particular certification programme. State which revision applies to each layer and agree how a later revision will be handled. |
Bought-in equipment and supplier boundaries (who owns which evidence)
Bought-in equipment moves some evidence outside the programme’s direct control, but it does not automatically transfer the integrator’s responsibilities. Supplier design data may support the integrator’s work without establishing acceptability for the intended installation or closing every assurance gap. A strategy should state the split explicitly for each bought-in item:
- Evidence supplied and gaps retained: For each purchased device or module, list the qualification and design assurance data the supplier can provide, and identify the gaps the integrator still needs to close.
- Baseline of the supplied item: Record the hardware and software baseline covered by the supplier’s evidence, and agree how changes, obsolescence and end-of-life will be notified and assessed.
- Ownership of fixtures and data: Agree who owns fixtures, rig software and test data, and which configuration records will be handed over for later campaigns or design changes.
- Export and supply: Confirm the export classification and supply route of the item and finished system. A component’s classification does not automatically determine the status of every product that incorporates it.
What can gaps between layers cost a programme?
A gap found during formal testing or review can mean redesign, rework, repeat testing and another laboratory booking. Laboratory time is a planning constraint. Element’s guidance gives approximate planning durations for simple equipment: one shift for DO-160 vibration Category S, two shifts for fixed-wing Category R and six shifts for helicopter Category U. These are laboratory estimates, not DO-160 requirements. Larger or more complex units can take longer, and retest timing depends on laboratory availability. For a high-risk section, consider whether the programme schedule needs contingency for a repeat campaign.
|
Certification basis and environment |
Agreed categories, revisions and installation assumptions |
Test scope and design margins may change after the design is frozen |
|
Assurance allocation |
Plans and data items matched to the agreed approach |
Completed work may need to be reviewed again |
|
Component and sensor selection |
Installed-environment data and qualification evidence |
A late sensor change can reopen interface, calibration, software and test work |
|
Pre-compliance |
Resonance, emissions and fixture results on representative hardware |
Problems found in the formal campaign, with redesign and another laboratory booking |
|
Rigs and laboratory |
Fixture, calibration, accreditation scope and configuration records |
Evidence questioned, or repeat testing |
|
Change control |
Baselines and change impact records |
Evidence that no longer describes the product |
The evidence required for a programme depends on the equipment, assurance level and certification basis.
A strategy cannot remove technical or scheduling risk. It can expose unresolved assumptions while the design is still changeable and give buyers a basis for comparing suppliers on how evidence will be produced, assessed and maintained.
What the series case studies have in common (and what they do not prove)
The related posts use different case studies to illustrate particular layers. Read together, they show recurring questions about how assumptions, interfaces, test inputs and evidence baselines are managed. They do not establish that every failure was caused by the same weakness.
|
2013 Heathrow transmitter fire (DO-160 post) |
The AAIB investigation traced the fire to the ELT battery; crossed and trapped battery wires were identified as a probable short-circuit path. The case illustrates the limits of treating environmental qualification as a complete assessment of installation and battery hazards. |
Battery design, installation and safety assessment |
|
Engine wiring harness fretting (vibration post) |
The reported fretting damage illustrates that harness support, span and vibration response can interact. The precise failure mechanism should be understood in the context of the conditions documented in the original investigation or study. |
Harness design, mounting and vibration environment |
|
Qantas flight 72 (IMU post) |
The ADIRU produced intermittent erroneous data spikes; the flight-control computers could not handle the specific pattern of angle-of-attack spikes. The lesson concerns both sensor behaviour and downstream system response, not simply a failure of built-in test. |
Sensor failure behaviour and host-system response |
|
Ariane 501 (test rigs post) |
The inquiry identified shortcomings in the testing and analysis of the inertial reference system under Ariane 5 flight conditions. The failure involved reused software and assumptions about the flight profile, not only the representativeness of a test rig. |
Software assumptions, analysis and representative testing |
|
Boeing 737 MAX (documentation post) |
Investigations and reviews identified shortcomings in MCAS safety assessment and the certification information describing the system’s functionality and assumptions about pilot response. The case involves safety assessment and certification-process issues, not documentation in isolation. |
Safety assessment, system functionality and certification evidence |
Across the cases, the useful common thread is the relationship between an assumption and the system or conditions to which it was applied. The assumption might concern a hazard, a mounting configuration, a sensor failure mode, a test input or a design baseline. The engineering lesson is to examine those dependencies alongside the evidence for each layer. Air France 447, discussed next, provides a separate example concerning knowledge of the operating environment.
The cases differ in kind: they include accident investigations, a research study and a launch failure. None supports a single-cause reading, and the table should be read as a set of bounded lessons rather than proof of one universal failure mechanism.
Case Study: Air France 447 and the Gap Between a Certification Envelope and the Sky
On 1 June 2009, an Airbus A330-203 operating as Air France flight AF 447 crashed into the Atlantic Ocean on a flight from Rio de Janeiro to Paris, killing all 228 people on board. The French investigation authority, the BEA, issued its final report on 5 July 2012. The sequence is described in the BEA’s presentation of the report and Aviation International News, which report that the sequence began with inconsistent measured airspeeds, likely following obstruction of the pitot probes by ice crystals, and autopilot disconnection. Subsequent control inputs destabilised the flight path. The investigation also examined crew training, task sharing and the handling of unreliable airspeed information; the BEA issued 41 safety recommendations, as recorded in ASN’s summary.
The relevance to validation strategy is limited to the assumptions made about the operating environment. The BEA concluded that pitot-probe obstruction by ice crystals in cruise was known but not well understood by the aviation community at the time. Later, EASA’s decision adopting CS-25 Amendment 16 noted that large aeroplanes operating in icing conditions could encounter environmental conditions that the CS-25 provisions at the time did not address, or addressed only in part. The amendment introduced requirements concerning additional icing conditions, including ice-crystal and mixed-phase icing, and required applicants to demonstrate safe operation in the specified conditions.
This was not a failure of an electronics test programme, and the investigation identified contributing factors beyond the probes. The case does not show that a product failed a required qualification test or that a deficient electronics validation strategy caused the accident. Its narrower relevance is the distinction between demonstrating compliance with defined requirements and checking whether those requirements adequately represent conditions encountered in service. A standard defines specified test conditions; operational experience can reveal conditions or interactions that were not adequately understood when the requirements were set.
For a programme, record the environmental assumptions behind each relevant requirement or test category and define when in-service information, customer feedback and changes to the certification basis will be reviewed against them. If new information challenges an assumption, record the impact assessment and identify which requirements, analyses or tests may need to be revisited.
Questions to ask a design partner about validation strategy before you commit
Programme managers and buyers can assess whether a design partner works to an integrated evidence strategy or only to a list of tests by asking five questions:
- Certification basis and environment: How will the certification basis, installation environment and applicable revisions be recorded and agreed, and how will the assumptions behind them be reviewed as the programme learns more?
- Evidence plan: For each requirement, can you show the planned evidence, who produces it, where it will be produced and which baseline it applies to? For bought-in items, which evidence comes from the supplier and which gaps remain with the integrator?
- Representativeness: Which parts of the installation and which electrical or data interfaces will the test set-ups include, and where do simulations or stand-in equipment replace the real system?
- Independence and records: Which verification objectives require independence at the assigned assurance level, and what calibration, configuration, traceability and anomaly-disposition records will be handed over?
- Change and retest: How are changes assessed against the safety analysis and affected plans, who carries the retest and laboratory rescheduling risk, and what happens if a new revision of a standard is published during the programme?
Final Thoughts
An aerospace validation strategy links the certification basis and installed environment to assurance planning, component selection, test configurations and a controlled evidence baseline. It helps a programme see what each activity demonstrates and what remains dependent on assumptions or evidence from elsewhere.
The cases in this series do not share one cause. They show why the evidence needs to be assessed against the system, installation, failure behaviour and assumptions it is intended to cover. Before committing to a design or test plan, ask what requirement each item of evidence closes, which configuration and conditions it represents, what limitations remain, and who will resolve them. Where the answer is unclear, the gap should be recorded with an owner, a closure method and a decision date.
|
WORK WITH IGNITEC Ignitec’s engineers support airborne electronics programmes from early design through to qualification planning. If you are building a validation strategy, we can review your certification basis, evidence plan, test set-ups and change control, and identify gaps between them before you commit to a test plan and a laboratory. |
Contact the team to discuss your programme and validation strategy.


