Aircraft exterior washing sits at the awkward intersection of two worlds that rarely speak to each other: the maintenance crew that controls the work, and the compliance department that has to prove it was done properly. Hand the task to a shared spreadsheet and you get the familiar failure pattern: some people write the work down in too much detail, some people skip items on busy days, and nobody can agree afterwards on what "clean" was supposed to mean. A written cleaning checklist is the simplest fix, provided it is built around three things: clear zones on the airframe, defensible intervals, and a signature you can produce when someone asks.
Start with the airframe zones, not the tasks
A checklist that lists activities ("wash the aircraft") is difficult to verify, because nobody can tell which parts were reached. Divide the airframe into a small, fixed set of zones and make the crew confirm each one. A practical division for a light or general-aviation aircraft looks like this:
- Upper fuselage, canopy or windscreen, and glazing
- Lower fuselage, nose landing-gear bay, and wheel wells
- Leading and trailing edges of the wings, control surfaces, and static ports and probe areas
- Empennage and control surfaces on the tail
- Powerplant area, cowlings, and any accessible engine surfaces
- Ground-support area: stands, steps, hoses, and waste recovery
Six or seven zones is usually the limit of what a two-person crew will actually complete on a line turnaround. Anything finer turns into paper that gets initialled without being read.
Match frequency to the operating environment, not to a template
Fixed calendar intervals are a starting point and often wrong. An aircraft based near a coastal site, a farm, or a busy apron with heavy ground-traffic dust accumulates contamination far faster than the same type stored in a hangar inland. Build the checklist so the interval is stated in two ways: a maximum period, plus a trigger condition that shortens it. Useful triggers include visible residue on the leading edges, insects or organic deposits on the windscreen after a season of low-level flying, oil or hydraulic traces around the engine area, and any aircraft returned from an unpaved or agricultural strip.
Write the interval column as "at least every X days, or when condition Y appears". That phrasing forces the person scheduling the work to justify a delay, instead of defending a date.
State the method and equipment next to the zone
A checklist that says "cleaned" and lets each technician improvise produces inconsistent results across shifts. Name the approved method for each zone and reference the equipment by model so the wrong machine is not grabbed from the store. This is where specifying the wrong machine does real damage. A unit intended for a hard shop floor is too heavy to move around an airfield, while a light domestic appliance will not deliver the steam temperature and pressure that compacted grease and organic film actually need.
Where the operation needs high-temperature steam at controlled pressure rather than a plain pressure wash, that capability is a separate equipment class: aircraft exterior cleaning equipment on the PowerDe cleaning range covers mobile and fixed high-pressure steam units that switch between dry and wet steam. Dry steam carries less free water, which matters around airframes where you want the surface to fall dry and where standing water on apron or in a bay is a hazard. For a checklist this means the method column can name one approved machine and one mode per zone instead of leaving it open. Any decision on approved materials, detergents, or pressure limits must still follow the airframe manufacturer's maintenance documentation; the checklist records the site's practice, it does not replace that documentation.
Add the items people forget
Most disputes after an inspection are not about the fuselage. They are about the things nobody photographed. Put these lines in the checklist explicitly:
- Confirmation that static ports, pitot tubes, and probes were protected or cleared before and after washing
- Confirmation that no water or cleaning agent was directed into openings, vents, or avionics bays
- Drain and waste recovery: where rinse water went, and that it was not released to the apron drainage
- Post-wash visual check for damage, blistering, or coating loss found during cleaning, with a defect-report number if anything was seen
- Equipment check-out: tank filled, hoses and nozzles intact, unit returned and logged
Make sign-off mean something
A usable checklist has two signatures per line: the person who did the zone, and the person who released the aircraft. Add a free-text column for exceptions, because a form with no space for "why was this skipped" simply gets crossed out. Keep the whole thing to one page per aircraft so it can be completed in the field rather than at a desk afterwards.
Finally, review the checklist itself on a fixed cycle, quarterly at least. Ask which lines were always ticked identically and can be simplified, and which defects keep appearing that justify a stricter interval. The document earns its place by changing, not by being filed.
