OpenARIA : Enhancing Aviation Safety Through Open-Source Innovation

This repository contains an open-source edition of the Aviation Risk Identification and Assessment (ARIA) software program developed by MITRE on behalf of the Federal Aviation Administration’s (FAA) Safety and Technical Training (AJI) Service Unit.

OpenARIA’s Goal

Our goal is to build a community focused on improving aviation safety & efficiency by extracting value from aircraft location data.

How OpenARIA Can Achieve This Goal

1. Provide a publicly available solution for detecting aviation risks within aircraft location data.
   • This tangible working solution can be critiqued by the community and improved as necessary.
2. Provide a publicly available solution for detecting and then aggregating aviation risks for bulk analysis.
   • Someone operating OpenARIA for a day will have one day’s worth of output
   • Someone operating OpenARIA for a year will have a year’s worth of output.
   • We must facilitate capturing and utilizing large amounts of output data.
3. Provide a publicly available solution for archiving and replaying aircraft location data
   • E.g., when OpenARIA detects an event, we will want to be able to replay the event to understand what happened.
4. Provide solutions that work with near-real time data streams as well as archival data.

Getting Started

• To begin detecting aviation events see here
• To begin archiving and replaying aircraft location data see here
• To begin detecting and then aggregating aviation data see here

Documentation

• High-level source code summary
• About ARIA’s Airborne Event Data
  • An example of this JSON output data is here
  • A PDF describing the output data is here
• Architectural Decision Records (ADRs)
  • Why YAML configs are preferable to Properties
  • Critique of Point and Track interfaces
  • How to compute an event’s uniqueId

Using And Contributing

First of all, Welcome to the community!

Contributing As A User

• Please submit feedback.
• Do you have a technical question? If so, please ask. We are here to help. Your question could lead to improvements. User questions lead to improved documentation, understanding defects, and eventually code improvements the reach everyone in the community.
• Do you have a feature request? If so, please ask. We’ll see what we can do given the development time we have available.

Contributing As A Developer

• We will use GitHub’s Issue tracking features when the project launches.
• Anyone interested in making technical contributions is welcomed to communicate with the dev team on GitHub. Feel free to submit issues, fix issues, and submit PRs.
• We may write a “contributing guidelines” document in the future should the need arise. But for now, our focus will be on making high-quality, high-value improvements to the code (not policy documents).

Near-Term Project RoadMap