Public utility easements (SUPs) are administrative limitations on the right to property, they are established for the benefit of public persons, concessionaires of public works or public works, private persons engaged in an activity in the public interest. The collection and conservation of public utility easements is a sovereign task of the State, which must bring them to the attention of local and regional authorities so that they may annex them to their urban planning documents. The public utility easements concerned are those defined by Articles L. 126-1 and R. 126-1 of the Urban Planning Code and their annexes.
T5 SUPs, known as Aeronautical Clearance Servitudes, are created to ensure the safe operation of aircraft, excluding radio easements. They are defined as:
—by a plan of aeronautical alternate easements (PSA) drawn up for each aerodrome referred to in Article L.6350-1 (1) and (2) of the Transport Code (formerly R. 241-2 of the Civil Aviation Code),
—or by provisional safeguard measures which may be implemented in the event of an emergency, before being included in an approved SAAP.
Legislative texts:
Latest laws, orders or decrees issued by the Council of State:
Order No 2010-1307 of 28 October 2010 concerning the legislative part of the Transport Code, repealing Title IV of Book II of the Civil Aviation Code relating to aeronautical easements in order to incorporate it into “Part 6: Civil Aviation” of the Transport Code, under Title V, “Requirements in the vicinity of aerodromes”
link to articles L.281-1 et seq. of the Civil Aviation Code:
http://www.legifrance.gouv.fr/WAspad/UnArticleDeCode?code=CAVIACIL.rcv&art=L281-1
link to SUP scanning guide: http://www.geomatique-aln.fr/spip.php?article296
The reference date of the data is the date of publication of this metadata
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.