EN

Comparison: manual vs. automated

Drone Log vs. the manual flight verification process

Manually checking a drone flight means opening several official sources, reading NOTAMs in PDF and entering coordinates by hand. Drone Log automates these steps and cuts the time from ~15 minutes to ~2 minutes.

2 min
verification time with Drone Log
4
steps instead of 8
-87%
time saved per flight
0
PDFs to download manually

Step-by-step comparison

Step Manual Drone Log
Estimated time ~15 minutes ~2 minutes
Number of steps ~8 steps 4 steps
UAS zone check Manual search on the ROMATSA map Automatic, on an interactive map
Reading NOTAMs Manual PDF, coded text Automatic, in plain language
Coordinates Entered manually Automatic (GPS / click on map)
Flight log Filled in manually Generated automatically
Total ~15 minutes, 8 steps ~2 minutes, 4 steps

Benefits of automation

✓
Faster

Cut pre-flight preparation time by over 85% — check zones and NOTAMs from a single place.

✓
Fewer errors

Coordinates and restrictions are filled in automatically, removing manual transcription mistakes.

✓
Always up to date

UAS zones and NOTAMs are imported automatically from official sources, with the last update date shown.

✓
Automatic documentation

The flight log and documents are generated automatically, ready to present when needed.

Anonymised examples of generated requests

These examples show what HG859 documents look like when generated from Drone Log after a map check. All data is fictional and anonymised — not from real users.

Demonstration only. Always verify current authority requirements and official sources before submitting.

PDF preview

Open PDF

The document is generated with the same PDF engine used in your account. For a real submission you use your profile data and map check.

Field explanations

UAS zone (name / ID)

ROMATSA map zone identifier, taken automatically when the flight point is in a restricted area.

Operator / applicant

Name from your pilot/UAS operator profile. Anonymised in these examples.

Phone and email

Contact details from your profile for authority follow-up. Not published in these examples.

UAS operator number and remote pilot certificate

The UAS operator registration number (without its 3 secret characters) and the remote pilot certificate, on separate rows, from your account profile.

Type, manufacturer, model, MTOW

Selected aircraft from your fleet — type, maximum take-off weight and sensor equipment.

Registration / identification

UAS registration code and aircraft serial from the drone record in your account.

Flight purpose and operation category

Activity description (filming, inspection, etc.) and operational category declared at generation.

Date / operation period

Planned interval from the map (start and end), shown as summary and in ISO format.

Minimum / maximum heights

Vertical limits set when planning the flight and the pre-check reference altitude.

Take-off / landing coordinates

Latitude and longitude from the point marked on the map — not entered manually.

Area of operation

Perimeter or reference point description from the pre-check; GIS attachments may be added when submitting.

PDF preview

Open PDF

The document is generated with the same PDF engine used in your account. For a real submission you use your profile data and map check.

Field explanations

UAS zone (name / ID)

ROMATSA map zone identifier, taken automatically when the flight point is in a restricted area.

Operator / applicant

Name from your pilot/UAS operator profile. Anonymised in these examples.

Phone and email

Contact details from your profile for authority follow-up. Not published in these examples.

UAS operator number and remote pilot certificate

The UAS operator registration number (without its 3 secret characters) and the remote pilot certificate, on separate rows, from your account profile.

Type, manufacturer, model, MTOW

Selected aircraft from your fleet — type, maximum take-off weight and sensor equipment.

Registration / identification

UAS registration code and aircraft serial from the drone record in your account.

Flight purpose and operation category

Activity description (filming, inspection, etc.) and operational category declared at generation.

Date / operation period

Planned interval from the map (start and end), shown as summary and in ISO format.

Minimum / maximum heights

Vertical limits set when planning the flight and the pre-check reference altitude.

Take-off / landing coordinates

Latitude and longitude from the point marked on the map — not entered manually.

Area of operation

Perimeter or reference point description from the pre-check; GIS attachments may be added when submitting.

PDF preview

Open PDF

The document is generated with the same PDF engine used in your account. For a real submission you use your profile data and map check.

Field explanations

UAS zone (name / ID)

ROMATSA map zone identifier, taken automatically when the flight point is in a restricted area.

Operator / applicant

Name from your pilot/UAS operator profile. Anonymised in these examples.

Phone and email

Contact details from your profile for authority follow-up. Not published in these examples.

UAS operator number and remote pilot certificate

The UAS operator registration number (without its 3 secret characters) and the remote pilot certificate, on separate rows, from your account profile.

Type, manufacturer, model, MTOW

Selected aircraft from your fleet — type, maximum take-off weight and sensor equipment.

Registration / identification

UAS registration code and aircraft serial from the drone record in your account.

Flight purpose and operation category

Activity description (filming, inspection, etc.) and operational category declared at generation.

Date / operation period

Planned interval from the map (start and end), shown as summary and in ISO format.

Minimum / maximum heights

Vertical limits set when planning the flight and the pre-check reference altitude.

Take-off / landing coordinates

Latitude and longitude from the point marked on the map — not entered manually.

Area of operation

Perimeter or reference point description from the pre-check; GIS attachments may be added when submitting.

In short

Drone Log reduces pre-flight verification from about 15 minutes and 8 manual steps (ROMATSA maps, NOTAM PDFs, manually entered coordinates) to roughly 2 minutes and 4 steps, with official data imported automatically and a flight log generated automatically.

Frequently asked questions

On average you go from ~15 minutes of manual checks to ~2 minutes, because UAS zones, NOTAMs and coordinates are filled in automatically.

No. Drone Log aggregates and presents official data in a fast-to-check format, but the final confirmation remains the pilot's responsibility, from primary sources.

Checking UAS zones, reading NOTAMs in plain language, entering coordinates and filling the flight log are done automatically instead of manually.
Create a free account Open the Romania UAS map How to use Drone Log Compared with the ROMATSA map, AEROFOTO and DJI FlySafe