UAS Guide Romania

Drone flight log: what UAS pilots must record

EU Regulation 2019/947 requires operators to keep records of UAS operations. The flight log proves you planned, executed, and documented missions under open, specific, or certified rules. In Romania it complements UAS map, NOTAM, and MoD clearance checks. This guide covers essential fields, retention, audit-ready examples, and how Drone Log automates repetitive documentation without replacing pilot responsibility.

What EU 2019/947 requires for operation records

Operators must maintain operation information: date, location, duration, mission type, UAS and pilot ID, risk mitigations. Even recreational pilots benefit at incidents and inspections. Read how Drone Log works.

Include NOTAM references, UAS zones checked, landowner consent, MoD or AACR authorisations. See flight log guide.

Digital logs beat lost notebooks — search, export, attachments. Drone Log is built for this workflow.

What to record before, during, and after flight

Pre-flight: coordinates, route, max altitude, UAS type, pilot competency, UAS/NOTAM checks with references, weather, ground risk, landowner consent.

Post-flight: take-off/landing times, deviations, incidents, battery use. If cancelled due to NOTAM, note code and decision. Link UAS map verification in the same entry.

Commercial: client, purpose, contract, insurance. Attach MoD clearance or flight approval PDFs.

Manual log vs app — pros and pitfalls

Paper works if complete and stored safely. Spreadsheets lack standardisation. Dedicated apps enforce minimum fields and link map checks to log entries.

Pitfall: ticking boxes without real checks — worse than no log. See legal flight guide.

Export backups periodically. Drone Log allows mobile entry right after landing.

Open category vs specific regime logging

Open category: simple but complete proof of checks. Specific/certified: aligned with operations manual, signatures, safety metrics.

Registered operators must present records to AACR on request. See flight request guide.

Multi-pilot teams: separate accounts and clear mission roles in Drone Log.

Good entries and audit checklist

Good: dated coordinates, UAS type, competency, map/NOTAM references, weather, consent, duration, no incidents — reconstructible.

Bad: “Flight Cluj, ok.” Audit checklist: time, place, UAS, pilot, category, geo/NOTAM, weather, consent, authorisations, duration, incidents.

Link to drones Romania for legal context. Drone Log builds compliance packages without hours of admin.

Retention, GDPR, and long-term practice

Retain operational data per UAS and contract requirements. Identifiable persons in imagery fall under GDPR — separate technical log from commercial deliverables.

Off-site backup, restricted access. Archive departing pilots' entries. Standardise AGL vs AMSL and WGS84 coordinates.

Five minutes in Drone Log after landing beats hours explaining an undocumented incident. Make logging the mandatory last step, like NOTAM is the first.

FAQ — drone flight log

Operation records are required for operators under EU 2019/947. Logs protect you at incidents.

Depends on operation type — often several years for commercial. Check AACR requirements.

The log documents map checks. Drone Log attaches verification to the same entry.

DJI logs are useful but incomplete for UAS compliance (NOTAM, clearances). Centralise in Drone Log.

Log date, planned location, reason, references — documented cancellation shows process.

Insurers may request records at claims. Complete logs with geo checks help.

Recommended pages

Drone Log guides

Blog articles

Drone Log helps you organise checks and documents. It does not replace applicable regulations — verify official sources (AACR, ROMATSA, MoD, EASA) before every flight.

Create free account Sign in All guides Blog