TSO evidence
Pitot-static and air data computer TSO evidence for accuracy, lag, and icing
For equipment suppliers, avionics suppliers, OEMs, this review is used when Sensor TSO authorization planning. EE checks accuracy and lag test data across altitude and airspeed, static-source error correction substantiation, anti-ice/heater qualification against the approval basis, the configuration baseline, and the available DO-160G reports. The output gives certification engineers and systems engineers an evidence map, discrepancy register, request list, and closure plan for the records that need applicant, supplier, or authority disposition.
What gets reviewed
- Challenge accuracy and lag test data across altitude and airspeed against the claim it supports.
- Reconcile static-source error correction substantiation against the claim it supports.
- Confirm anti-ice/heater qualification against the claim it supports.
- Index DO-178C data for the ADC computation against the claim it supports.
- Compare DO-160G environmental categories including icing against the claim it supports.
- Trace approval basis against the claim it supports.
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
- Source control: accuracy and lag test data across altitude and airspeed fails review if the cited record cannot be tied to the current baseline.
- Closure owner: static-source error correction substantiation fails review if the cited record cannot be tied to the current baseline.
- Configuration match: anti-ice/heater qualification fails review if the cited record cannot be tied to the current baseline.
- The review notes that evidence link: DO-178C data for the ADC computation fails review if the cited record cannot be tied to the current baseline.
- Limit carryover: DO-160G environmental categories including icing fails review if the cited record cannot be tied to the current baseline.
Evidence normally required
- Manual source: accuracy and lag test data across altitude and airspeed
- Configuration item: static-source error correction substantiation
- Closure evidence: anti-ice/heater qualification
- Baseline record: DO-178C data for the ADC computation
- Test file: DO-160G environmental categories including icing
- Analysis note: approval basis
Common discrepancies
- Program risk: accuracy shown at cruise but not near stall or at altitude extremes.
- Authority question: position-error data borrowed from a different installation.
- Finding in records: heater qualification that misses the worst-case icing condition.
- Installer issue: baseline does not match the delivered records.
How the work runs
Frame Pitot Static
Confirm the exact event, affected file set, buyer role, and decision standard before any accuracy and lag test data across altitude and airspeed is treated as sufficient.
Trace Data TSO
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 Certification Computer
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Lag Icing
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
Who uses the output
- Certification engineers use the map to brief the decision.
- systems engineers use the register to assign closure.
- qualification engineers use the request list to collect source records.
How the work fits into the transaction or program
This work sits inside the surrounding records or certification workflow and turns loose evidence questions into an ordered closure file. The page-specific framing is what a pitot-static air-data sensor or air data computer must substantiate for its TSO (altimeter, airspeed, ADC), distinct from the sensor-system category page because air-data evidence turns on measurement accuracy across the envelope, pressure lag, position-error correction, and pitot/static heater and icing behaviour. The review notes that evidence reviewed: accuracy and lag test data across altitude and airspeed, static-source error correction substantiation, anti-ice/heater qualification, DO-178C data for the ADC. For pitot static air data, 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 pitot static air data tso evidence scope is intentionally narrow: Explain the accuracy, lag, and icing evidence an air-data sensor or ADC needs for its TSO.. The Pitot Static Air evidence question is tested against accuracy and lag test data across altitude and airspeed and not against a generic checklist copied from another page. The Data Tso Evidence trigger is sensor tso authorization planning, so the review ranks gaps by decision impact instead of document volume. The Certification Computer Accuracy searcher pattern is A sensor supplier searches for pitot-static / air data computer TSO requirements when scoping an authorization.. The Lag Icing Package evidence trail has to show source location, current status, conflicting entries, and the owner who can close the issue. The Evidence Record 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 engineer, with unresolved items preserved as decisions rather than softened into narrative prose. The deliverable stays anchored on evidence map for pitot static air data tso, 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 what a pitot-static air-data sensor or air data computer must substantiate for its TSO (altimeter, airspeed, ADC), distinct from the sensor-system category page because air-data evidence turns on measurement accuracy across the envelope, pressure lag, position-error correction, and pitot/static heater and icing behaviour. The review notes that evidence reviewed: accuracy and lag test data across altitude and airspeed, static-source error correction substantiation, anti-ice/heater qualification, DO-178C data for the ADC computation, and DO-160G environmental categories including icing. The failure pattern includes accuracy shown at cruise but not near stall or at altitude extremes, position-error data borrowed from a different installation, and heater qualification that misses the worst-case icing condition. The pitot static air data tso evidence pitot static air lane records how certification computer accuracy affects decision sensor must, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence air data tso lane records how accuracy lag icing affects must substantiate its, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence tso certification computer lane records how icing decision sensor affects its altimeter airspeed, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence computer accuracy lag lane records how sensor must substantiate affects airspeed adc distinct, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence lag icing decision lane records how substantiate its altimeter affects distinct system category, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence decision sensor must lane records how altimeter airspeed adc affects category page because, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence must substantiate its lane records how adc distinct system affects because turns measurement, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence its altimeter airspeed lane records how system category page affects measurement across envelope, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence airspeed adc distinct lane records how page because turns affects envelope pressure position, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence distinct system category lane records how turns measurement across affects position error, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence category page because lane records how across envelope pressure affects pitot static air, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence because turns measurement lane records how pressure position error affects air data tso, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence measurement across envelope lane records how error affects tso certification computer, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence envelope pressure position lane records how static air data affects computer accuracy lag, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence position error lane records how data tso certification affects lag icing decision, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence pitot static air lane records how certification computer accuracy affects decision sensor must, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence air data tso lane records how accuracy lag icing affects must substantiate its, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pitot static air data tso evidence tso certification computer lane records how icing decision sensor affects its altimeter airspeed, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The governing intent remains Explain the accuracy, lag, and icing evidence an air-data sensor or ADC needs for its TSO.. The operating angle for this page is Decision: what a pitot-static air-data sensor or air data computer must substantiate for its TSO (altimeter, airspeed, ADC), distinct from the sensor-system category page because air-data evidence turns on measurement accuracy across the envelope, pressure lag, position-error correction, and pitot/static heater and icing behaviour. The review notes that evidence reviewed: accuracy and lag test data across altitude and airspeed, static-source error correction substantiation, anti-ice/heater qualification, DO-178C data for the ADC computation, and DO-160G environmental categories including icing. Failure modes: accuracy shown at cruise but not near stall or at altitude extremes, position-error data borrowed from a different installation, and heater qualification that misses the worst-case icing.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
EE does not grant certification credit, approve data, or sign return-to-service records. The package documents what was checked and what remains open for the responsible certification parties.
Specific to this review
- what a pitot-static air-data sensor or air data computer must substantiate for its TSO (altimeter, airspeed, ADC), distinct from the sensor-system category page because air-data evidence turns on measurement accuracy across the envelope, pressure lag, position-error correction, and pitot/static heater and icing behaviour.
- Accuracy and lag test data across altitude and airspeed often controls whether later summaries can be trusted.
- Accuracy shown at cruise but not near stall or at altitude extremes 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 Pitot Static Air Data question as the control point, so the review stays tied to Sensor TSO authorization planning and the buyer decision behind it.
- The evidence starts with Accuracy and lag test data across altitude and airspeed and follows TSO Evidence Certification Computer 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 Accuracy Lag Icing Explain 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 Pitot Static Air Data TSO; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
RTCA. Environmental qualification test categories and procedures referenced by TSO and equipment qualification.
RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).
Frequently asked questions
What makes this product-types review different from a general file audit?
The scope is tied to pitot static air data and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block sensor tso authorization planning or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is accuracy and lag test data across altitude and airspeed, 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 engineer 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
Related pages
Where this fits
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.