TCAS II / ACAS II TSO-C119e for DO-185B collision-logic evidence

What gets reviewed

• Trace DO-185B MOPS and logic-version verification against the claim it supports.
• Challenge hybrid-surveillance test data against the claim it supports.
• Reconcile DO-178C software data at the assigned level for the RA logic against the claim it supports.
• Confirm coordination-with-transponder interface data against the claim it supports.
• Index DO-160G environmental categories against the claim it supports.
• Compare approval basis against the claim it supports.

What gets validated

• Limit carryover: DO-185B MOPS and logic-version verification fails review if the cited record cannot be tied to the current baseline.
• Source control: hybrid-surveillance test data fails review if the cited record cannot be tied to the current baseline.
• Closure owner: DO-178C software data at the assigned level for the RA logic fails review if the cited record cannot be tied to the current baseline.
• Configuration match: coordination-with-transponder interface data fails review if the cited record cannot be tied to the current baseline.
• The review notes that evidence link: DO-160G environmental categories fails review if the cited record cannot be tied to the current baseline.

Evidence normally required

• Analysis note: DO-185B MOPS and logic-version verification
• Manual source: hybrid-surveillance test data
• Configuration item: DO-178C software data at the assigned level for the RA logic
• Closure evidence: coordination-with-transponder interface data
• Baseline record: DO-160G environmental categories
• Test file: approval basis

Common discrepancies

• Buyer concern: logic version 7.0 residual behaviour where 7.1 is required.
• Program risk: hybrid surveillance credited without the supporting track-quality evidence.
• Authority question: RA/HMI alerting not substantiated against the human-factors expectations.
• Finding in records: baseline does not match the delivered records.

How the work runs

What the buyer receives

• The review notes that evidence map for TCAS Ii ACAS Ii TSO C119e
• Discrepancy register for TCAS Ii ACAS Ii TSO C119e
• Applicability and approval basis summary
• Source record request list

Who uses the output

• Certification engineers use the map to brief the decision.
• avionics engineers use the register to assign closure.
• safety engineers use the request list to collect source records.

How the work fits into the transaction or program

What a TCAS II / ACAS II unit must substantiate for TSO-C119e, distinct from the transponder and surveillance pages because the decisive artifact is DO-185B collision-avoidance logic (version 7.1) behaviour, hybrid-surveillance performance, and the resolution-advisory alerting shown safe at the flight deck. The evidence set centers on DO-185B MOPS and logic-version verification, hybrid-surveillance test data, DO-178C software data at the assigned level for the RA logic, coordination-with-transponder interface. The likely weak points are logic version 7.0 residual behaviour where 7.1 is required, hybrid surveillance credited without the supporting track-quality evidence, and RA/HMI alerting not substantiated against the human-factors expectations. The output gives the certification engineer a cleanup register for TCAS II / ACAS II TSO-C119e for DO-185B collision-logic evidence before surveillance TSO authorization planning.

Regulatory limits

EE does not certify equipment, approve installations, or declare an aircraft compliant. The output identifies supportable claims, missing records, and questions that need applicant or authority disposition.

Specific to this review

• what a TCAS II / ACAS II unit must substantiate for TSO-C119e, distinct from the transponder and surveillance pages because the decisive artifact is DO-185B collision-avoidance logic (version 7.1) behaviour, hybrid-surveillance performance, and the resolution-advisory alerting shown safe at the flight deck.
• DO-185B MOPS and logic-version verification often controls whether later summaries can be trusted.
• Logic version 7.0 residual behaviour where 7.1 is required is treated as a record gap until an owner closes it.
• FAA and EASA evidence should stay distinguishable from commercial claims and installer notes.
• The scope uses the Tcas Acas TSO C119e question as the control point, so the review stays tied to Surveillance TSO authorization planning and the buyer decision behind it.
• The evidence starts with DO-185B MOPS and logic-version verification and follows Evidence Certification 185b Collision 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 engineer: 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 Logic Explain Hybrid Surveillance questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
• The handoff value comes from Evidence map for TCAS Ii ACAS Ii TSO C119e; it gives the next reviewer a precise map instead of another broad request for a better file.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits