KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#typescript #ai-agents #developer-tools #cli #codex #claude-code #react #dsh-plugin #mcp #open-source #dsh #deepseek-harness

getstarted

★ 39 Open GitHub ↗

Operationalization of UTM services to support complex UAS operations, with an initial focus on furthering shared airspace.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# US Shared Airspace

UAS Traffic Management (UTM) implementation in the US is the operationalization of UTM services to support complex UAS operations, with an initial focus on furthering shared airspace.

**Onboarding guidance:** New service providers onboarding SCD capabilities should follow the [SCD onboarding steps](./onboarding.md). Existing service providers adding Network Remote ID should follow the separate [NRID onboarding guidance steps](./NRID_onboarding.md).

## Recent Updates
+ June 8, 2026: [Network Remote ID onboarding guidance](./NRID_onboarding.md) introduced.
+ May 21, 2026: [UTM Service Provider Data Sharing and Governance Agreement](./docs/USP_Agreement_05212026.pdf) Updated
+ May 19, 2026: [Network Remote ID SDD](./docs/Network_Remote_Identification_Service_Description_Document_V1.0.pdf) v1.0 introduced.
+ April 22, 2026: [Service Description Document](./docs/UA-UA_Strategic_Coordination_Service_Description_Document_V2.0.3.pdf) updated to v2.0.3.
+ April 8, 2026: [Prioritization policy](./docs/prioritization-policy-04082026.md) updated.
+ April 8, 2026: SDD v2.0.1 implementation timeline updated.
+ January 21, 2026: [Service Description Document](./docs/UA-UA_Strategic_Coordination_SDD_V2.0.1.pdf) updated to v2.0.1.

## SDD Version and Status
<table><tr><th scope="col"> </th><th scope="col">Version</th><th scope="col">Test Baseline</th><th scope="col">Montly Reporting Template</th><th scope="col">Rollout Status</th></tr>
    <th scope="row">SCD</th><td><a href="./docs/UA-UA_Strategic_Coordination_Service_Description_Document_V2.0.3.pdf">v2.0.3</a></td><td>TB-722d968</td><td><a href="./docs/Service_Provider_and_Operator_Monthly_Reporting_Templates_V2.0.xlsx">v2.0</a></td><td>Implemented as of 4/2026 and currently active</td></tr>
    <th scope="row">NRID</th><td><a href="./docs/Network_Remote_Identification_Service_Description_Document_V1.0.pdf">v1.0</a></td><td>TB-3765023</td><td><a href="./docs/Network_Remote_Identification_Service_Provider_Monthly_Reporting_Template_V1.0.xlsx">v1.0</a></td><td>Implemented as of 5/2026 and currently active</td></tr>
</table>
<i>Note: Some links in this table may only be accessible to participants and observers.</i>

## About the US UTM Implementation

