ETSO authorization
Means-of-compliance map support for an ETSO authorization
This review examines the means-of-compliance map that connects each ETSO requirement to the method chosen to satisfy it and to the evidence that method will produce. During an EASA European Technical Standard Order authorization, a supplier assigns every requirement a means, whether test, analysis, inspection, or design review, and the map is where that logic lives. A certification specialist checks that each assigned means is accepted for its requirement and that a real evidence path leads from it rather than a label with nothing behind it. You get a gap assessment, an evidence map tracing requirement to method to record, and a closure plan for the paths that dead-end.
When this review is needed
- A supplier has assigned a means to every requirement and wants the assignments checked before evidence is generated.
- Some requirements were assigned a means of analysis where the authority expects test, or the reverse.
- The article's requirements changed and the map has not caught up with the new set.
- A team wants to confirm each means actually leads to a producible record before it commits budget.
The problem
Assigning a means is quick; making it real is not. A requirement gets tagged as shown by analysis because that seemed lightest at the time, but no analysis is ever scoped, or the analysis that runs cannot actually demonstrate the requirement. The map reads as complete because every requirement has a method beside it, yet several of those methods lead nowhere. The failure is invisible until someone follows a path to its supposed evidence and finds an empty file.
What gets reviewed
- Every ETSO requirement checked for an assigned means in the map
- The chosen method tested against what the authority accepts for that requirement type
- The evidence path from each means to a specific producible record
- Requirements that carry a means label but no scoped work behind it
- Consistency between the map and the compliance matrix that reports its results
- Reassignments needed where the chosen method cannot demonstrate the requirement
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
- Each requirement carries a means and none is left without an assigned method
- The assigned method is one EASA accepts as demonstrating that specific requirement
- A method of analysis names the analysis that will run, not merely the intent to analyze
- Every means leads to a record type that the program can actually produce
- The methods in the map agree with what the certification plan committed
Evidence normally required
- The means-of-compliance map at its current revision
- The full requirement set for the article and its latest changes
- The invoked ETSO and its minimum performance standard
- The certification plan's declared compliance approach
- Any scoped test or analysis procedures produced so far
Common discrepancies
- Requirements tagged shown by analysis with no analysis ever scoped
- A method assigned that cannot actually demonstrate the requirement it sits against
- New or changed requirements missing from the map entirely
- Map entries that contradict the means the certification plan committed
What is at stake
A method that cannot produce its evidence has to be reassigned mid-program, and reassignment ripples: a requirement that moves from analysis to test needs a test article, a procedure, and schedule the program did not plan. Discovered near submittal, one broken path can hold a whole requirement group while the replacement evidence is generated from scratch.
How the work runs
Inventory the requirements
Confirm every current ETSO requirement, including recent changes, appears in the map with an assigned means.
Test each method
Check that the assigned method is accepted for its requirement and can actually demonstrate it rather than merely label it.
Follow the path
Trace each means to the specific record it will produce and flag the ones that lead nowhere.
Plan the reassignments
Deliver a gap assessment and a closure plan for the dead-end paths and the work they now require.
What the buyer receives
- A gap assessment of requirements with a broken or missing evidence path
- An evidence map tracing requirement to method to the record it will produce
- A closure plan naming the reassignments and scoped work each dead-end needs
Who uses the output
- Compliance managers confirming the map before evidence generation starts
- Certification leads deciding which methods to commit budget to
- Engineers scoping the test and analysis the map implies
How the work fits into the transaction or program
The map is the bridge between requirements and evidence, and it is cheapest to fix before the evidence work begins. Checking that every method is both accepted and producible means the program funds test articles and analyses that will actually close requirements, rather than discovering near submittal that a chosen method was never going to reach its record.
Start with a single asset
Reduce finding cycles by checking the package first.
Jurisdiction-specific considerations
EASA has expectations about which methods demonstrate which ETSO requirements, and those expectations can differ from an FAA reading. The review checks each assigned means against EASA acceptance for the invoked ETSO, so a method that would pass under one authority is not assumed acceptable under the other.
Regulatory limits
The review evaluates the supplier's assignment of methods to requirements. It does not accept the means of compliance on EASA's behalf, grant an authorization, or determine that any method is sufficient in the authority's judgment. Those determinations stay with EASA.
What this review does not cover
- Accepting the means of compliance on the authority's behalf
- Performing the tests or analyses the map assigns
- Writing the article's requirements
Specific to this review
- A means-of-compliance map can be one hundred percent populated and still be broken, because a populated cell only proves a method was named, not that it produces evidence.
- Reassigning a requirement from analysis to test late in a program pulls in a test article and procedure, so a broken path found near submittal costs far more than the same path found at map stage.
- EASA acceptance of a method is requirement-specific, so a supplier cannot rely on a method having been accepted elsewhere for a different requirement.
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).
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
Frequently asked questions
The map is fully populated. Why would it need review?
A full map only shows every requirement has a method beside it. Review confirms each method is one EASA accepts for that requirement and that it leads to a record the program can actually produce, which is where populated maps most often fall short.
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.