A lavatory faucet that fires with nobody at the sink is almost never a dirty lens. In a 20 by 24 inch lav, the sensor is doing exactly what its detection window and reflectivity threshold tell it to do, and the trigger is usually a surface, a vibration, or an IR source inside that window that has nothing to do with a hand. Fixing it means finding the reflector, not replacing the faucet.
Sensor Range Limits in Tight Lavs
Most aircraft lav faucets use IR proximity sensors tuned for a 4 to 6 inch detection range, calibrated for a hand approaching the spout in a basin envelope that’s standardized across most narrowbody and widebody lav designs. That range is a compromise: wide enough to catch a hand reliably, narrow enough to reject ambient cabin motion. The problem is that a standard aircraft lav basin often puts the back wall, the mirror surround, or a soap dispenser housing within 8 to 10 inches of the faucet body. Anything reflective inside roughly double the rated detection distance can return enough IR signal to read as a target, especially if the surface is glossy laminate or polished metal trim.
This is why relocating a faucet during a cabin refresh, even by an inch or two toward the back wall, can turn a fixture that behaved fine on the bench into one that free-runs in the aircraft. The sensor spec sheet number is measured in open air, not against a lav’s actual reflective geometry.
Vibration and False Return Triggers
Cabin vibration during taxi, takeoff roll, and turbulence moves the faucet body and anything mounted near it by fractions of a millimeter, but that’s enough to shift the IR return signal’s phase or amplitude on some sensor designs, particularly capacitive-assist or older analog IR modules that infer distance from signal strength rather than time-of-flight. A vibrating faucet head effectively sweeps its own detection field across nearby surfaces, and a momentary return spike above threshold fires the solenoid the same way a hand would.
This shows up more on aft lavs near the APU or engine-adjacent structure, and it’s intermittent by nature, which makes it easy to misdiagnose as a wiring fault. If the phantom activations correlate with flight phase rather than ground power state, vibration coupling is the first thing to rule out before pulling the sensor module.
Cabin Lighting and IR Interference
Galley work lighting, LED mood lighting transitions, and even sunlight through a lav’s frosted vent panel can inject IR energy into the sensor’s receive window. Most aircraft sensor faucets filter for a modulated IR signal at a specific frequency to reject ambient light, but galley equipment with its own IR-based controls, or high-CRI LED fixtures with broader spectral output than older fluorescent cabin lighting, can occasionally sit close enough to the sensor’s passband to cause false reads. This is more of an issue during cabin lighting scene changes, when intensity ramps rather than sudden on/off states create a moving IR baseline the sensor has to track.
Retrofit programs that swap cabin lighting without re-verifying lav sensor behavior under the new lighting scenes are a common source of post-refresh service reports. The faucet didn’t change. The photon environment around it did.
Grounding, Bonding, and Vacuum System Noise
Vacuum lavatory systems run their own wiring for the flush motor, solenoid valves, and waste tank sensors, and that wiring shares structure and often shares a bonding point with the faucet’s control electronics. Electrical bonding per the aircraft’s structural bonding plan is there to control static and fault current, but a marginal bond, a corroded ground stud, or a harness routed too close to a vacuum generator’s motor leads can inject noise into the faucet’s low-voltage sensor line. A sensor module reading a noisy ground reference can misinterpret a transient as a valid target signal.
Sensor electronics used in these installations are qualified to DO-160 environmental categories covering conducted and radiated emissions susceptibility, so a compliant module should reject typical cabin EMI. Phantom triggers that trace back to noise usually mean a bonding or grounding installation defect rather than a sensor design failure, which is a useful distinction when deciding whether to open a discrepancy against the part or against the wiring.
Diagnosing Phantom Triggers on the Ground
Ground testing needs to reproduce the conditions under which the crew reported the fault, not just cycle the faucet on external power in a quiet hangar. A basic diagnostic sequence:
- Check basin geometry: measure sensor-to-back-wall and sensor-to-dispenser distances; anything under 12 inches is worth flagging for reflectivity testing, particularly on glossy surfacing.
- Run the flush motor and any nearby galley equipment while observing the faucet for correlated triggers, to isolate electrical noise from optical interference.
- Inspect the bonding strap and ground stud at the lav module’s electrical interface for corrosion or torque loss.
- Cycle cabin lighting through its full scene range, including transition states, not just full-on and full-off.
- If the aircraft has a history of vibration-correlated faults, test with the sensor module secured and unsecured to differentiate mounting-induced vibration from structural vibration.
Document flight phase, lighting state, and adjacent equipment operation for every reported event before swapping the sensor module. A part swap that doesn’t address a reflective surface or a bonding defect will produce the same complaint on the next flight.
Certification Limits on Sensor Recalibration
Field adjustment of sensor sensitivity or detection range is limited by the fixture’s original certification basis. A sensor faucet installed as part of a certified lav monument was qualified with a specific detection threshold as part of its approved configuration, and changing that threshold in the field, even to solve a nuisance trigger, can take the installation outside its approved data unless the change is covered by existing service instructions or goes through engineering disposition. This is different from a commercial building fixture, where a technician can turn a sensitivity dial and move on.
In practice this means most phantom-trigger fixes on certified installations focus on removing the interference source, reflective surface, EMI path, vibration coupling, rather than recalibrating the sensor itself. Where a sensor module needs replacement, it has to be a like-for-like part number or one covered by the applicable service bulletin, not a field-selected substitute with a different detection curve. For reference on how touchless sensor ranges and thresholds are documented in a non-aircraft context, manufacturer listings for touchless bathroom faucets typically state detection range and response time on the spec sheet, which is the same kind of data an MRO should be pulling from the aircraft fixture’s component maintenance manual before touching anything.
What to Check Before Writing Up a Sensor Fault
Before opening a component removal against a faucet reported as self-activating, confirm the basin’s reflective clearances, check bonding integrity at the lav electrical interface, and correlate reported events against flight phase and lighting state. Most phantom triggers trace back to geometry, vibration, or noise rather than a failed sensor. If none of those check out and the fault is repeatable on the bench under simulated cabin conditions, then the sensor module itself is a legitimate suspect, and replacement should follow the approved part number and any applicable service bulletin rather than a field substitution.
