Certification, qualification and acceptance: different questions

Aircraft design certification concerns the applicable airworthiness requirements and an identified design. Qualification establishes suitability against defined criteria for a particular device, component or purpose. Contractual acceptance concerns the agreement and its acceptance provisions. Operational readiness also depends on matters such as trained personnel, procedures, maintenance and support. None of these labels should be used as a substitute for understanding scope. The same report can support more than one process when its conditions fit, but the decisions remain distinct.

Why this case matters

A project meeting uses the words certified, qualified and accepted as if they mean the same thing. A test result may be valuable in all three discussions, but the claims and decision makers differ. This lesson helps you turn a broad statement such as “the system passed testing” into an exact statement about what was demonstrated, in which configuration, against which criteria and for which purpose.

Follow the evidence

Showing and Finding in the TAA System

The TAM's type certification process (Part 2, Ch. 1, paras. 2.1.1.2-2.1.1.3) divides the labour the same way every credible certification system does. The applicant - typically the prime contractor working the acquisition project, supported by its design organization - conducts the Compliance Program: the inspections, analyses and tests that demonstrate compliance with each element of the certification basis, documented in a compliance matrix with agreed means and methods of compliance and capped by function and reliability testing. The finding of compliance is made by the TAA or on the TAA's behalf. That "on behalf of" is organizationally delegated, not personally licensed: individuals within TAA-accredited or acceptable organizations may be "assigned technical airworthiness authority directly by the TAA to make findings of compliance and/or grant airworthiness approval in speciality engineering areas, similar to that of a Transport Canada Design Approval Representative" (TAM Part 1, Ch. 4, para. 1.4.1.5) - note the TAM cites the civil DAR title only by analogy; the DND instruments are the Authorized Individual and the Senior Design Engineer (SDE) of an Acceptable Technical Organization or Acceptable Design Organization. Collapsing the showing into the finding - an applicant certifying to itself - is as much a failure mode here as in any civil program; the accreditation system exists precisely to keep the finding authority traceable to the TAA.

Conformity Before Test - the TAA Version

Compliance data is only as good as the article that produced it. The TAM's compliance program expects the applicant to establish that test articles conform to the design definition being certified before certification testing, to give the TAA access for the inspections and tests it requires, and to sequence the work: conform, then test, then report, then finding. In the military system this discipline has an extra wrinkle - the test aircraft is frequently a prototype or instrumented asset owned by the Crown or the contractor, flying under an Experimental Flight Permit rather than a CofA, sometimes before the type certificate exists at all. The flight authority question (which permit, issued by whom, with what limitations) is therefore part of test planning, not an administrative afterthought: an engineering flight test flown without a valid EFP produces data the TAA cannot use and risk the FTA will not accept.

The compliance matrix is the working artifact that ties this together. In DND practice it records, for each element of the certification basis: the agreed means and methods of compliance; the compliance document that will carry the evidence (with revision control); the organization producing it; and the finding authority. The TAM expects the applicant's compliance program to culminate in function and reliability testing for a type certification - the operational-representative proving that complements the paragraph-by-paragraph evidence - and expects findings of compliance to be made by or on behalf of the TAA throughout, not batched at the end. A well-run matrix is therefore a scheduling tool as much as a technical one: rows close in the order the finding authorities can actually sign, and the critical path runs through the rows only the TAA itself will find - typically the novel, contested or high-consequence items that Issue Papers under Advisory 2023-01 exist to resolve.

Certification vs Qualification - Draw the Line and Hold It

The ADSM separates two acts that civilian engineers routinely conflate: "Generally, type-certification is considered to be a pre-requisite to qualification. Type certification focuses exclusively on aviation safety-related requirements, while qualification expands the scope to encompass all of the aircraft system performance and mission capability requirements... The TAA's role is to regulate and oversee the type certification process, while qualification is entirely the responsibility of the project manager" (ADSM 1.3.2(3)-(5)). Practically: the radar's airworthiness interfaces - electrical load, structural mounting, failure effects - are certification scope and belong on your compliance matrix; the radar's detection range against a reference target is qualification scope and belongs to the project office's contractual demonstration. Both must close before Release to Service, but they close to different authorities against different requirements, and a finding in one domain proves nothing in the other. This is also where the terminology trap from Day 7 bites hardest: the CH-47F was "designed and certified (qualified)" by the US Army to ADS-51 - a *qualification* handbook - and the TDE still had to examine that work against airworthiness criteria before credit could flow (ADSM 1.3.12(1)). Qualification evidence can be excellent; it is not certification evidence until the TAA says so.

The certification/qualification line also runs through the test enterprise itself. AETE flies two kinds of programs: engineering flight test supporting the TAA's certification findings - envelope expansion, stores clearance substantiation, handling and performance evidence against the certification basis - and operational test and evaluation supporting the OAA's Operational Airworthiness Clearance and Release to Service. Same runway, same instrumented aircraft sometimes, different authority, different requirement set, different flight authority context: the engineering sorties ride the EFP under FTA oversight; the operational evaluation feeds the OAA's clearance judgment. Historically the engineering role is long-standing - the CF-188 480-gallon external fuel tank certification program is the documented example of the CAF flight test authority executing a certification test campaign. When you write the flight-test rows of a compliance matrix, write them for the TAA's finding; the operational evaluation is planned beside them, not instead of them.

Twelve-minute project workshop

• Spend three minutes writing four claims: aircraft design compliance, simulator qualification, contractual acceptance and operational readiness. Name the evidence each claim needs.
• Spend four minutes reviewing the two test configurations. Identify relevant differences and explain whether each matters for its intended claim.
• Spend three minutes rewriting the project slide with bounded language. Keep achievements visible while identifying the approval work that remains.
• Spend two minutes drafting a question for the responsible authority rather than choosing an approval instrument yourself.

Compare your reasoning

A careful rewrite records the training-device qualification and contract demonstration as achievements within their scopes. It does not infer aircraft certification from them. The aircraft result needs traceability to requirements and an applicable configuration; the simulator baseline needs review against its qualification and training purpose. Do not conclude that the tests are worthless. Explain what they substantiate and what further evidence or decisions are needed. Transport Canada simulator guidance is an analogy for the distinction, not the authority governing Canadian military aircraft certification.

Keep your worksheet as an optional learning aid. It is not submitted or graded. The practice below has no pass mark and does not affect core course completion.