Educational familiarization only. This is original TechOpsBase learning content created from privately supplied legacy training and MSG-3 source material. It does not reproduce manufacturer pages, proprietary diagrams, task steps, numerical maintenance limits, dispatch criteria or controlled maintenance data. Current approved aircraft data, effectivity and operator procedures govern all aircraft work.
Resource profile
- Aircraft: Airbus A350 family
- ATA chapter: 38 — Water/Waste
- Resource: A350 ATA 38 Maintenance and Troubleshooting Workshop
- Level: Intermediate-to-advanced
- Status: Draft pending technical review
Learning objectives
- Build a diagnostic plan.
- Separate local and common failures.
- Use physical-fluid evidence with BITE.
- Work safely around water/waste contamination.
- Verify full restoration.
1. Purpose and operational value
The workshop applies flow-path, control-path and safety-boundary reasoning to realistic ATA 38 faults.
2. Architecture and system flow
Begin by classifying the complaint: potable supply, servicing, vacuum toilet, waste-tank or gray-water drainage.
Then map the physical flow and control/indication path separately.
Do not reset, drain or service before preserving quantity, pressure, valve, bus and fault evidence when safe to do so.
3. Major components and functions
Evidence capture
Records quantity, pressure, affected consumers, tank state, phase and recent servicing. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes PWIP/FAP screenshots, BITE, fluid evidence and temperature history. Command, feedback and physical effect must agree before hardware is condemned.
Physical-flow isolation
Traces water, air, vacuum or waste path. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes pressure/flow checks, branch comparison and leak/blockage evidence. Command, feedback and physical effect must agree before hardware is condemned.
Control-path isolation
Traces command, feedback, power and CAN buses. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes command state, node communication and local override. Command, feedback and physical effect must agree before hardware is condemned.
Safety/hygiene control
Prevents contamination, pressure release or waste exposure. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes PPE, approved cleaning/disinfection and safe servicing. Command, feedback and physical effect must agree before hardware is condemned.
Restoration verification
Proves function, indications, leak tightness and correct configuration. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes normal use, servicing and remote/local agreement. Command, feedback and physical effect must agree before hardware is condemned.
4. Normal operating sequence
1. Make safe
Control electrical, pneumatic, fluid and contamination hazards.
2. Preserve
Save original status and servicing configuration.
3. Compare
Use another consumer, subsystem, panel or tank.
4. Localize
Separate physical flow from command/indication.
5. Repair/verify
Restore hardware, hygiene and full workflow.
5. Control, monitoring and protection
Temporary pressure or flush recovery does not prove the original cause is corrected.
A clean electronic test does not prove a pipe, seal, heater or valve is physically sound.
6. Failure modes and maintenance reasoning
- No pressure: Source, pump, valve, blockage or leak.
- No flush: Local toilet, vacuum, tank or bus.
- Wrong quantity: Sensor/transmitter/controller/display.
- Cannot service: Panel, interlock, valve, vent or external equipment.
- Leak/freeze: Pipe, valve, heater or drain mast.
- Contamination: Source, treatment, dead leg or incomplete disinfection.
7. Interfaces with other aircraft systems
- ATA 21/30/44/45.
- Ground servicing equipment.
- Cabin consumers.
- Electrical and pneumatic power.
- Approved hygiene and waste procedures.
8. Practical maintenance scenarios
Pump runs continuously
Find demand/leak or control issue before replacing pump.
One side toilets fail
Use forward/aft subsystem boundary.
Water quality complaint
Do not treat as a simple pressure fault.
Fault returns after reset
Use first-fault and physical evidence.
9. Technician takeaways
- Use both physical and electronic evidence.
- Contamination control is part of maintenance.
- One-consumer patterns matter.
- Verify local and remote indications.
Maintenance boundary
This resource explains architecture, operation, indications and system-level troubleshooting. It intentionally excludes removal/installation instructions, wiring-pin checks, maintenance limits, software part numbers, servicing quantities, inspection intervals and release-to-service criteria.
Review prompts
- What is the required system function?
- Which component commands, processes or physically performs it?
- Which power, fluid, pneumatic or data path is required?
- What command proves the function was requested?
- What feedback or physical effect proves correct operation?
- Which adjacent ATA system can create the same symptom?
- What evidence should be preserved before reset, draining, servicing or software action?
- What hygiene, electrical, pressure, network or safety boundary applies?
