Flight Features

Flight features are a set of predicates which contain additional details and properties regarding a user's flight. More simply, a flight feature is a question that must be answered by the pilot (via your application) to check compliance with a corresponding airspace rule that applies to their flight. Answers to flight features are required to generate an accurate Flight Briefing.

Flight features belonging to applicable rules can be accessed in one of two ways. First, once your application requests the available rulesets for the pilot's desired flight area, you will see in the response a list of rules contained in each ruleset and a list of flight_features for each of those rules, if present. Alternatively, the response includes one comprehensive list of flight features as a child of the ruleset itself. This object simply lists all flight features belonging to any rules within the given ruleset. It provides a quick list of all questions that must be asked of the pilot without having to iterate through the entire list of rules.

For example, a ruleset query might return the following flight features as part of the response for the "FAA Part 107 Certified" ruleset:

"flight_features": [
        {
          "flight_feature": "uav_weight",
          "description": "What is the weight of the drone?",
          "input_type": "float",
          "measurement_type": "weight",
          "measurement_unit": "kilograms"
        },
        {
          "flight_feature": "uav_registered",
          "description": "Is the drone registered?",
          "input_type": "bool",
          "measurement_type": null,
          "measurement_unit": null
        },
        {
          "flight_feature": "uav_nav_lights",
          "description": "Does the drone have anti-collision lighting?",
          "input_type": "bool",
          "measurement_type": null,
          "measurement_unit": null
        }
]

As seen in the response above, the list of flight features contains the name of the flight feature along with the question that the pilot must answer. Each flight_feature key will be paired with the pilot's response value from your application to form part of the request for creating or updating a Flight Plan and generating the subsequent Flight Briefing. The description, input_type, measurement_type, and measurement_unit parameters are provided to assist your application in prompting the pilot for these inputs.

For example, a user might have the following flight_features object as part of a request:

"flight_features": {
          "uav_weight" : 1.0,
          "uav_registered": true,
          "uav_nav_lights": true
}

Before moving on to flight creation, let's explore another component of Contextual Airspace, the Airspace Advisory.

Updated 3 years ago


What's Next

Apply rulesets to discover the airspace

Airspace Advisory

Flight Features


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.