Almost everything written about DO-178C assumes you are dealing with the FAA. The objectives tables are the same wherever you are, but the route to an approval, the people who hold the authority, and the regulations your evidence is ultimately answering to are not.
If your programme is Canadian — or you are a foreign supplier selling into one — this is the orientation that the published literature does not give you.
Who you are actually dealing with
The authority is Transport Canada Civil Aviation (TCCA), the civil aviation arm of the federal Department of Transport. It certifies aeronautical products designed in Canada and validates approvals issued elsewhere.
The legal instruments are the Aeronautics Act and, under it, the Canadian Aviation Regulations (CARs). Airworthiness sits in Part V. That is the chain your software evidence eventually answers to — not to DO-178C, which is a means of compliance rather than a regulation, in Canada exactly as everywhere else.
CAR 521 — and the stale references you will meet
Type design approval today runs under CAR 521, which sets out application, certification basis, compliance demonstration and the issuance of approvals.
The vocabulary problem
Much of the friction for teams arriving from US programmes is simply that the words differ. The concepts map closely; the terms do not.
| Canada (TCCA) | United States (FAA) | Europe (EASA) | |
| Design approval framework | CAR 521 | 14 CFR Part 21 | Part 21 |
| Approval issued | Type Certificate / Supplemental Type Certificate | Type Certificate / STC | Type Certificate / STC |
| Individual delegate | DAR — Design Approval Representative | DER — Designated Engineering Representative | Privileges held by the approved organisation |
| Organisational delegate | DAO — Design Approval Organization | ODA — Organization Designation Authorization | DOA — Design Organisation Approval |
| Airborne software | RTCA DO-178C accepted as a means of compliance | RTCA DO-178C, recognised via FAA advisory material | EUROCAE ED-12C, recognised via EASA acceptable means of compliance |
Delegation, and what it means for your evidence
TCCA does not review every compliance finding itself. Authority is delegated under the Aeronautics Act — a Design Approval Representative is an individual authorised to make findings on the Minister's behalf, and a Design Approval Organization holds equivalent authority at the organisational level. The Airworthiness Manual's delegation chapter governs how that works.
The practical consequence for a software team is the one people miss: your evidence is very often read first by a delegate, not by a TCCA engineer. That does not lower the bar. It does mean the working relationship, the review rhythm, and how findings get raised and closed are shaped by whoever holds the delegation on your programme — and it is worth knowing which model applies before you write your PSAC, not after.
The standard itself does not change
To be unambiguous: DO-178C is the same document in Canada. The five levels, the objectives tables, independence, structural coverage, the supplements — none of it is different. A team that has certified under the FAA has not learned a different craft.
What differs is the frame around it: which regulation the compliance ultimately answers to, who holds the authority to accept a finding, how the engagement is structured, and — the part that matters commercially — how the resulting approval travels.
Getting a Canadian approval recognised elsewhere
This is usually the question behind the question. A Canadian supplier does not want an approval that stops at the border, and a foreign supplier wants to know what its existing approval buys in Canada.
| Partner | Instrument | Established | What it does |
| United States | Agreement for Promotion of Aviation Safety (BASA), with Implementation Procedures for Airworthiness (IPA) authorised under Article III | Agreement signed 12 June 2000; IPA currently at Revision 3 | Governs how TCCA and FAA accept and validate each other's design approvals |
| European Union | Canada–EU Bilateral Aviation Safety Agreement | Signed 6 May 2009; in force 26 July 2011 | Provides for EASA recognition of Canadian approvals and the reverse |
The important nuance is that validation is not one thing. Depending on the product and the agreement, recognition can range from acceptance requiring no separate application, through a streamlined validation, to a full technical review. The engineering consequence is direct: whether your DO-178C evidence will be re-examined by a second authority, and in how much depth, is knowable at the start of a programme. Find out then, because it changes what you keep, how you write it, and in which language.
If you are a supplier entering a Canadian programme
- Establish the delegation model early. Whether findings run through a DAR, a DAO, or TCCA directly shapes your engagement plan and your PSAC.
- Do not assume your FAA relationship transfers. The technical work does. The authority to accept a finding does not.
- Ask about validation at kickoff, not at the end. If the product will be validated by another authority, that is a planning input, not a closing task.
- Check that your process documents cite current regulations. AWM 511 references are the tell.
- Budget for French. On Quebec programmes it is not a translation line item at the end; it is a delivery requirement.
Why this matters more now
Canadian industrial, defence and security programmes are increasingly being sourced domestically. That pushes certification work toward Canadian suppliers, a good number of whom have strong engineering and no DO-178C capability yet, and toward foreign firms who need a Canadian route for the first time.
For those firms the standard is the easy part. The frame around it — which authority, which delegate, which regulation, which validation route, which language — is what is not written down anywhere convenient. That is the gap this article exists to close, and there will be more of them.
Frequently asked questions
Is DO-178C different in Canada?
No. It is the same RTCA document with the same objectives. What differs is the regulatory frame it sits in, who holds the authority to accept a compliance finding, and how the resulting approval is recognised by other authorities.
Does TCCA accept an FAA approval?
Canada and the United States have a bilateral safety agreement whose Implementation Procedures for Airworthiness govern how each authority accepts or validates the other's design approvals. The effort involved varies by product and route, so treat it as something to confirm for your specific case rather than assume.
What is a DAR?
A Design Approval Representative — an individual authorised under the Aeronautics Act to make compliance findings on the Minister's behalf. The closest US counterpart is a DER, though the constructs are not identical.
Do we need to produce our certification evidence in French?
The requirement depends on your customer and the programme, not on TCCA as such. In practice, suppliers working with Quebec primes should plan for French as a delivery language rather than treat it as an afterthought.
We are a Canadian SME with no DO-178C experience. Where do we start?
With the planning documents and the delegation model, in that order. Most of the schedule risk on a first programme is created at planning time, long before any code is written, and it is much cheaper to get help there than to retrofit evidence later.
We work on Canadian certification programmes in both official languages. If you are scoping one, or entering the Canadian market for the first time — get in touch.
