Read the aircraft before the log

Preserve the evidence before cleaning

Dust patterns, staining, witness marks and displaced labels may help explain a problem. The intake process should capture relevant condition before cleaning or disassembly alters it. Photographs should show context as well as detail: a close-up without a recognizable location can become difficult to interpret later. Include the affected aircraft identifier in the record rather than depending on an image filename alone.

A good operator handover describes what happened, when it happened and what changed afterward. Record an abnormal landing, water exposure, transport impact, unusual sound or repeated warning in neutral language. Do not turn an observation into a diagnosis prematurely. “A vibration warning appeared after a propeller replacement” preserves a useful sequence; “the motor is defective” may narrow the investigation without evidence.

Look at interfaces, not just surfaces

Airframe inspections commonly consider joints, arm mechanisms, attachment points, landing structures and propulsion interfaces. However, the exact inspection method, access requirements and acceptable limits must come from applicable instructions. This article deliberately provides no universal torque values, crack limits or bearing-clearance tolerances. A number transferred from another model can make an otherwise careful inspection unsafe.

Ask how the center distinguishes a cosmetic mark from suspected structural damage. The answer should describe the relevant reference and escalation path, not simply the technician’s confidence. If a finding falls outside published limits or workshop authority, a manufacturer consultation or specialist assessment may be necessary. An unresolved finding should remain visible in the report instead of disappearing beneath a general “passed” statement.

Separate routine checks from event-driven work

A scheduled visit is not necessarily an adequate response to an impact, immersion or persistent flight anomaly. An event can require a different scope, including checks beyond the visibly affected area. The operator should preserve relevant logs and avoid repeatedly powering or operating equipment merely to reproduce a potentially unsafe symptom. Obtain model-specific advice on handling and isolation before further testing.

Operating environment also matters. Coastal salt exposure, abrasive dust, agricultural chemicals and frequent vehicle transport create different histories. These factors do not authorize invented maintenance intervals. They do justify asking whether the manufacturer specifies additional precautions, inspection triggers or approved cleaning methods. Record the environmental context so that later trends have a meaningful explanation.

Understand what verification proves

After an intervention, ask which checks were performed and what each one establishes. A visual inspection, a powered diagnostic and a controlled operational test answer different questions. A successful powered check does not automatically verify performance under every payload, temperature or mission condition. The report should identify the test conditions, outcome and limitations without implying a universal guarantee.

For UK operations, consult the Civil Aviation Authority’s current unmanned-aircraft guidance, including the relevant CAP 722 material. In the European Union, EASA guidance and Regulations (EU) 2019/947 and 2019/945 provide important operational and product context. In the United States, FAA Part 107 is an operational framework. None of these references substitutes for the aircraft’s maintenance instructions or establishes that a workshop is approved for your specific work.

Before returning an aircraft to the dispatch pool, reconcile the service findings with your own procedures. Confirm that unresolved defects, configuration changes and any required follow-up are understood by the responsible personnel. This website does not issue airworthiness findings or flight-clearance decisions.