This feature allows for efficient monitoring of flight operations by comparing flight log data to a pre-defined policy.
The creation of a flight conformance policy allows remote pilots, mission planners and chief remote pilots a convenient way to determine adherence to planned mission parameters and organisational policy.
This feature allows for the tracking of 3 parameters:
- Maximum Visual Distance (m)
- Maximum Height (ft AGL)
- Flight Area
On the completion of a mission, these parameters are checked using the RPA's flight log as the data source.
In the event that any of the enabled parameters have been exceeded during the mission, notifications will be generated based on the policy's settings. The information can then be used internally for training or enforcement purposes.
Notifications and associated flight data only exist within their specific organisation and are solely intended for internal monitoring and training. Only the recipients specified in the conformance policy are able to view these notifications.
The results of this comparison are saved as part of the mission record, where you can find them under the conformance tab.
Creating a Conformance Policy
There are two types of conformance policy: Default and Authority-based. Authority based policies will be in effect on any mission planned under that specific authority (for example, an operator's certificate).
If no authority-based policy is created, or isn't enabled - the default policy serves as a 'catch-all' and will apply to all missions.
To create a conformance policy, visit the profile menu > organisation admin. You should see a tab called 'flight conformance'. If you don't see this option, please contact us to have it enabled.
In the flight conformance tab, click the + button to add a rule.
Fill out the new rule details as follows:
- Rule Type: Select between visual distance, flight height or flight area restrictions (you can add several rules or even all three).
- Description: This text will show up in any triggered notifications. This is the message you'd like the notification recipient to recieve.
- Default Value: This number acts as a 'fall back' value. If the mission parameters or RPA information don't contain the relevant value, the default will be used (optional)
- Maximum Value: This maximum supercedes any mission/RPA specific values and acts as a maximum allowable value for the policy. Eg even if a mission approval contains a max height above this value, the rule will be triggered if it is broken. (optional)
Once you've completed these fields, click Add. You can then either save the policy of add additional rules to the policy by following the same steps.
When you have one or more existing policies, you will see the following options:
- Enabled: This switch allows you to toggle the rule on/off. If you no longer wish to use that rule, simply disable it.
- Settings: Displays the values entered for that rule.
- Message: Displays the message used for notifications.
- Notify toggles: These switches allow you to determine who should recieve notifications triggered by the rule. This can be any of Remote Pilot (RP), Remote Pilot in Command (RPIC) and Approver (usually the Chief Remote Pilot).
Note: The notification component is coming soon. We'll update this article when that system comes online.
Finally, you can edit the parameters of the rule using the pencil icon.
Reviewing Flight Conformance
Once your mission has been completed and the relevant flight logs have been assigned, the flight conformance will automatically be checked by the system. You can find the conformance details in the View mission Record screen, as shown below.
The conformance check relies on your RPA flight logs. If you haven't uploaded flight logs and assigned them to the relevant flights, the conformance tab will be empty.
Clicking on the conformance tab, you will see a list of all flights for which there are associated logs.
Flights that adhered to your conformance policy will display a green tick in the status column.
Flights with conformance issues will display the description of the rule (along with the maximum allowable value and the actual value where appropriate).
During the reconciliation stage of the mission, the remote pilot should review any conformance issues and can add their own notes (shown above under 'acknowledgement'). This can lead to continuous self improvement - for example flying outside the planned flight area might be due to flying incorrectly, or perhaps the flight area was drawn inaccurately in the first place. Using the conformance system, the remote pilot or mission planner is prompted to identify such errors so that they can be corrected next time.
Once the remote pilot has acknowledged the breach, the CRP has the option to 'finalise' it prior to finalising the mission itself.
Certain aspects of this new feature are still under development. As improvements are made to mission conformance, we will update this article with the latest information.
If you have any queries, please contact firstname.lastname@example.org