In Romania, some drone flights can be performed without extra approval, while others require coordination before take-off. The difference depends on the UAS map, NOTAMs, exact location, altitude, time and purpose.
Key information
- Approval is decided by the exact point and operation area, not by the town name.
- Check the UAS map, NOTAMs and vertical limits before preparing documents.
- Core data: operator, pilot, drone, location, time window, altitude, purpose and safety measures.
- Military or sensitive operations may also require MoND clearance, separate from UAS zone approval.
- Do not take off in a zone requiring approval until you have written confirmation valid for the planned window.
- Drone Log can generate documentation from the map check; you submit it to the indicated authority. The app does not issue or guarantee approval.
What this means for you
Treat the request as part of flight planning, not a last-minute admin step. Clear data makes the request easier to understand and process.
Before sending documents, check if you need approval. Then generate the approval request or read about the HG 859 request and flight approval in Romania.
When approval is needed
Not every flight needs approval, but every flight needs checking. In practice, approval matters when the zone, altitude or operation context adds a restriction.
- You fly in a restricted or controlled area, or near an aerodrome/CTR, as shown on the UAS map.
- The zone displays a contact or explicit coordination instruction before flight.
- A NOTAM affects the planned location, time or altitude.
- The operation involves filming/photography in a sensitive or military area, where MoND clearance may also apply.
- The operation has higher risk: large area, long duration, infrastructure proximity or significant altitude.
Recommended steps to request approval
-
Check the exact area on the map
Mark the take-off point and operation area, not just the locality. Two nearby points can fall under different restrictions.
-
Set the real time and altitude
The request must match the field plan. If you change time or altitude, re-check NOTAMs and zone conditions.
-
Identify the authority/contact
In zone details, check who should be contacted: tower/control, zone administrator, military structure or other official channel.
-
Prepare pilot and operator data
Include name, contact data, UAS operator ID, relevant certificates and drone data: model, serial number, weight and identification.
-
Describe the operation clearly
State purpose, coordinates, radius/perimeter, maximum altitude, local/UTC time, duration, safety procedure and responsible person.
-
Generate the documents
In Drone Log you can start from the UAS map: set the flight, check the area and use the request generation button for PDF/DOCX documents.
-
Submit and track the answer
Send documents through the indicated official channel and keep the response. In the app you can track prepared, sent, approved, rejected, expired or more-info status.
Generate request documentation in Drone Log
The flow starts from the UAS map: complete your pilot profile, choose the drone, set the flight, draw the operation area, check the status and generate the documentation needed to request approval. Documents remain in your account; you send them from your own email. The app does not issue or guarantee approval.
Practical examples
Below are three anonymised scenarios with PDF preview and an explanation for each field filled in automatically from the map and your profile.
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.
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.
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.
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.
Common mistakes to avoid
- Submitting the request without clear coordinates or only with a locality name.
- Using local time without clarifying UTC when required.
- Ignoring temporary NOTAMs because the permanent zone looked allowed.
- Submitting too late for an operation needing analysis or extra clearance.
- Taking off based on informal conversation without written valid confirmation.