Coordination of Unmanned Aircraft System Operations

Coordination of unmanned aircraft system (UAS, drone) operations with controlled civil or military airports (TWR – control tower), with aerodrome flight information service at an uncontrolled airport (so-called “towerlet” AFIS or RADIO), or with heliport operators and ULL strip operators (for ultralight aircraft).

Flying a drone in these places requires increased attention and coordination (agreement) with the relevant ATS units. The purpose of this coordination is not to restrict drone pilots, but to ensure safety in shared airspace – so that drones and manned aircraft can safely remain separated.

LKPR (Prague)

If you plan a drone flight (subject to operator registration) in the inner part of the controlled zone (CTR), marking the flight plan in the digital map DroneMap is mandatory, regardless of altitude. In the outer part of the CTR, mark only those flights whose height above ground exceeds the grid value.

Before that, any flight exceeding the grid value must be coordinated – proceed as follows:

a) If you plan a drone flight above the grid value in the inner part of CTR Prague-Ruzyně, send no later than 3 working days before the planned flight:

  1. a request for a UAS flight in CTR LKPR to the airport operator (Prague Airport) electronically via this form, and at the same time
  2. a request for a non-standard type of UAS flight to the control tower via the ANS CR e-mail address: amcpraha@ans.cz with the following details:
  • Operator identification (name/company name, registration number);
  • Mobile phone contact for the remote pilot (and name if different from the operator);
  • Date of planned operation, take-off time (specify whether local time or UTC – Coordinated Universal Time), flight duration, and requested coordination validity for possible repeated flights;
  • Take-off and landing location, area of operation or requested flight trajectory – map drawing and a list of coordinates describing the requested area;
  • Requested flight altitude in meters above ground (optionally also in feet above mean sea level – rounded to hundreds of feet);
  • Type, class label (if assigned /C0–C6/), weight, characteristic (maximum) dimension and color of the unmanned aircraft;
  • Purpose of the flight.

As part of the approval, additional conditions may be set:

  • Requirement to request tactical coordination and flight clearance from the aerodrome control tower by phone a certain time before the flight, or
  • Maintain continuous two-way communication with the control tower, and/or
  • Equip the drone with a secondary surveillance radar transponder.

b) If you plan a drone flight above the grid value in the outer (more distant) part of CTR Prague-Ruzyně, send only the request to ANS CR according to point a) 2.

Military, customs, or IZS (integrated rescue system) unmanned aircraft may handle coordination and flight clearance with ATS units immediately before entering the area by phone according to the contacts table in AIP CR, section GEN 3.3, table 3.3.6 ( https://aim.rlp.cz/ais_data/www_main_control/frm_cz_aip.htm ).

LKTB (Brno), LKMT (Ostrava), LKKV (Karlovy Vary)

If you plan a drone flight (subject to operator registration) in the inner part of the controlled zone (CTR), marking the flight plan in the digital map DroneMap is mandatory, regardless of altitude. In the outer part of the CTR, mark only those flights whose height above ground exceeds the grid value.

Before that, any flight exceeding the grid value must be coordinated – proceed as follows:

a) If you plan a drone flight above the grid value in the inner part of the CTR, send no later than 3 working days before the planned flight:

  1. a request for a non-standard type of UAS flight to the airport operator to the relevant e-mail address from the table:
Airport Code Contact (e-mail)
Brno LKTB dron@brno-airport.cz
Ostrava LKMT operation@airport-ostrava.cz
Karlovy Vary LKKV info@airport-k-vary.cz
  1. and at the same time send the request for a non-standard type of UAS flight to the control tower via the ANS CR e-mail address: amcpraha@ans.cz.

Both requests are identical in content and must include the following:

  • Operator identification (name/company name, registration number);
  • Mobile phone contact for the remote pilot (and name if different from the operator);
  • Date of planned operation, take-off time (specify whether local time or UTC), flight duration, and requested coordination validity for possible repeated flights;
  • Take-off and landing location, area of operation or requested flight trajectory – map drawing and a list of coordinates describing the requested area;
  • Requested flight altitude in meters above ground (optionally also in feet above mean sea level – rounded to hundreds of feet);
  • Type, class label (if assigned /C0–C6/), weight, characteristic (maximum) dimension and color of the unmanned aircraft;
  • Purpose of the flight.

