Preparing for an FAA SAS DCT Review: What Part 135 Operators Should Expect
A SAS Data Collection Tool review is not a pop quiz — it is a structured, predictable evaluation of one element of your compliance system at a time. The operators who move through it smoothly are not the ones with the thickest manuals; they are the ones who can put a finger on the exact paragraph that answers each question. This guide walks through what the inspector is actually evaluating, what to stage before the review, and the handful of mistakes that send answers back.
The short answer
What is being judged? Whether your written program satisfies the regulation (design), and whether your operation actually performs to that program (performance).
What wins? Paragraph-level citations to your current, controlled manual suite — not narrative restatements of the rule.
What to do first? Build a question-to-paragraph cross-reference before the inspector ever opens the DCT.
What a SAS DCT review actually is
The FAA’s Safety Assurance System (SAS) is the framework Flight Standards uses to certificate and then continuously oversee 14 CFR Part 135 operators. Within SAS, the Data Collection Tool (DCT) is the standardized instrument an inspector uses to evaluate a single element of your operation — one slice of the compliance system, such as training, hazardous materials, manuals and recordkeeping, airworthiness, or operational control.
Because the DCT is standardized, the review is far more predictable than operators expect. The inspector is not improvising questions; they are working a defined list, and every question traces back to a regulatory requirement. That predictability is your advantage: if you know the questions are coming, you can stage the answers in advance.
If you want the full anatomy of SAS DCTs — the element structure, the assessment types, and who completes which — start with What are SAS DCTs? Element-Design (DA) and Element-Performance (PA) Explained.
The two questions behind every DCT: design and performance
Every SAS element can be evaluated along two axes, and understanding the difference is the single most useful thing an operator can know walking into a review.
| Assessment | The question it answers | What the inspector examines |
|---|---|---|
| Element-Design (Design Assessment / DA) | Is the written program sound? | Your manuals and procedures — does a complete, clear, regulation-satisfying method of compliance exist on paper, traceable to a specific paragraph? |
| Element-Performance (Performance Assessment / PA) | Does the operation do what the program says? | Records, observations, and processes — does the line operation actually follow the documented procedure in practice? |
The trap is to prepare for one and forget the other. An operator can have an immaculate manual (strong design) and still draw findings because line crews do something different from what the manual says (weak performance). The reverse happens too: a sound operation whose manuals never quite documented the procedure. A DCT review may probe design, performance, or both — so prepare for both.
What to stage before the review
Preparation is almost entirely about having the right documents current, controlled, and indexed. Stage these before the inspector opens the DCT:
- The complete current manual suite. General Operations Manual, General Maintenance Manual, training program, hazmat program (if you are a hazmat carrier or carry will-not-carry obligations), and every other volume your OpSpecs require. Confirm each is at its live, controlled revision — not a working draft on someone’s desktop.
- Your Operations Specifications. The OpSpecs define your authorized scope. The inspector reads the DCT against what you are actually authorized to do, so the OpSpecs frame every answer. Have them current and at hand.
- A question-to-paragraph cross-reference. The highest-leverage prep there is. For each DCT question, pre-identify the exact manual paragraph (and record, if performance is in scope) that answers it. This is the difference between a smooth review and a week of follow-up emails.
- Key personnel designations and the org chart. Many elements turn on who holds operational control, who supervises maintenance, who runs the training program. Have the current designations documented.
- Referenced program documents. SMS, drug and alcohol program, CASS, MEL/MMEL authorizations, and anything your manuals cross-reference. If a manual paragraph points to another document, the inspector may want to see it.
- The current revision of each DCT in scope. DCTs are issued per peer group (135B, 135C, 135D, 135E) and specialty (OP or AW) and are revised as regulations and guidance change — the file name carries all three, e.g.
ED_4_3_9_135C_OP_V17. Confirm you are working the revision your inspector will open, and record the revision and date on every answered DCT. For applicants the FAA expects DCT answers to be current within 90 days. - Evidence of currency for the regulatory references. The questions cite 14 CFR sections, Advisory Circulars and 8900.1 paragraphs that also move. An AC superseded last quarter is a cite an inspector will catch. Check each reference against the current corpus before the review.
What makes a DCT answer strong
A strong answer does three things: it points to a precise location, it matches the current revision, and it addresses the right axis (design, performance, or both). The model answer reads less like an essay and more like a citation: “This requirement is satisfied at GOM § 4.3.2, which establishes the procedure; performance is evidenced by the training records retained under GOM § 12.1.”
Notice what that answer does not do: it does not restate the regulation in narrative form, it does not gesture vaguely at “the manual,” and it does not leave the inspector to go hunting. Precision is courtesy, and courtesy moves reviews.
The five reasons answers get sent back
Across certification and surveillance, rejected DCT answers cluster into a short list of avoidable problems:
- The cited paragraph doesn’t actually contain the required content. The citation points to § 4.3, but § 4.3 covers something adjacent. Verify every citation by reading the paragraph as if you were the inspector.
- Narrative instead of citation. The answer explains how the operator complies in prose but never points to where that compliance is documented. The inspector needs the location, not a paraphrase.
- Stale revision. The answer cites a manual paragraph that moved, was renumbered, or was removed in the current revision. Always answer against the live controlled document.
- Blank or not-applicable without a rationale. “N/A” is a legitimate answer when a requirement genuinely doesn’t apply to your scope — but only with a documented reason tied to your OpSpecs and operations. An unexplained N/A reads as an evasion.
- Design answered, performance ignored. The operator documents the written procedure beautifully but never addresses whether the operation performs to it — leaving the performance half of the inspector’s question open.
A sixth has become common enough to earn its own line:
- Wrong DCT revision, peer group or specialty. The operator answered revision 15 of a 135C Operations DCT; the inspector opened revision 17, or the 135B edition, or the Airworthiness counterpart. Question numbers shift, items are added, and the package reads as incomplete even where the underlying compliance is sound. Match the exact instrument before you start.
Every one of these is preventable with disciplined, paragraph-level work against the current manual suite and the current DCT bank.
How long the review takes — and what controls it
Operators often ask how long a DCT review runs. The honest answer is that the number of questions matters far less than the quality of the responses. A clean response set — precise citations, current revisions, documented rationales — gives the inspector nothing to chase, and the element closes quickly. A disorganized set generates a cycle of clarification requests that can stretch a review for weeks.
In other words, preparation does not just improve the outcome of a review; it shortens the duration. The cross-reference you build up front pays for itself in review time saved.
Applicants: you now complete the Element-Design DCTs yourself
Under the FAA's 2026 readiness process (Notice N 8900.766), a new Part 135 applicant completes the Element-Design DCTs for its own design as part of the package the certification team reviews — the same instruments a certificate holder meets in surveillance. Everything above applies, with one difference: the applicant is answering against manuals that are themselves still being accepted, so every answer has to track the manual revision the FAA will actually read. Building the manuals, the compliance statement and the DCT answers from one set of operator facts is how that is kept straight; see Can a Company Build Your Part 135 Certificate for You?.
How Delta Bravo reviews its own work before you see it
The send-back list above is exactly what a reviewer who did not write the answers is best at catching. Every DCT package Delta Bravo renders therefore passes a blind counsel review: a panel of independent inspector-style reviewers, working from the rendered package and the operator's manuals with no knowledge of how the answers were produced, reads for the weak citation, the stale revision, the unsupported N/A and the design-only answer. Findings are fixed before the package is delivered, and the review itself — what was checked and what was found — is kept with the engagement record. It is the step most in-house DCT efforts skip, and the one that most shortens the inspector's review.
Revision currency is not optional
An inspector reads your answers against the current revision of each DCT on the Dynamic Regulatory System. If you answered revision 16 and the inspector opens revision 17, question numbers shift and compliant answers look incomplete. Before any surveillance event or assigned DCT package, re-check the revision of every DCT in scope. Delta Bravo refreshes the full SAS DCT bank weekly against DRS and publishes what changed in DCT Watch.
Frequently asked questions
What is a SAS DCT review?
A SAS Data Collection Tool (DCT) review is the structured process an FAA inspector uses under the Safety Assurance System to evaluate one element of a Part 135 operator's compliance system. The inspector works through a standardized questionnaire — the DCT — that asks whether the operator's written program (Design Assessment) and actual operation (Performance Assessment) meet the underlying regulatory requirement. Each DCT focuses on a single element, such as training, hazmat, recordkeeping, or maintenance.
What does the FAA inspector look for during a DCT review?
The inspector is looking for two things. First, in the Element-Design (Design Assessment) phase, that the operator's manuals and written procedures actually contain a documented method of compliance for each regulatory requirement — and that the method is clear, complete, and traceable to a specific manual paragraph. Second, in the Element-Performance (Performance Assessment) phase, that the operation performs in practice the way the manuals say it does. A DCT answer is strongest when it points to an exact manual paragraph and, where relevant, the record or process that demonstrates the procedure is actually followed.
How should an operator prepare for a DCT review?
Stage the manual suite in its current, controlled revision; confirm the table of contents and paragraph numbering match the live documents; assemble the OpSpecs so the inspector can see the operator's authorized scope; and pre-map each DCT question to the specific manual paragraph that answers it. Operators who walk into a DCT review with a question-to-paragraph cross-reference already built spend far less time in back-and-forth and present a more organized compliance picture.
What is the difference between Element-Design and Element-Performance in a DCT?
Element-Design (also called Design Assessment, or DA) evaluates whether the operator's written compliance system is sound — do the manuals contain a complete, clear, regulation-satisfying procedure? Element-Performance (also called Performance Assessment, or PA) evaluates whether the operator actually does what the manuals say. An operator can have an excellent design and still fail performance if line operations diverge from the documented procedure, and vice versa. A DCT review may cover one or both.
Why do DCT answers get rejected by the FAA?
The most common reasons are: citing a manual paragraph that does not actually contain the required content; answering the regulation in narrative rather than pointing to where compliance is documented; referencing an outdated manual revision; leaving a question blank or marked not-applicable without a documented rationale tied to the operator's scope; and answers that address the design but ignore the performance side the inspector is also evaluating. Precise, paragraph-level citations to the current controlled manual fix the majority of rejections.
How long does a DCT review take?
The inspector-side review depends on how many DCTs are in scope and how clean the operator's responses are. A well-prepared operator with paragraph-level cross-references can move an inspector through an element quickly because there is nothing to chase down. A disorganized response — vague citations, stale revisions, missing rationales — extends the review with repeated requests for clarification. Preparation, not the number of questions, is usually what determines how long a review drags on.
Can a consultant complete DCTs for a Part 135 operator?
Yes. Aviation compliance consultancies routinely complete SAS DCTs on behalf of Part 135 Certificate Holders and applicants, working from the operator's manual suite, OpSpecs, and operational scope. The consultant supplies the regulatory craft and the citation discipline; the operator remains the responsible party and submits the answers under its own name. Delta Bravo Aviation completes DCTs at a flat rate of $20 per question with chapter-and-verse citations to the operator's own manuals.
What documents does an operator need ready for a DCT review?
At minimum: the complete current manual suite (General Operations Manual, General Maintenance Manual, training program, hazmat program where applicable, and any other volumes); the operator's Operations Specifications; the organizational chart and key personnel designations; and any program documents referenced by the manuals (SMS, drug and alcohol program, CASS, and similar). Each DCT question should be traceable to a paragraph in one of these documents.
Related reading
- What are SAS DCTs? Element-Design (DA) and Element-Performance (PA) Explained
- DCT vs. SOC: When the FAA Wants More Than Answered DCTs
- OpSpecs Explained: How Operations Specifications Scope Your Certificate and Drive DCT Answers
- Can a Company Build Your Part 135 Certificate for You? What a Complete 2026 Application Contains
- DCT Completion service — what's included, scope, deliverable format
- Pricing — flat rates for DCT, SOC, Manual Gap Suggested Edit Report and the Builders