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) — now a day-one requirement

Until 2026 the compliance statement arrived during the formal-application phase, after the applicant was already working with a certification team. FAA Notice N 8900.766 moved it to the front. Every Part 135 applicant — single-pilot, nine-or-less and ten-or-more alike — now files a compliance statement “sized and scoped for intended operations” in the readiness package the FAA reviews before deciding whether to place the applicant on its Applicant List. For a single-pilot applicant the compliance statement carries much of what a General Operations Manual carries for larger operators, with the Safety Management System documentation integrated into it. For nine-or-less and ten-or-more applicants it sits alongside the GOM, training manual and (for ten-or-more) the CAMP and GMM, cross-referencing each regulation to the manual section that satisfies it.

Two things follow. The SOC must now be built in step with the manuals rather than after them — which is why Delta Bravo's Part 135 Certificate Builder drafts both from a single operator ground-truth register. And because the FAA's new AIS Services portal runs a machine-assisted completeness check before an inspector reads the file, a cleanly indexed, section-by-section compliance statement is what gets an application accepted in the 30-day window rather than returned on a 15-day clock. Individual DCTs still answer the certification team's element-level questions; the SOC is what shows the whole design reconciled against the regulations, and it is what the FAA wants to see first.

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: you are a new applicant — N 8900.766 requires it in your first filing — or 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 Notice N 8900.766, Determine Applicant Readiness for Certification (January 26, 2026), Appendix A, Table A-4 — the readiness tiers that place the compliance statement in every applicant's first filing.
• 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.

When the FAA asks for both

Under the 2026 readiness process, many applicants file a compliance statement as part of the N 8900.766 package and complete Element-Design DCTs. Certificate holders under surveillance may be asked for DCT responses alone, for a Statement of Compliance alone, or for both. The distinction is practical: DCTs are question-by-question assessments against the SAS element; a Statement of Compliance is a broader attestation that the manuals and procedures satisfy the applicable regulations. If your inspector asked for one and you deliver the other, the package comes back. When in doubt, ask the Principal Inspector which instrument they want before drafting.

Delta Bravo Aviation produces both: DCT completion at $20 per question and a Statement of Compliance package at $2,500 (or $1,500 bundled with a DCT engagement). Published fees are on the pricing page.

Frequently asked questions

What is a Statement of Compliance (SOC) in FAA Part 135?

A Statement of Compliance (SOC) is a regulation-by-regulation traceback document that shows how an FAA Part 135 operator's manual suite and operational procedures satisfy each underlying regulatory requirement end-to-end. It cross-maps the operator's General Operations Manual, General Maintenance Manual, training program, hazmat program, and other manual volumes against specific 14 CFR sections, Advisory Circulars, and FAA Order 8900.1 references. The result is a single, comprehensive document an FAA Principal Inspector can use to evaluate the entire compliance picture rather than answering individual DCTs in isolation.

How does an SOC differ from a DCT?

A Data Collection Tool (DCT) is a structured FAA questionnaire focused on a specific element of the operator's compliance system — for example, training, hazmat, or maintenance. Each DCT covers one element at a time. A Statement of Compliance (SOC) is broader: it walks the regulations end-to-end, regulation by regulation, and demonstrates how the operator's manual suite and procedures satisfy each one. Think of DCTs as element-by-element answers; an SOC is the entire compliance picture in one package.

When does the FAA require an SOC?

An SOC is typically requested in three scenarios. First, for a new Part 135 applicant, where since FAA Notice N 8900.766 (January 2026) a compliance statement sized and scoped to the intended operation is part of the readiness package filed before the FAA places the applicant on its Applicant List. Second, during major OpSpec amendments where the proposed change touches multiple regulatory areas (for example, adding a new aircraft type or a new operations authorization). Third, during surveillance events where the Principal Inspector wants the complete compliance picture in one package rather than working element-by-element through answered DCTs.

Do I need both a DCT package and an SOC?

Often yes. Answered DCTs and an SOC are not redundant — they answer different inspector questions. DCTs demonstrate compliance for specific elements with citation-by-citation precision. An SOC demonstrates that the operator's design satisfies the regulations end-to-end. During certification or a major amendment, an FAA inspector commonly asks for both. Some operators bundle them together for the discount; some run the DCT engagement first and add the SOC only if the inspector requests it.

What does a Statement of Compliance package contain?

A complete SOC package typically contains: (1) an executive summary describing the operator's scope (OpSpecs, fleet, operations type); (2) a regulation-by-regulation traceback covering each applicable 14 CFR Part 135 section; (3) cross-mapping between each regulation and the specific paragraph in the operator's manual suite where compliance is documented; (4) Advisory Circular and FAA Order 8900.1 references where applicable; (5) rationales for any deviations or exemptions; and (6) a delivery format ready for FSDO submission — typically a branded, paginated PDF.

How long does it take to produce an SOC?

An SOC engagement is meaningfully larger than a single DCT engagement because it covers regulations end-to-end rather than one element at a time. With a focused, experienced team, a complete SOC package can be produced in one to two weeks for an operator with a tight, current manual suite, or two to four weeks when a DCT engagement runs first to surface gaps depending on operator scope and the current state of the manual suite. Operators with a tight, well-organized manual suite finish faster; operators with manual gaps benefit from running a DCT engagement first to surface those gaps before the SOC work begins.

Who reviews an SOC after it's produced?

The operator's FAA Principal Inspector reviews the SOC, often with input from other specialists at the FSDO (Flight Standards District Office). During certification, the Certification Project Manager and the certification team work through the SOC together. For OpSpec amendments, the relevant subject-matter specialist may also review. The SOC is designed to be the document that gets handed across the desk — it should be defensible without an operator briefing.

Can a consultancy produce an SOC?

Yes. Aviation compliance consultancies routinely produce SOC packages on behalf of Part 135 Certificate Holders and Applicants. The consultancy works from the operator's manual suite, OpSpecs, and known regulatory exposure to produce a traceback document the operator submits under its own name. The operator remains the responsible party for accuracy — the consultancy provides the regulatory craft and the documentation discipline.

Related reading

• What are SAS DCTs? Element-Design (DA) and Element-Performance (PA) Explained — primer #1 in this series
• Can a Company Build Your Part 135 Certificate for You? What a Complete 2026 Application Contains
• How Long Does FAA Part 135 Certification Take? The Phases, the Clocks and What Changed in 2026
• 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, Manual Gap Suggested Edit Report and the Builders