As part of the approval, additional conditions may be set:

  • Requirement to request tactical coordination and flight clearance from the aerodrome control tower by phone a certain time before the flight, or
  • Maintain continuous two-way communication with the control tower, and/or
  • Equip the drone with a secondary surveillance radar transponder.

b) If you plan a drone flight above the grid value in the outer (more distant) part of the CTR, send only the request to ANS CR according to point a) 2.

Military, customs, or IZS (integrated rescue system) unmanned aircraft may handle coordination and flight clearance with ATS units immediately before entering the area by phone according to the contacts table in AIP CR, section GEN 3.3, table 3.3.6 ( https://aim.rlp.cz/ais_data/www_main_control/frm_cz_aip.htm ).

LKVO (Vodochody), LKKU (Kunovice), LKCS (České Budějovice)

If you plan a drone flight (subject to operator registration) above the grid value, do not forget to mark the flight plan in the digital map DroneMap. In the inner part of the controlled zone (CTR), marking is mandatory for any flight altitude.

Before that, any flight exceeding the grid value must be coordinated – proceed as follows:

No later than 3 working days before the planned flight, send one request for a non-standard type of UAS flight to both the airport operator and the control tower to the shared e-mail address from the table:

Airport Code Contact (e-mail)
Vodochody LKVO twr@aero.cz
Kunovice LKKU Form LKKU
České Budějovice LKCS airport@airport-cb.cz

The request must include the following:

  • Operator identification (name/company name, registration number);
  • Mobile phone contact for the remote pilot (and name if different from the operator);
  • Date of planned operation, take-off time (specify whether local time or UTC), flight duration, and requested coordination validity for possible repeated flights;
  • Take-off and landing location, area of operation or requested flight trajectory – map drawing and a list of coordinates describing the requested area;
  • Requested flight altitude in meters above ground (optionally in feet above mean sea level – rounded to hundreds of feet);
  • Type, class label (if assigned /C0–C6/), weight, characteristic (maximum) dimension and color of the unmanned aircraft;
  • Purpose of the flight.

As part of the approval, additional conditions may be set:

  • Requirement to request tactical coordination and flight clearance from the aerodrome control tower by phone a certain time before the flight, or
  • Maintain continuous two-way communication with the control tower, and/or
  • Equip the drone with a secondary surveillance radar transponder.

Military, customs, or IZS (integrated rescue system) unmanned aircraft may handle coordination and flight clearance with ATS units immediately before entering the area by phone according to the contacts table in AIP CR, section GEN 3.3, table 3.3.6 ( https://aim.rlp.cz/ais_data/www_main_control/frm_cz_aip.htm ).

Military controlled airports: LKCV (Čáslav), LKKB (Kbely), LKNA (Náměšť), LKPD (Pardubice)

All drone flights (subject to operator registration) in military controlled zones (MCTR) must be marked in DroneMap, regardless of altitude.

Coordination with airport operators and the control tower is mandatory if you plan:

  • a) any drone flight in the inner part of the MCTR, regardless of altitude (below or above the grid value), or
  • b) any drone flight above the grid altitude in the outer part of the MCTR.

The coordination procedure is the same in both cases:

No later than 3 working days before the planned flight, send one request for a non-standard type of UAS flight to both the airport operator and the control tower to the shared e-mail address from the table (for LKPD send to both addresses listed):

Airport Code Contact (e-mail)
Čáslav LKCV aro.lkcv@mo.gov.cz
Kbely LKKB maro.ais.lkkb@mo.gov.cz
Náměšť LKNA mtwr.lkna@mo.gov.cz
Pardubice LKPD twr.lkpd@mo.gov.cz
handling@airport-pardubice.cz

The request must include the following:

  • Operator identification (name/company name, registration number);
  • Mobile phone contact for the remote pilot (and name if different from the operator);
  • Date of planned operation, take-off time (specify whether local time or UTC), flight duration, and requested coordination validity for possible repeated flights;
  • Take-off and landing location, area of operation or requested flight trajectory – map drawing and a list of coordinates describing the requested area;
  • Requested flight altitude in meters above ground (optionally in feet above mean sea level – rounded to hundreds of feet);
  • Type, class label (if assigned /C0–C6/), weight, characteristic (maximum) dimension and color of the unmanned aircraft;
  • Purpose of the flight.

