From signing the agreement to flying live, here's the whole journey, in plain language. The consortium designed it to be performance-based: prove your system works, and you're in.
To providers & operators, public or private
To complete testing once you sign
One-time extension available
Test → simulate → fly
There are two starting steps, then three "gates" you pass in sequence. Each gate is about showing your system works, first on its own, then with others, then in production.
Email the Operations Committee with the name and email of the person who'll sign. They send you the Form of Joinder (Annex E) via DocuSign. Then share your committee points of contact and GitHub handles.
Unlocks observer status in both committees while you onboard.
Once you sign, your 120-day clock starts. You get a test configuration so you can run tests independently, without affecting live participants. You'll gather artifacts like proof of insurance, security/privacy/quality attestations (or ISO/IEC certs), and an operator relationship (SLA signature page).
Implement the service requirements from the applicable Service Description Document, then pass automated testing on your own system.
Pass automated testing across the ecosystem, and integrate your systems with your operator so you can exchange data the way the standard requires.
Note: "Integration" means the technical ability to exchange data. It does not require FAA approvals, which run on their own timeline.
Operators run coordinated, simultaneous simulations with the other members they expect to overlap with in real life, establishing "operational practicality." Service providers pass Production Fitness testing as part of their release process.
You receive a certificate from the Co-Chairs and can request access to the production environment. Voting rights are granted after Gate 3. Keep meeting the ongoing requirements to stay active. Welcome to the shared airspace.
Already working with a service provider that's live on the network?
Parter with a service provider that has already completed onboarding and is live on the network. They provision your UTM services and connect your operations to the shared airspace.
Sign a Service Level Agreement with your provider. The SLA flows the consortium's governance requirements down to you as the operator, in addition to provider specific terms & conditions. You, or your provider on your behalf, submit the signed signature page as evidence.
With your service provider, run coordinated, simultaneous shared-airspace simulation with the overlapping operators you reasonably expect to encounter, to establish operational practicality.
If you'll fly time-critical, life-safety missions, submit a request to use high priority, along with the required eligibility evidence.
You're ready to fly alongside other members in shared airspace, with your provider handling the UTM service connection.
Your system, on its own, meets the requirements and passes automated testing.
Your system passes ecosystem testing and integrates with your operator.
Operational practicality is proven through simulation; production testing passes; onboarding is confirmed.
After signing, you have a defined onboarding window to complete all gates and submit your artifacts. Miss it, and you're removed from the implementation and lose observer access. But you can request a one-time 30-day extension before the window closes, no conditions attached.
Removed applicants may reapply after a 90-day waiting period.
The consortium runs two services today: Strategic Coordination (SCD) and Network Remote ID (NRID). If you've onboarded for one, the second has a streamlined path that builds on your existing Gate 0 status.
See service documentsExpress your interest and an Operations Committee co-chair will guide you through signing and your first gate.