Checking flight restrictions is the most important activity in planning a drone mission. In Romania, restrictions can come from permanent UAS zones, temporary NOTAMs, MoD/MApN requirements, or local conditions. Ignoring any source can turn an apparently legal flight into an offence.

Sources of restrictions — at a glance

| Source | Type | Check frequency | |--------|------|-----------------| | ROMATSA UAS zones | Permanent / semi-permanent | Every flight | | NOTAM | Temporary | On flight day, before takeoff | | MoD/MApN clearance | Per-operation authorisation | Per operation | | Open category rules | General legal requirements | Every flight |

Step 1: Identify the exact location

Define:

  • GPS coordinates of the takeoff point
  • Radius of the operation (how far you will fly)
  • Maximum planned altitude
  • Approximate trajectory

The more precisely you define the area, the more reliable the check.

Step 2: Check UAS zones

Open the UAS map (ROMATSA or Drone Log) and confirm:

  • whether the point is inside a coloured zone
  • what restriction category applies (prohibited, conditional, informational)
  • whether there are different altitude limits

Related articles: UAS zones · Prohibited zones

Step 3: Check NOTAMs

NOTAMs can appear after you checked the zone yesterday. Verify:

  • NOTAM series relevant to Romania
  • UAV NOTAM layers on the ROMATSA map
  • NOTAM aggregation on Drone Log

Read: What is a NOTAM

When to re-check NOTAMs

  • On the morning of the flight
  • 1–2 hours before takeoff
  • If the flight lasts many hours — mid-day

Step 4: Assess whether MoD/MApN clearance is needed

If the map indicates a military or sensitive zone:

  • start the HG 859 request in good time
  • do not fly until you receive written confirmation
  • re-check NOTAMs after receiving clearance

Step 5: General rules (beyond the map)

Even if the map looks "green":

  • distance from airports (according to your subcategory)
  • VLOS — keep the drone in visual line of sight
  • Uninvolved persons — minimum distances
  • Private property — respect privacy
  • Flight times — some night operations require special conditions

Step 6: Document the check

Record in your logbook:

  • date and time of the check
  • sources consulted
  • result (permitted / conditional / prohibited)
  • relevant NOTAM IDs
  • clearances applied

Documentation demonstrates the operator's due diligence.

  1. Enter the location on the map
  2. Review UAS + NOTAM layers
  3. If OK — generate a logbook entry directly from the check
  4. If clearance is needed — start the HG 859 workflow
  5. After the flight — complete duration and observations

Warning signs — stop the flight

  • Active NOTAM in your area
  • Expired or missing MoD/MApN clearance
  • Helicopters or aircraft present in the area
  • Unforeseen event (gathering, police, fire)
  • Dangerous weather conditions

Conclusion

Checking restrictions is not a box to tick mechanically — it is the pilot's professional judgement. Combine UAS zones, NOTAMs, clearances, and general rules; check twice on flight day; and document everything. That is how you operate legally, safely, and with peace of mind.