As part of the approval, additional conditions may be set:

  • Requirement to request tactical coordination and flight clearance from the aerodrome control tower by phone a certain time before the flight, or
  • Maintain continuous two-way communication with the control tower, and/or
  • Equip the drone with a secondary surveillance radar transponder.

Military, customs, or IZS (integrated rescue system) unmanned aircraft may handle coordination and flight clearance with ATS units immediately before entering the area by phone according to the contacts table in AIP CR, section GEN 3.3, table 3.3.6 ( https://aim.rlp.cz/ais_data/www_main_control/frm_cz_aip.htm ).

Small sport airfields

If in the aerodrome traffic zone (ATZ) of an uncontrolled airfield you plan a drone flight above the grid value, prior coordination is required with the aerodrome flight information service (AFIS or RADIO) or, if these services are not provided, directly with the airfield operator.

For coordination, contact the relevant airfield (see the Contacts tab in the AD-1 VFR manual). Coordination is carried out by mutual agreement between the pilot and airfield personnel; as part of it, additional operating conditions may be set, but only to the extent strictly necessary to ensure operational safety, and to protect the interest of the unmanned aircraft operator in conducting the flight.

Long-term refusals or discouraging and selective charging for coordination that is not applied to other aircraft transiting the same area are, according to the CAA, not considered to be “necessary extent”.

Registered ULL strips (for ultralight aircraft)

If you plan a drone flight within < 1.5 km of the center of a registered ULL strip, do not forget to coordinate in advance with its operator – contacts are listed in the SLZ VFR manual.

Coordination is carried out by mutual agreement between the pilot and the ULL strip operator and may include additional operating conditions, but only to the extent strictly necessary to ensure operational safety, and to protect the interest of the unmanned aircraft operator in conducting the flight.

Long-term refusals or discouraging and selective charging for coordination that is not applied to other aircraft transiting the same area are, according to the CAA, not considered to be “necessary extent”.

Heliports

If you plan a drone flight within < 1 km of a heliport, do not forget to mark the flight plan in the digital map DroneMap, regardless of altitude!

If your planned flight height is to exceed the heliport elevation (within < 200 m of the heliport) or 25 m above the heliport elevation (applies for a distance of 200–1000 m), then the operation must be coordinated in advance with the heliport operator. The exact heliport elevations and contact details for their operators are listed in the HEL-1 VFR manual.

Coordination is carried out by mutual agreement between the pilot and the heliport operator and may result in additional operating conditions, but only to the extent strictly necessary to ensure operational safety.

In the case of a flight near a heliport that is also located within controlled airspace (CTR or MCTR), prior coordination is required not only with the heliport operator but also with the relevant air traffic control tower. The coordination procedure for such flights is the same as for operations requiring coordination in CTR and MCTR airspace, as described in the text above.

Public interest sites (alternate heliports – PIS)

If you plan a drone flight within < 1 km of an alternate heliport (public interest site), do not forget to mark the flight plan in the digital map DroneMap, regardless of altitude!

If your planned flight height is to exceed the heliport elevation (within < 200 m of the heliport) or 25 m above the heliport elevation (applies for a distance of 200–1000 m), then the operation must be coordinated in advance with the public interest site operator via the e-mail address uas@mzd.gov.cz, preferably at least 5 days in advance.

Coordination is carried out by mutual agreement between the pilot and the public interest site operator and may result in additional operating conditions, but only to the extent strictly necessary to ensure operational safety.

If an alternate heliport is also located in controlled airspace (CTR or MCTR), prior coordination is required not only with the site operator, but also with the relevant control tower. The coordination procedure is the same as for flights subject to mandatory coordination in CTR and MCTR, as described above.

Rejoining the server ...

Rejoin failed... attempting to reconnect in seconds.

Failed to rejoin.
Please reload the page.

Session was paused on the server.

An attempt to refresh the session failed.
Please reload the page.