T70X Engine Indications Test Set

A T70X variant within the ULTRAX engine-indications-to-cockpit family for firewall-forward engine-versus-airframe separation.

T70X Engine Test Set product image.
What it is

The T70X configuration extends UxValidator Series II into engine indication domains. It supports end-to-end observation of engine indication signals from the firewall to the cockpit, helping separate engine indication behavior from airframe effects when troubleshooting and verifying condition.

Family context

T70X is one variant within the broader Engine Indications to Cockpit family. The S-70i/M Engine Indications Test Set and Navy / Coast Guard CSIE configurations apply the same firewall-forward logic in their own service environments.

Dependency

This configuration operates in conjunction with the UxValidator Series II platform and is not a standalone solution.

What it enables

By observing indication behavior across the full signal path, the T70X configuration improves comparability across events and supports clearer interpretation when symptoms are ambiguous. This reduces defensive action driven by uncertainty and strengthens confidence in decisions made within existing procedures.

Role in Condition-Based Intelligence™
  • Listen: disciplined observation of engine indication behavior across the signal path
  • Know: preserves comparable context across runs and maintenance events
Primary connection scheme

Firewall-anchored vs DCU-anchored indication evaluation

ULTRAX intentionally operates firewall-forward—not as a hardware constraint, but as a sustainment strategy. The firewall represents the boundary where ambiguity first enters engine–airframe decision-making, making it the most stable and informative place to anchor indication evaluation.

Both T70X and EICAS configurations support cockpit-facing indication evaluation. The distinction is not what they display—it is where the indication path is anchored, and what that implies for long-term stability, coverage, and problem isolation.

The T70X configuration anchors at the engine firewall, a durable boundary point that remains relevant even as downstream avionics evolve. By observing indications from this location, maintainers can separate the troubleshooting domain early—distinguishing engine-related behavior from airframe-related behavior before ambiguity escalates.

EICAS configurations typically connect at the DCU. That anchor point is more sensitive to future DCU changes, may be harder to access in practice, and does not cover the distance between the firewall and the DCU—leaving additional indication path unobserved when ambiguity appears.

By reducing ambiguity before a removal decision is forced, firewall-anchored evaluation helps prevent short-term availability losses that can feel like obsolescence—especially in limited-size fleets where a single precautionary swap can ground the mission.

Dimension T70X configuration
Engine firewall connection
EICAS configuration
DCU connection
Primary connection point Engine firewall DCU
Stability over time Durable anchor point; less sensitive to avionics evolution, including DCU changes Sensitive to DCU revisions and avionics changes
Problem-domain isolation Separates engine-side domains from airframe-side domains, allowing faster isolation Couples troubleshooting to the DCU domain, making isolation less direct
Coverage of indication path Covers the full path from firewall to cockpit Covers DCU-to-cockpit; does not cover the firewall-to-DCU segment
Setup practicality Firewall access is generally straightforward and repeatable May require awkward access depending on aircraft configuration
Operational implication Reduces ambiguity by bounding the troubleshooting area early Can leave part of the indication path unobserved, requiring additional troubleshooting

Both approaches reveal indications at the cockpit. The distinction is not visibility, but how much of the system is observable, how early ambiguity can be bounded, and how resilient the configuration is as avionics architectures evolve.

Aircraft & configuration applicability
  • H-60A/L/V — T70X engine indication domains (configuration-dependent)
  • HH-60W — T70X engine test set configuration
  • S-70i/M — engine indications configuration
Part numbers & variants
  • 17-0518-00 — T70X Engine Test Set (H-60A/L/V)
  • 18-1130-00 — T70X Engine Test Set (HH-60W)
  • 18-2120-00 — S-70i/M Engine Indications Test Set
Lifecycle & continuity

As additional engine-indications-to-cockpit configurations are introduced, this family expands on the same UxValidator foundation alongside S-70i/M and Navy / Coast Guard CSIE variants—increasing coverage without replacing the platform or resetting the decision environment.

Manuals & Firmware
ServicePart NumberApplies ToNIINManualsService Pack Rev
US Army17-0518-00H-60A/L/V01-695-0225T70X Engine Test Set Maintenance Manual, PN 17-0828-01, Rev 55
US Air Force18-1130-00HH-60W01-708-6066T70X Engine Test Set Maintenance Manual, PN 18-1130-40, Rev 62
S-70M/i18-2120-00S-70i/MT70X Engine Test Set Maintenance Manual, PN 18-2120-30, Rev 13

*Not a calibrated item; no firmware required.