The AlphaTango annual activity report: a January guide

The annual activity report ('bilan annuel d'activité') is the declaration an operator makes every year on AlphaTango, the DGAC portal, to account for the past calendar year. AlphaTango's online help sums it up in one sentence: the previous year's annual activity report must be filed every year in January.

• When: in January, for the previous calendar year (the January 2027 report covers 2026).
• What: the flight hours per operational scenario and per activity domain, and the incident summary.
• Where: on AlphaTango, from the 'Mon activité professionnelle' (My professional activity) section.
• Who: the operator who declared an activity on AlphaTango — the operator files the report, not its remote pilots.

The obligation comes from the arrêté of 3 December 2020 on the national standard scenarios. Point 3.3.4 of its annex reads: every year in January, the operator declares to the minister in charge of civil aviation the number of flight hours flown and summarises the problems met in the safety monitoring during the previous calendar year.

The national standard scenarios S1, S2 and S3 have ended: according to the DSAC Specific-category guide, since 1 January 2026 only the European standard scenarios apply. The same guide, in its March 2026 edition, still lists the annual activity report among the rules a UAS operator must follow, and AlphaTango's help still asks for it every January.

AlphaTango's help lists two blocks, and the arrêté details the second:

Hours are declared for the calendar year, 1 January to 31 December: the date of the flight counts, not the day the mission was planned or invoiced. A flight flown on 31 December belongs to the year that ends, even when the mission was planned for 2 January.

The incident summary is not limited to accidents. A lost link, a triggered return-to-home, a battery failure, a flight cut short in an emergency: this is the safety monitoring your operations manual organises. A year with no event at all is possible; an empty section while your logs tell of several is not.

1. 1Sign in to AlphaTango with the operator's account.
2. 2Open the 'Mon activité professionnelle' (My professional activity) section.
3. 3Click the calendar icon, top right.
4. 4Enter the hours per scenario and per activity domain, then the incident summary, and submit.

The report joins the history of your procedures. If you find a mistake afterwards, AlphaTango does not edit a filed report: you write a new one. The old one stays in the history, but for a given year only the most recent report is authoritative. The second report must therefore be complete, not just the corrected line.

For the rest of the portal — delegation, aircraft declaration, operator information statement — see our AlphaTango operator guide.

• Rebuilding the year in January — without a log kept as you go, hours are estimated from memory, and the gap shows at the first inspection.
• Putting a flight in the wrong year — a late-December flight counted with the January mission that followed it, or the reverse.
• Forgetting flights never closed — a flight flown but left open in your tool appears in no total.
• Leaving missions without an activity domain — the split per domain becomes a guess.
• Mixing categories — open-category hours do not go under a standard scenario.
• Correcting one line only — a corrective report replaces the old one for the year: it restates everything.
• An incident summary left empty by reflex, while events are recorded in your logs or reports.

The report is prepared all year long, not in January:

• ☐ Every flight is dated by its take-off and landing, and closed the same day.
• ☐ Every mission carries its scenario and activity domain from preparation onwards.
• ☐ Every safety event is noted when it happens, with the measure taken.
• ☐ Flight logs are kept: the DSAC asks for their traceability over 3 years, and an inspection compares them with your reports.

Dronops computes your figures, you copy them into AlphaTango. The 'Annual activity report' page of your operator area does the year's sums from your completed missions:

• the flight hours per standard scenario and the split per activity domain, laid out in the order of the AlphaTango form;
• each mission counted in the year of its first logged flight, or of its planned date when none was logged;
• where the hours come from: stamped at take-off and landing, entered by hand, estimated, or failing that the operating window, flagged as overstated;
• the year's flights still to close, the flights declared on AlphaTango but never confirmed and the missions without an activity domain, flagged before you copy anything;
• what remains to complete in AlphaTango — safety monitoring and the commitment — with a link to the portal.