DO-178C review

DO-178B to DO-178C transition review for avionics suppliers

This page is for avionics suppliers, equipment suppliers, Certification teams when Legacy product modification or reissue puts do-178b to do-178c transition review on the critical path. EE checks legacy software lifecycle data, DO-178C objective map, tool qualification rationale against the approval basis, configuration baseline, effectivity, revision status, and source records named in the brief. The buyer receives a discrepancy register, evidence map, and closure request list for the next review gate. The work tests records and certification-data traceability only; it does not replace authority, delegate, approval-holder, or authorized-person decisions.

When this review is needed

Use this review when Legacy product modification or reissue starts driving schedule or commercial exposure.
A certification manager reviving or modifying a legacy product searching for whether DO-178B evidence is still acceptable.
The highest-risk breakpoint is: assuming blanket acceptance of DO-178B data without checking the applicable AC/AMC revision, legacy tool qual credit that does not translate to a TQL, and mixed-revision programs where new code follows C while changed legacy code silently keeps B processes.

The problem

At this gate, on a new or changed program, can DO-178B-era lifecycle data stand, or do the DO-178C changes (supplements, tool qualification restructuring into TQLs, parameter data items, clarified objectives) force rework. The file set covers the certification basis and guidance revision the authority expects, the legacy data set mapped against DO-178C objective changes, tool qualification claims restated in TQL terms, and the change scope that reopens otherwise grandfathered data. Known breakpoints include assuming blanket acceptance of DO-178B data without checking the applicable AC/AMC revision, legacy tool qual credit that does not translate to a TQL, and mixed-revision programs where new code follows.

What gets reviewed

