Aerodromes
Background
The term aerodrome encompasses airports, heliports, seaplane bases, and facilities designated for use by another specific type of aircraft such as sailplanes, ultralights, or hot air balloons. Small privately-owned aerodromes vastly outnumber public facilities:
Fewer than 5% of aerodromes are associated with controlled (Class B, C, D, or E2) airspace, meaning prior authorization is not needed to operate near many of these facilities. But UAS operators are required to be aware of their presence and be prepared to avoid conflict and yield right of way to any manned aircraft.
The Aerodromes endpoints
Request bodies for /aerodromes endpoints are “basic”, meaning the only information you need to provide are those parameters that define your area of interest (point/distance, route, or poly).
In all cases, the response body will be a json object containing a single element named found. The contents of found will be a GeoJSON FeatureCollection with one Feature per aerodrome found in your requested area of interest. The feature properties given for aerodromes are:
- ident: FAA site identifier
- name: facility name
- facility_type:
- PRIVATE AIRPORT
- PRIVATE BALLOONPORT
- PRIVATE GLIDERPORT
- PRIVATE HELIPORT
- PRIVATE SEAPLANE BASE
- PRIVATE ULTRALIGHT
- PUBLIC AIRPORT
- PUBLIC BALLOONPORT
- PUBLIC GLIDERPORT
- PUBLIC HELIPORT
- PUBLIC SEAPLANE BASE
- PUBLIC ULTRALIGHT
- facility_status:
- OPERATIONAL
- CLOSED INDEFINITELY
- CLOSED PERMANENTLY
The geometry type of Features returned from /aerodromes endpoints will always be a single Point, usually the centroid of the facility’s property but it could be anywhere within the bounds of the facility. Keep this in mind when interpreting your results and also that:
- the greatest potential for conflict is generally when manned aircraft are arriving (descending to) or departing (climbing out from) the aerodrome, i.e. when they will be at the same altitudes as traversing UAVs
- climb and descent profiles for manned aircraft will differ by type (airplane, helicopter, seaplane, glider, or balloon)
- distance and polygon queries return only the the aerodromes whose point coordinates are contained within – or intersect the boundaries of – your requested area
- route queries return all aerodromes within 1 nautical mile of your route
Below are examples of each request type.
Distance Request
- Request body:
{ "longitude": -70.5, "latitude": 43.9, "distance": 15000 } - Endpoint: https://dflight-api.ljaero.com/us/v1/aerodromes/distance-query
Route Request
- Request body:
{ "route": { "type": "LineString", "coordinates": [ [-89.613, 43.765], [-89.658, 43.759], [-89.7, 43.751], [-89.717, 43.747], [-89.796, 43.745], [-89.8, 43.737], [-89.834, 43.734] ] } } - Endpoint: https://dflight-api.ljaero.com/us/v1/aerodromes/route-query
Polygon Request
- Request body:
{ "poly": { "type": "Polygon", "coordinates": [[ [-81.425,28.333], [-81.450,28.199], [-81.133,28.176], [-81.125,28.349], [-81.425,28.333] ]] } } - Endpoint: https://dflight-api.ljaero.com/us/v1/aerodromes/polygon-query
