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 Potable-Water Servicing Panels and Interfaces
- Level: Intermediate-to-advanced
- Status: Draft pending technical review
Learning objectives
- Identify service-panel equipment.
- Explain PWIP functions.
- Describe interlocks.
- Recognize filling/draining faults.
- Verify servicing closeout.
1. Purpose and operational value
The ground servicing interfaces allow controlled filling, draining, preselection, indication and manual backup while preventing unsafe panel closure or incorrect system configuration.
2. Architecture and system flow
The PWSP combines fill/drain and overflow connections with the PWIP and physical door/cap features.
PWSP door state can inhibit selected FAP functions and is displayed to cabin crew.
The forward drain panel provides access to the forward drain outlet and related servicing controls.
3. Major components and functions
PWIP
Controls and monitors ground 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 power, quantity, valve command/feedback and fault display. Command, feedback and physical effect must agree before hardware is condemned.
Fill/drain nipple and cap
Connect ground service hose and protect the port. 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 cap position, sealing and service flow. Command, feedback and physical effect must agree before hardware is condemned.
Overflow nipple/funnel
Allows ventilation and controlled overflow/drainage. 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 flow, heating and panel accumulation. Command, feedback and physical effect must agree before hardware is condemned.
PWSP door switch/interlock
Reports door state and prevents incorrect closure/control. 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 switch state, message and mechanical interlock. Command, feedback and physical effect must agree before hardware is condemned.
Forward drain panel
Supports forward-system drainage. 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 access, cap/connection and actual drainage. Command, feedback and physical effect must agree before hardware is condemned.
4. Normal operating sequence
1. Prepare
Open panel, verify power, quantity and connections.
2. Select
Set quantity or drain function.
3. Execute
PWIP sequences treatment and valves.
4. Observe
Monitor quantity, overflow and status.
5. Closeout
Disconnect, stow caps, close doors and verify normal indications.
5. Control, monitoring and protection
A service-panel door-open message can be a real door/switch condition and may intentionally inhibit FAP preselection.
Do not use panel indications as a substitute for leak and connection inspection.
6. Failure modes and maintenance reasoning
- No servicing power: Aircraft/ground power, PWIP or protection.
- Cannot fill: Connection, valve, vent, treatment or control.
- Overflow too early: Quantity sensing, vent restriction or incorrect configuration.
- Door message remains: Switch, alignment or cap/interlock.
- Cannot drain: Valve, outlet, blockage or trapped pressure.
7. Interfaces with other aircraft systems
- Electrical power.
- CIDS/FAP.
- ATA 30 panel/line heating.
- Tank quantity and valves.
- Ground servicing equipment.
8. Practical maintenance scenarios
PWIP works, no water enters
Check external equipment, nipple, valve and vent path.
FAP preselection unavailable
Check PWSP door state before software fault.
Water accumulates in panel
Inspect overflow/funnel/drain and panel closure.
9. Technician takeaways
- Servicing is a full workflow.
- Door/cap state is functional logic.
- Observe physical water flow.
- Complete closeout prevents later faults.
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?
