DCT vs. SOC: When the FAA Wants More Than Answered DCTs

When an FAA inspector asks for “the compliance picture,” they may want answered Data Collection Tools (DCTs) — element-by-element answers that map specific procedures to the manual suite. Or they may want a Statement of Compliance (SOC) — a single, regulation-by-regulation traceback that demonstrates the operation satisfies 14 CFR Part 135 end-to-end. The two are not redundant; they answer different inspector questions. This guide walks through when each is required, what each contains, and how to choose between them.

What a DCT is, briefly

A SAS Data Collection Tool is a structured FAA questionnaire focused on a specific element of the operator’s compliance system. Each DCT covers one element — training, hazmat, dispatch, maintenance, and so on — and asks the operator to answer questions with citations back to the manual suite. DCTs come in two flavors: Element-Design (ED), also called Design Assessment (DA), which evaluates the written compliance system; and Element-Performance (EP), also called Performance Assessment (PA), which evaluates whether the operation actually performs to the documented design.

For a full primer on SAS DCTs — what each flavor evaluates, who completes which, and what makes an answer acceptable — see What are SAS DCTs? Element-Design (DA) and Element-Performance (PA) Explained.

What a Statement of Compliance (SOC) is

A Statement of Compliance — usually abbreviated SOC — is a single, integrated document that walks the FAA regulations end-to-end and shows how the operator’s manual suite and procedures satisfy each underlying requirement. Where DCTs answer specific element-level questions, an SOC answers the broader question: across the entire regulatory landscape this operator faces, where is each requirement satisfied, and how?

An SOC is the document an inspector can sit down with, in one read-through, and form an opinion about the operator’s complete compliance picture. It is also the document the operator can submit when the FAA asks not for a particular DCT answer, but for proof that the operation as a whole holds up under scrutiny.

DCT vs. SOC: a side-by-side comparison

Aspect	Answered DCT (set)	Statement of Compliance (SOC)
Scope of each artifact	One element at a time (training, hazmat, maintenance, etc.)	The full regulatory picture for the operator, end-to-end
Structure	Question-and-answer form populated by the operator	Regulation-by-regulation traceback document
What the inspector sees	Element-level answers, each citation-traceable	An integrated narrative showing how the operation satisfies 14 CFR Part 135
Typical use case	Surveillance events, OpSpec amendments touching specific elements, certification work on individual elements	Certificate construction, major OpSpec amendments, surveillance events requesting the whole picture
Effort to produce	Scales with the number of DCT questions in scope	Larger than a single DCT — covers regulations end-to-end
Bundles with the other?	Often paired with an SOC when both are requested	Discounted when bundled with a DCT engagement for the same operator

When the FAA asks for an SOC

Three recurring scenarios drive an SOC request:

1. Certificate construction (new Part 135 applicants)

When an applicant works through the certification process, the FAA Certification Project Manager and the certification team want to see the complete compliance demonstration before issuing the certificate. Individual DCTs answer pieces of the puzzle, but an SOC is what shows the whole picture — the design, the manuals, the OpSpecs, the procedures, all reconciled against the regulations. Many applicants find that an SOC delivered alongside answered DCTs accelerates the certification timeline by removing back-and-forth questions.

2. Major OpSpec amendments

An OpSpec amendment that touches one narrow area (say, adding a single aircraft tail to A001) is usually handled with a focused DCT or two. But when the amendment touches multiple regulatory areas at once — adding a new aircraft type, adding international operations authorizations, adding HEMS or external-load authority — the inspector often wants an integrated view of how the operator’s compliance picture changes. That’s an SOC.

3. Surveillance events requesting the whole picture

Surveillance is when the inspector evaluates an existing Certificate Holder against the regulations and against the operator’s own documented design. For routine surveillance on specific elements, answered DCTs are usually sufficient. But when the inspector wants to see how the operation holds up across the regulatory landscape — especially after a significant change in scope, ownership, key personnel, or operations — an SOC is the document that ends the conversation rather than extending it.

What a good SOC package contains

A defensible SOC package is more than a list of regulations with citations. The components a Principal Inspector wants to see:

1. Operator scope summary. One concise section establishing the OpSpecs held, fleet, operations type, crew complement, active programs (SMS, AQP, ASAP, FOQA, CASS, etc.), hazmat carrier status, and other facts that determine which regulations apply.
2. Regulation-by-regulation traceback. The core of the document. For each applicable 14 CFR Part 135 section, a clear statement of where in the operator’s manual suite the requirement is satisfied, with paragraph-level citations.
3. Manual suite cross-mapping. A two-way index showing both directions: regulation → manual paragraph, and manual paragraph → regulation. Inspectors verify either direction depending on what question they’re asking.
4. Advisory Circular and 8900.1 references. Where the FAA expects operators to consider non-regulatory guidance, the SOC names the AC or 8900.1 chapter and shows how the operator’s procedures align.
5. Documented rationales for deviations, exemptions, or N/A determinations. Where a regulation does not apply (or applies with a documented exemption), the SOC explains why, in operator voice, tied to the operator’s actual scope.
6. FSDO-submission-ready delivery. A clean, branded, paginated PDF the operator can submit to the FSDO without further work.

How long an SOC engagement takes

SOC engagements are meaningfully larger than single DCT engagements because they cover the entire regulatory landscape rather than one element at a time. Realistic timing:

• Operators with a tight, current manual suite: typically one to two weeks from intake to delivered package.
• Operators with known manual gaps: running a DCT engagement first surfaces those gaps, and the SOC follows once the gaps are addressed. Total: typically two to four weeks across both engagements.
• New Part 135 applicants in mid-certification: the SOC is often built in parallel with manual suite development, so timing depends on how mature the manual suite is at SOC kickoff.

Pace is set by manual quality, not by SOC complexity. A well-organized manual suite with clear paragraph numbering is the single biggest accelerator.

The DCT-first vs. SOC-first decision

For applicants and operators choosing where to start:

• Start with a DCT engagement when: the inspector has assigned specific DCTs, you need a quick first deliverable, or you suspect your manual suite has gaps you want surfaced before producing a comprehensive document.
• Start with an SOC when: the inspector has asked for an end-to-end compliance demonstration (typical for certification or a major amendment), your manual suite is already mature and current, or you want a single artifact rather than a set of element-level answers.
• Bundle both when: the inspector is asking for both, or when you want the discount and the SOC will benefit from the DCT-phase manual cross-references. Delta Bravo Aviation prices SOCs at $1,500 (vs. $2,500 standalone) when paired with a DCT engagement for the same operator.

Where the references live

If you want to read further on the regulatory side:

• 14 CFR Part 135 — the substantive regulation. An SOC walks this end-to-end, section by section.
• FAA Order 8900.1 — particularly Volume 10 (SAS), which contains the procedures inspectors follow when working through DCTs, SOCs, and the broader compliance framework.
• Advisory Circulars in the 120-series and the 135-series — non-regulatory guidance the FAA expects operators to consider; SOCs cite these where applicable.
• Your Operations Specifications (OpSpecs) — the operator-specific authorities and limitations that define the scope of the SOC.

Related reading

• What are SAS DCTs? Element-Design (DA) and Element-Performance (PA) Explained — primer #1 in this series
• Statement of Compliance service — scope, deliverables, typical engagements
• DCT Completion service — what’s included, scope, deliverable format
• Manual Gap Suggested Edit Report — closing gaps surfaced by a DCT or SOC engagement
• Pricing — flat rates for DCT, SOC, and Manual Gap Suggested Edit Report