Sensor ETSO
ETSO compliance evidence support for sensor systems
This support maps a sensor system's evidence against its European ETSO authorization, tracing the requirements, calibration, ARP4754B development data, environmental qualification, and installation effects as an EASA reviewer reads them. A sensor's accuracy claim only holds if its development chain closes and its calibration traceability satisfies the European reading, so this lays that chain against the ETSO reference end to end. An engineer experienced with ETSO sensor submissions runs it during evidence mapping, before an application or against a finding. You receive a standards map, a gap list, and a closure sequence for the article.
When this review is needed
- A sensor system is heading for an ETSO authorization and its requirements trace needs a European-structure read.
- An EASA finding questioned the calibration traceability or an accuracy claim and the answer must reach source data.
- A sensor holding a TSO is being brought to ETSO and its development and calibration evidence must be re-represented.
- An installation study for a European operator changed the error budget and the affected evidence has to be re-mapped.
The problem
A sensor's ETSO case runs from its requirements through the ARP4754B development that derives and validates them, the calibration that anchors its readings to a traceable standard, and the installation effects that reshape its accuracy in place, and all of it must present in the European structure. A supplier who built the chain for the FAA path can find the calibration traceability referenced to a national standard the European reviewer reads differently, or the derived-requirement validation arranged where the ETSO process does not look, so the chain that closed once no longer closes cleanly.
What gets reviewed
- Requirements trace from the sensor's top-level requirements to their verification results
- ARP4754B development data represented for the European reading of derivation and validation
- Calibration traceability tied to a standard the European reviewer accepts
- Installation effects and the sensor error budget reconciled with the declared accuracy
- European article-authorization representation confirmed for the development and calibration structure
What gets validated
- Each top-level requirement traces to a verification result, with none stranded
- Derived-requirement validation is represented where the ETSO structure reads it
- Calibration traceability rests on a standard the European reviewer accepts as current
- The installation error budget stays within the accuracy the article's ETSO claim declares
- Declared DO-160G categories match the conditions the sensor is authorized for
Evidence normally required
- The draft ETSO application or the EASA finding to be answered
- The requirements trace matrix and verification results
- ARP4754B development and validation data
- Calibration procedures, results, and traceability records
- Installation effects analysis and the sensor error budget
Common discrepancies
- Calibration traceability referenced to a national standard the European reviewer reads differently
- Derived-requirement validation arranged where the ETSO structure does not read it
- A top-level requirement with no verification result closing it
- An installation error budget that consumes more accuracy than the ETSO claim allows
What is at stake
A sensor package whose calibration traceability does not satisfy the European reading, or whose derived-requirement validation is hard to follow in the ETSO structure, draws a finding that reaches into development and calibration at once. Because sensors underpin the systems that consume them, a late correction to the accuracy basis can ripple into every function that trusted the sensor's declared error budget.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Lay the chain to the ETSO
Establish the sensor's requirements, development, calibration, and installation basis against the European reference.
Test the trace and validation
Confirm each requirement reaches verification and each derived requirement its validation, represented for the ETSO reading.
Check calibration and error budget
Confirm calibration traceability satisfies the European reading and the error budget respects the claim.
Separate representation from gaps
Distinguish re-representation from missing evidence and sequence both.
What the buyer receives
- A standards map arranging the sensor's development and calibration evidence for the European structure
- A gap list separating missing evidence from evidence that is present but mis-represented
- A closure sequence ordering the trace, calibration, and installation work that remains
Who uses the output
- Certification engineers preparing the ETSO application for the sensor
- Compliance managers deciding which gaps are representation and which are missing evidence
- Engineering leads directing the development and calibration work that closes them
How the work fits into the transaction or program
The mapping runs as the sensor moves toward European authorization, laying the requirements, development, calibration, and installation chain against the ETSO reference so a broken or mis-represented link is caught before submittal. Its gap list drives the re-representation and any real evidence work, and its standards map anchors the finding responses to the European structure.
Start with a single asset
Confirm requirements trace through verification.
Jurisdiction-specific considerations
Calibration traceability that satisfies the FAA reading can rest on a national standard the European reviewer treats differently, so a sensor's accuracy chain may need an additional traceability step or a re-referenced standard for the ETSO path. The mapping separates the calibration work that is genuinely missing from the work that only needs re-referencing for European acceptance.
Regulatory limits
The mapping reads the sensor's evidence chain and reports its state and representation. It does not grant an ETSO authorization, validate a calibration on an authority's behalf, or make an airworthiness determination on the sensor or its installation.
What this review does not cover
- Performing the missing verification, calibration, or installation analysis
- Filing the ETSO application for the supplier
- Any installation or airworthiness determination on the fitted sensor
Specific to this review
- Calibration traceability is the sensor link most exposed under ETSO, because a national reference standard accepted for the FAA path may be read differently for European acceptance.
- Derived-requirement validation is easy to have and hard to find in the wrong structure, so a sound ARP4754B case can still draw a finding on where it sits.
- A sensor's error budget propagates into every consuming function, so a late accuracy correction under ETSO reaches far beyond the sensor itself.
Sources
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
RTCA. Environmental qualification test categories and procedures referenced by TSO and equipment qualification.
RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).
Frequently asked questions
Our calibration was traceable under the FAA path. Does it satisfy ETSO?
Sometimes, but the reference standard behind the traceability can be read differently for European acceptance. The map checks whether the calibration chain rests on a standard the European reviewer treats as current, and where it does not, it identifies the re-referencing or additional traceability step needed rather than a full re-calibration.
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.