AAS 1.10 OPERATIONAL USE OF UNMANNED AIRCRAFT (UA)

  • Home AAS AAS 1.10 OPERATIONAL USE OF UN....

AAS 1.10 OPERATIONAL USE OF UNMANNED AIRCRAFT (UA)

ATC should not have to apply different rules or work with different criteria in order to handle UA. From the air traffic controller’s perspective, the provision of ATS to an UA must be transparent. This includes all stages of the flight from pre-notification to landing. There should be no difference in RTF, landline communications or transponder data procedures nor should the controller have to apply different rules or different criteria.


IFATCA Policy is:

IFATCA is opposed to the operations of any autonomous aircraft in non-segregated airspace.

All Remotely Piloted Aircraft Systems (RPAS) operations in non- segregated airspace must be in full compliance with ICAO requirements. Whether the pilot is onboard or not shall be irrelevant for the purposes of air traffic control, therefore the same division of responsibilities and liabilities as manned aircraft shall apply.

ATCOs shall not be held liable for incidents or accidents resulting from the operations of RPAS that are not in compliance with ICAO requirements, in non-segregated airspace.

Standardized procedures, training and guidance material shall be provided before integrating RPAS into the Civil Aviation System.

IFATCA encourages education and awareness campaigns on the use of RPAS for the general public.

IFATCA urges the development and implementation of technology to prevent airspace infringements by Unmanned Aircraft.

Contingency procedures and controller training shall be provided for the management of infringements by Unmanned Aircraft.


See: WP 90 – Melbourne 2005, WP 91 – Dubrovnik 2009, WP 160 – Sofia 2015 and Resolution B3, B4, and B5 – WP 88 – Toronto 2017

 

Last Update: September 23, 2020  

November 3, 2019   442   Jean-Francois Lepage    AAS    

Comments are closed.


  • Search Knowledgebase