As of January 2026, the cohort includes 17 service providers and operators using the USS Network to support UAS operations in several parts of the United States. In October 2025, [many members submitted joint comments](https://www.regulations.gov/comment/FAA-2025-1908-2544) in support of the cohort's activities in response to the Federal Aviation Administration's Notice of Proposed Rulemaking (NPRM) for Normalizing UAS Beyond Visual Line of Sight (BVLOS) Operations. In June 2025, Unmanned Airspace [covered the cohort's progress to date](https://www.unmannedairspace.info/uncategorized/one-year-on-assessing-challenges-and-achievements-of-the-us-utm-implementation-programme/). In March 2025, the Mid-Atlantic Aviation Partnership (MAAP) at Virginia Tech completed their [Initial Operationalization Report](./docs/Shared_Airspace_Report_v1_FINAL.pdf), which the Operations Committee approved and makes publicly available.

Shared airspace is the digital coordination of intended UA flight paths with overlapping operators in support of FAA Order 8040.6A and complex operations. This implementation of shared airspace leverages the strategic conflict detection and aggregated conformance monitoring services (collectively identified as strategic coordination) defined in [ASTM F3548-21 Standard Specification for UAS Traffic Management (UTM) UAS Service Supplier (USS) Interoperability](https://www.astm.org/f3548-21.html). These services are expected to be accepted by the FAA per the [Near Term Approvals Process (NTAP)](https://www.faa.gov/uas/advanced_operations/traffic_management) and incorporate participation and feedback from the FAA and NASA. Participants include Service Providers and Operators with the need to reduce UA to UA risk and who have signed the agreement available on this page.

Shared airspace is built around these guiding principles:

1. Safety first!
2. We will establish and abide by collaborative operating practices to enable the safe and efficient use of shared airspace by UAS operators.
3. We will support and enable a US-wide approach for UTM.
4. We will implement services based on mutually agreed requirements for performance, security, privacy, and quality based on industry consensus standards.
5. We will establish processes to evolve and adapt services based on operational learnings and needs.
6. We will proactively monitor and manage service and operator conformance to mutually agreed requirements.
7. We will eliminate barriers to entry by individuals and organizations by establishing performance-based onboarding criteria.
8. We will establish transparent and fair governance processes that value consensus building and provide equal voting rights to members.
9. We will foster transparency with and invite feedback from regulators and other stakeholders.

With performance-based criteria, UTM service providers and their operators can participate via key documents, which include onboarding instructions, available below:

* [UTM Service Provider Data Sharing and Governance Agreement](./docs/USP_Agreement_05212026.pdf)
* (SCD SDD) [Service Description Document for Strategic Coordination, v2.0.3](./docs/UA-UA_Strategic_Coordination_Service_Description_Document_V2.0.3.pdf)
* (SCD RTM) [Requirements Traceability Matrix for Strategic Coordination, v2.0](./docs/SCD-RTM-V2.0.xlsx)
* (NRID SDD) [Service Description Document for Network Remote Identification, v1.0](./docs/Network_Remote_Identification_Service_Description_Document_V1.0.pdf)
* (NRID RTM) [Requirements Traceability Matrix for Network Remote Identification, v1.0](./docs/Network_Remote_Identification_Compliance_Matrix_V1.0.xlsx)

## Frequently Asked Questions and Additional Resources

+ [Click here](faqs.md) for answers to frequently asked questions about the US UTM Implementation.
+ [Consult this page for the specific onboarding steps that are required](onboarding.md), including how to sign the governance agreement, and required timelines for completing the steps.
+ [Click here for more information on DSS Pooling](dss-pooling.md), which is applicable to service providers who are seeking to include their own DSS instance (or a subcontracted instance) in the Shared Airspace DSS Pool.

## How to Get Started

Participation in the shared airspace ecosystem enables collaboration, communication, and governance of shared airspace, aiming to integrate strategic coordination services to enable dense, overlapping BVLOS operations. This section provides an overview of the steps to join the US UTM Implementation.

As a participant, you will be able to leverage shared operational and governance resources to develop, verify, and advance your approach to sharing the airspace. This is an opportunity to learn from collaborative efforts and participate in democratized foundations of a shared airspace.

As a service provider, you can service operators by conveying digital intent and deconflicting flight paths. With revised FAA requirements for risk mitigation, and meeting industry-consensus standards, shared airspace offers a digital, transparent, and scalable process.

The ecosystem is open to service providers and their operators. Providers of UTM services, including private and public entities and organizations, are eligible and encouraged to join this agreement. Here are the steps and gate milestones to getting started:

<table>
    <tr>
        <th rowspan="2">Gate</th>
        <th colspan="3">Gate Exit Criteria</th>
    </tr>
    <tr>
        <th>Service Provider</th>
        <th>Operator</th>
        <th>Joint</th>
    </tr>
    <tr>
        <td>GATE 1: Qualification Testing</td>
        <td>
            <ul>
                <li>Implement the service requirements in accordance with the applicable service description document</li>
                <li>Pass automated testing (own system only)</li>
            </ul>
        </td>
        <td>N/A</td>
        <td>N/A</td>
    </tr>
    <tr>
        <td>GATE 2: Simulation</td>
        <td>
            <ul>
                <li>Pass automated testing (ecosystem)</li>
            </ul>
        </td>
        <td>N/A</td>
        <td>
            <ul>
                <li>Integrate service provider and operator systems</li>
            </ul>
        </td>
    </tr>
    <tr>
        <td>GATE 3: Production Flights</td>
        <td>
            <ul>
                <li>Pass automated testing (ecosystem) as a part of the software release process</li>
            </ul>
        </td>
        <td>
            <ul>
                <li>Validate operational practicality through overlapping airspace simulation</li>
            </ul>
        </td>
        <td>N/A</td>
    </tr>
</table>

_Source: Annex B - Onboarding Gates, UTM Service Provider Data Sharing and Governance Agreeement_

[BECOME A PARTICIPANT](https://forms.gle/3SgLJ6jnj9PVeDSF6)

## Current Activities

Participants in the current collaboration stemming from the active drone delivery market in North Texas are onboarding to or actively participating in simulations representing true, day-in-the-life operations. These simulations have progressed to live flights over the course of 2024. Companies have reached consensus on governance and data sharing, and have signed and implemented agreements that are publicly available on this page. This is known as the US UTM Shared Airspace Implementation.

![initial asset](https://raw.githubusercontent.com/utmimplementationus/getstarted/main/assets/SimulationExample.png)

## Background

Following the momentum around scaled UAS services, particularly around drone delivery, in the greater North Texas area in late 2023 and early 2024, several operators noted the inherent need to communicate amongst each other. Prior FAA and NASA projects like the [UTM Field Test](https://www.faa.gov/uas/research_development/traffic_management/field_test), [UTM Pilot Program](https://www.faa.gov/uas/research_development/traffic_management/utm_pilot_program), UTM Technical Capability Levels, and other efforts had already provided frameworks for deploying strategic coordination services in an operational environment.

Understanding the need to share airspace amongst scaled operations and leverage applicable standards, an initial seven operators engaged in a project to operationalize strategic conflict detection in the Dallas-Fort Worth area, including DroneUp, Flytrex, Manna, Prime Air, UPS Flight Forward, Wing, and Zipline, with ANRA Technologies as a service provider. Subsequently, AAMTEX, Avision and Cal Analytics have joined the activies as service providers. Initial activities are supported by contributions fromthe Virginia Tech Mid-Atlantic Aviation Partnership (MAAP), Global UTM Association (GUTMA) and the InterUSS Platform. The effort is applicable to UTM across the US.

## Open Source Approach

This Github repository of publicly available resources promotes the development of an open source solution, while facilitating transparency and enabling ongoing updates from new data and learnings.

Additionally as part of this implementation, the participants have evaluated and integrated open source tools and documents. Those include resources from the [Global UTM Association](https://gutma.org/) and the [InterUSS Platform](https://interussplatform.org/) (Linux Foundation).

getstarted

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README