The professional drone crossed a quiet border in recent years: it stopped being equipment and became a fleet. Line and structure inspection, aerial surveying, agriculture, public safety, support to crewed operations — serious RPA operation today has multiple aircraft, multiple pilots, a client demanding evidence and an insurer asking about history.
And here a paradox appears: the same operator that controls the crewed fleet rigorously usually manages the drones in a loose spreadsheet — when it manages them at all. Since RPA does not carry the documentary obligations of crewed aviation (there is no RAB or mandatory logbook for the typical operation), the illusion arises that there is nothing to control.
There is. And item number one is not what aeronautical intuition expects.
The battery is the drone's engine — with its life counted in cycles
In crewed aviation, the component that takes the aircraft off the line is the engine, and the unit of control is the hour. In RPA, the functional equivalent is the battery — and the unit that matters is the charge cycle.
The physics is familiar to those who operate: the lithium battery degrades with each cycle. Capacity drops, internal resistance rises, and the curve is not linear — the battery that "still works" may be delivering far less endurance than flight planning assumes, until the day the voltage drop under load becomes a forced landing. Or worse: a thermal incident in transport or charging.
That is why every serious operating recommendation converges on the same tripod:
- Identify each battery individually — name and serial number, not "the batteries of drone 2";
- Count cycles per battery — not by fleet estimate;
- Define service life in cycles and retire by criterion, not by failure — the degraded battery leaves service before it surprises you.
The problem is operational: counting cycles by hand does not survive routine. The operator who flies six missions in a day with three batteries in rotation will not update a spreadsheet at every battery swap — and within a month the control is detached from reality, which is the same as not existing.
The rest is a normal fleet — and deserves fleet treatment
Apart from the battery, the drone is surprisingly similar to the rest of the hangar: propellers with life limits, motors that accumulate hours, gimbal and sensors with calendar maintenance, firmware with controlled versions. It is classic maintenance tracking — hours, cycles and calendar — applied to smaller equipment.
And the documentary layer exists, even if different: registration in SISANT (ANAC, under RBAC-E No. 94), airspace access through SARPAS (DECEA), an insurance policy, the operation record that the client and the contract ask for. The operator that treats RPA as a fleet — and not as an accessory — arrives at these obligations with the data ready.
A detail that protects your CIV
Anyone who operates a drone and a crewed aircraft in the same company knows the statistical trap: drone hours are not pilot flight hours. Mixing the two records pollutes the declarable flight experience of the crew — and separating them by hand is guaranteed rework. The right control keeps the RPA flight recorded, with its own statistics, outside the pilot logbook and CIV of whoever flies.
How Alis handles this
The Alis drone module went live with a simple thesis: RPA is a fleet, and a fleet is managed together — on the same platform as the crewed operation:
- The drone joins the fleet as its own equipment, and RPA flights follow the same logging flow as the operation — with separate statistics: drone hours do not contaminate the pilot's logbook or CIV;
- Each battery is an individual: name, serial, cycles it already had when it came in, service life in cycles — and the cycles are added up automatically from the logged flights, with no parallel spreadsheet;
- Battery status with criteria: active, degraded or retired — the decision to take it out of service becomes management, not a reaction to a scare;
- Components in CTM like any aircraft: propellers, motors and calendar items with due dates and alerts;
- Complete trail: who flew, with which equipment, which battery, how many cycles — the evidence that the client, insurer and audit ask for.
If your operation already lives the routine of a crewed fleet, the reasoning is the same — only the size of the hangar changes: control that is born in the flight, an alert before the due date, and a record that proves what was done.
This article is informational and does not replace current regulations. Registration, operation and airspace requirements for RPA must be confirmed in ANAC's RBAC-E No. 94 and in the DECEA publications applicable to your operation.