wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Safety WG ======

===== Overview =====

One of the key elements of a full UAV software stack is ensuring that safety is built in at all levels — from the vehicle itself to the airspace, operator, ground and data. The Dronecode stack already has many of these elements in place on the aircraft side (e.g. fail-safes). Individual platform adopters, including drone manufacturers and service providers, have put in place other elements, such as airspace checking and communications link security. The Safety WG is taking a systems approach to safety, bringing completeness and coordination to the various layers and contributors to the stack via the Dronecode Working Group process. This approach is actively being encouraged by the FAA.

Key information:

  * **WG Lead:** Chris Anderson (3DR)
  * **Members:** Harris Teague (Qualcomm), Daniel Rubio (Airmap). Ulisses Furquim (Intel)

===== Current Status =====

The group are currently drafting an FAA Waiver application that describes all the elements of a UAS from a safety perspective, including:

  * Vehicle software design, testing and safety features
  * Vehicle hardware design, testing and safety features
  * Airspace data and compliance
  * Operator data and compliance
  * Datalogging and retention for incident analysis and reporting

wiki

User Tools

Site Tools

Page Tools