TSO evidence
Seat and restraint TSO-C127 evidence for run-time 16g testing and injury criteria
For equipment suppliers, OEMs, MROs, this review is used when Seat qualification planning. EE checks run-time test reports for the horizontal and vertical pulses, injury-criteria measurements, structural retention and floor-track load data against the approval basis, the configuration baseline, and the available certification records. The output gives certification engineers and structures engineers an evidence map, discrepancy register, request list, and closure plan for the records that need applicant, supplier, or authority disposition.
What gets reviewed
- Index run-time test reports for the horizontal and vertical pulses against the claim it supports.
- Compare injury-criteria measurements against the claim it supports.
- Trace structural retention and floor-track load data against the claim it supports.
- Challenge flammability of seat materials against the claim it supports.
- Reconcile installation-drawing basis for the tested configuration against the claim it supports.
- Confirm 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
- Configuration match: run-time test reports for the horizontal and vertical pulses fails review if the cited record cannot be tied to the current baseline.
- The review notes that evidence link: injury-criteria measurements fails review if the cited record cannot be tied to the current baseline.
- Limit carryover: structural retention and floor-track load data fails review if the cited record cannot be tied to the current baseline.
- Source control: flammability of seat materials fails review if the cited record cannot be tied to the current baseline.
- Closure owner: installation-drawing basis for the tested configuration fails review if the cited record cannot be tied to the current baseline.
Evidence normally required
- Baseline record: run-time test reports for the horizontal and vertical pulses
- Test file: injury-criteria measurements
- Analysis note: structural retention and floor-track load data
- Manual source: flammability of seat materials
- Configuration item: installation-drawing basis for the tested configuration
- Closure evidence: approval basis
Common discrepancies
- Finding in records: run-time tests run on a seat configuration that differs from the installed one.
- Installer issue: injury criteria passed but flail into adjacent structure not evaluated.
- Buyer concern: floor-track/attachment loads not reconciled with the airframe.
- Program risk: baseline does not match the delivered records.
How the work runs
Frame Seat Restraint
Confirm the exact event, affected file set, buyer role, and decision standard before any run-time test reports for the horizontal and vertical pulses is treated as sufficient.
Trace C127 Evidence
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 Run Time
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Testing Injury
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.
- structures engineers use the register to assign closure.
- Product managers use the request list to collect source records.
How the work fits into the transaction or program
What an aircraft seat and restraint system must substantiate for TSO-C127, distinct from any cabin-interior page because the decisive evidence is active (16g) crash-pulse testing against injury criteria (HIC, femur/lumbar loads), seat-structure retention, and occupant-flail/egress behaviour. The evidence set centers on active test reports for the horizontal and vertical pulses, injury-criteria measurements, structural retention and floor-track load data, flammability of seat materials. The likely weak points are active tests run on a seat configuration that differs from the installed one, injury criteria passed but flail into adjacent structure not evaluated, and floor-track/attachment loads not reconciled with the airframe. The output gives the certification engineer a cleanup register for Seat and restraint TSO-C127 evidence for run-time 16g testing and injury criteria before seat qualification planning.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
EE does not issue approvals, make compliance findings, approve manuals, or determine airworthiness. The review gives the applicant, designee, buyer, or authority-facing team a clear evidence record for their own decisions.
Specific to this review
- what an aircraft seat and restraint system must substantiate for TSO-C127, distinct from any cabin-interior page because the decisive evidence is run-time (16g) crash-pulse testing against injury criteria (HIC, femur/lumbar loads), seat-structure retention, and occupant-flail/egress behaviour.
- Run-time test reports for the horizontal and vertical pulses often controls whether later summaries can be trusted.
- Run-time tests run on a seat configuration that differs from the installed one 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 Seat Restraint TSO C127 question as the control point, so the review stays tied to Seat qualification planning and the buyer decision behind it.
- The evidence starts with Run-time test reports for the horizontal and vertical pulses and follows Evidence Certification Run Time 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 16g Testing Injury Criteria 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 Seat Restraint TSO C127; 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).
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
Frequently asked questions
What makes this product-types review different from a general file audit?
The scope is tied to seat restraint tso c127 and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block seat qualification planning or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is run-time test reports for the horizontal and vertical pulses, 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.