Review the buyer decision in the brief: Decide whether legacy DO-178B data survives on a current program and scope the upgrade where it does not.
Trace legacy software lifecycle data to source date, revision, owner, and current configuration.
Match effectivity for DO-178C objective map to the serial range, article version, aircraft, or fleet in scope.
At this gate, on a new or changed program, can DO-178B-era lifecycle data stand, or do the DO-178C changes (supplements, tool qualification restructuring into TQLs,.

Scope this review

Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.

Identify what is missing against the means of compliance.

What gets validated

Document control: legacy software lifecycle data has an identified owner and no uncontrolled copies carrying the main claim.
Effectivity test: DO-178C objective map is rejected when coverage is inferred from similar hardware or aircraft.
Configuration test: certificate scope, report setup, and delivered baseline are reconciled before credit is assigned.
Exception handling: each unresolved point receives a closure owner and a target source record.

Evidence normally required

Source record set for legacy software lifecycle data
Program file covering DO-178C objective map
Configuration baseline with approval basis and revision index
Open issue log tied to tool qualification rationale

Common discrepancies

The file set covers the certification basis and guidance revision the authority expects, the legacy data set mapped against DO-178C objective changes, tool qualification.
Known breakpoints include assuming blanket acceptance of DO-178B data without checking the applicable AC/AMC revision, legacy tool qual credit that does not translate to a TQL, and.
Revision mismatch leaves tool qualification rationale separated from the certificate, matrix, instruction, or delivered baseline.
Storage completeness is higher than decision readiness because the file lacks a clear disposition for this buying stage.

What is at stake

Specific exposure for this page: assuming blanket acceptance of DO-178B data without checking the applicable AC/AMC revision, legacy tool qual credit that does not translate to a TQL, and mixed-revision programs where new code follows C while changed legacy code silently keeps B processes.

How the work runs

Frame 178b 178c

Confirm the exact event, affected file set, buyer role, and decision standard before any legacy software lifecycle data is treated as sufficient.

Trace Review Avionics

Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.

Sort Defend Legacy

Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.

Package Upgrade 178

Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.

What the buyer receives

DO-178B to DO-178C transition review discrepancy register
source map for legacy software lifecycle data
effectivity and configuration closure list
decision summary with limits and escalation items

How the work fits into the transaction or program

A certification manager reviving or modifying a legacy product searching for whether DO-178B evidence is still acceptable. The review packages the evidence before that searcher's next gate, so records, engineering, and certification staff can work from the same exception list. The page-specific framing is on a new or changed program, can DO-178B-era lifecycle data stand, or do the DO-178C changes (supplements, tool qualification restructuring into TQLs, parameter data items, clarified objectives) force rework. Evidence reviewed: the certification basis and guidance revision the authority expects, the legacy data set mapped against DO-178C objective changes, tool qualification claims restated in TQL terms, and the change scope that reopens otherwise grandfathered data. Failure modes include assuming blanket. For 178b 178c transition review, the practical output is a defensible record of what was checked, what did not match, who owns the fix, and which issue remains outside the review boundary. The do 178b to do 178c transition review scope is intentionally narrow: Decide whether legacy DO-178B data survives on a current program and scope the upgrade where it does not.. The 178b 178c Transition evidence question is tested against legacy software lifecycle data and not against a generic checklist copied from another page. The Review Avionics Suppliers trigger is legacy product modification or reissue, so the review ranks gaps by decision impact instead of document volume. The Defend Legacy Data searcher pattern is A certification manager reviving or modifying a legacy product searching for whether DO-178B evidence is still acceptable.. The Upgrade 178 Revision evidence trail has to show source location, current status, conflicting entries, and the owner who can close the issue. The Acceptance Decision Review exception logic separates missing artifacts from mismatched data because those findings move through different closure routes. The Closure Trace Baseline handoff is written for certification manager, with unresolved items preserved as decisions rather than softened into narrative prose. The deliverable stays anchored on do-178b to do-178c transition review discrepancy register, which makes the next reviewer able to reperform the path without rebuilding the file. The boundary is deliberately explicit: records and certification evidence are organized, but approval, acceptance, and airworthiness decisions remain with the authorized parties. The brief-specific angle is on a new or changed program, can DO-178B-era lifecycle data stand, or do the DO-178C changes (supplements, tool qualification restructuring into TQLs, parameter data items, clarified objectives) force rework. Evidence reviewed: the certification basis and guidance revision the authority expects, the legacy data set mapped against DO-178C objective changes, tool qualification claims restated in TQL terms, and the change scope that reopens otherwise grandfathered data. The failure pattern includes assuming blanket acceptance of DO-178B data without checking the applicable AC/AMC revision, legacy tool qual credit that does not translate to a TQL, and mixed-revision programs where new code follows C while changed legacy code silently keeps B processes. The do 178b to do 178c transition review 178b 178c transition lane records how defend legacy data affects revision acceptance decision, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review transition avionics suppliers lane records how data upgrade 178 affects decision new changed, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review suppliers defend legacy lane records how 178 revision acceptance affects changed program can, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review legacy data upgrade lane records how acceptance decision new affects can era lifecycle, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review upgrade 178 revision lane records how new changed program affects lifecycle stand changes, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review revision acceptance decision lane records how program can era affects changes supplements tool, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review decision new changed lane records how era lifecycle stand affects tool qualification restructuring, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review changed program can lane records how stand changes supplements affects restructuring tqls parameter, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review can era lifecycle lane records how supplements tool qualification affects parameter items clarified, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review lifecycle stand changes lane records how qualification restructuring tqls affects clarified objectives, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review changes supplements tool lane records how tqls parameter items affects 178b 178c transition, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review tool qualification restructuring lane records how items clarified objectives affects transition avionics suppliers, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review restructuring tqls parameter lane records how objectives affects suppliers defend legacy, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review parameter items clarified lane records how 178c transition avionics affects legacy data upgrade, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review clarified objectives lane records how avionics suppliers defend affects upgrade 178 revision, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review 178b 178c transition lane records how defend legacy data affects revision acceptance decision, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review transition avionics suppliers lane records how data upgrade 178 affects decision new changed, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The do 178b to do 178c transition review suppliers defend legacy lane records how 178 revision acceptance affects changed program can, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The governing intent remains Decide whether legacy DO-178B data survives on a current program and scope the upgrade where it does not.. The operating angle for this page is Decision: on a new or changed program, can DO-178B-era lifecycle data stand, or do the DO-178C changes (supplements, tool qualification restructuring into TQLs, parameter data items, clarified objectives) force rework. Evidence reviewed: the certification basis and guidance revision the authority expects, the legacy data set mapped against DO-178C objective changes, tool qualification claims restated in TQL terms, and the change scope that reopens otherwise grandfathered data. Failure modes: assuming blanket acceptance of DO-178B data without checking the applicable AC/AMC revision, legacy tool qual credit that does not translate to a TQL, and mixed-revision programs where new code follows C while changed legacy code silently keeps B.

Start with a single asset

Confirm requirements map to substantiating evidence.

Regulatory limits

For do-178b to do-178c transition review, EE reviews legacy software lifecycle data, DO-178C objective map, tool qualification rationale for completeness, consistency, and traceability. The work does not issue approvals, approve data, grant relief, validate STCs, accept release certificates, or make airworthiness determinations. Final decisions remain with the responsible authority, delegate, approval holder, operator, or authorized person.

Specific to this review

At this gate, on a new or changed program, can DO-178B-era lifecycle data stand, or do the DO-178C changes (supplements, tool qualification restructuring into.
The file set covers the certification basis and guidance revision the authority expects, the legacy data set mapped against DO-178C objective changes, tool.
Known breakpoints include assuming blanket acceptance of DO-178B data without checking the applicable AC/AMC revision, legacy tool qual credit that does not.
The scope uses the 178b 178c Transition Review question as the control point, so the review stays tied to Legacy product modification or reissue and the buyer decision behind it.
The evidence starts with legacy software lifecycle data and follows Avionics Suppliers Defend Legacy references until every exception has a source location and a reason code.
The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
The timing matters for certification manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
The boundary control keeps Data Upgrade 178 Revision questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
The handoff value comes from DO-178B to DO-178C transition review discrepancy register; it gives the next reviewer a precise map instead of another broad request for a better file.
The source discipline is stricter on this page than on a general audit because the claim being tested is Decide whether legacy DO-178B data survives on a current program and scope the upgrade where it does not..

Sources

DO-178C - Software Considerations in Airborne Systems and Equipment Certification

RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).

Order 8110.4 - Type Certification

Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.

Frequently asked questions

What makes this standards review different from a general file audit?

The scope is tied to 178b 178c transition review and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block legacy product modification or reissue or can be closed later without changing the decision.

What evidence has to be available before this work starts?

The starting point is legacy software lifecycle data, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.

Who decides whether an open item is acceptable?

The review explains what the evidence supports and gives certification manager a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.

Relevant glossary terms

RTCA DO-178C / EUROCAE ED-12C, Software Considerations in Airborne Systems and Equipment Certification (DO-178C)EUROCAE ED-12C, Software Considerations in Airborne Systems and Equipment Certification (ED-12C)Tool Qualification Level (TQL)Reuse and Certification Credit Change Impact Assessment (CIA)Guidance Material

DO-160F to DO-160G delta review for equipment suppliersDO-160F to DO-160G delta review for equipment suppliers, with source-record checks, discrepancy findings, and DO-200B aeronautical data for data quality requirements and the processing chainPlanning do 200b data quality requirements? EE reviews lifecycle data, configuration limits, and missing suppo DO-178C software compliance support for airborne softwareYour lifecycle data faces every DO-178C objective at its software level. We map the gaps before review, so pla Software level objective mapping under DO-178CDoes your DO-178C objective set match the assigned level? We reconcile objectives, independence, and lifecycle Certification-basis mapping for a certification programMiss a special condition now and it surfaces as a finding later. Get a documented certification basis, each re

Where this fits

Service: TSO and STC Certification For Equipment

Talk to an engineer who has done this work

We will walk through your current state, the records or evidence involved, and a scoped first engagement.

Talk through the aircraft, records, evidence, deadline, and next useful step.

Book a scoping call