Category T5 easements relate to aeronautical clearance easements, established pursuant to articles L. 6351-1 1° and L. 6351-2 to L. 6351-5 of the Transportation Code (formerly R. 241-1 to R. 242-3 of the Civil Aviation Code) These are easements, known as aeronautical clearing services, created to ensure the safe movement 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 interim safeguard measures which may be implemented in the event of an emergency, before being included in an approved ASP. These aeronautical clearance easements shall include: — a prohibition on the creation or the obligation to modify or even remove obstacles which may constitute a danger to air traffic or which are harmful to the operation of safety devices (luminous, radio-electric or meteorological) established in the interest of air navigation, — the prohibition on carrying out major repairs or improvements on vessels and other works affected by aeronautical easements exempted from the building permit without the authorisation of the administrative authority. This resource describes the surface plates of grade T5 easements, namely clearance surfaces: — area bounded by the support perimeter; — landing hole; — take-off hole; — lateral surfaces; — inner horizontal surface; — conical surface; — additional surfaces associated with precision landings (obstructed areas)
Source: —NR—
Vintage: —NR—
Dissemination: Restricted
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.