AIRSPACE / KNOWLEDGE & DESIGN
UTM | A structure for sharing airspace cooperatively
No single map or single company can do it alone. We break down what operators, service providers, and authorities need to share with one another.
Read this page in order
What UTM covers
The FAA describes UTM (UAS Traffic Management) as an ecosystem for managing low-altitude unmanned aircraft operations cooperatively. It is a concept that complements existing air traffic services and covers planning, airspace authorization, monitoring, conflict management, and more. It does not mean there is a single finished system in use worldwide.
Source: FAA | UAS Traffic ManagementMap out each participant's responsibilities
| Participant | Role | Question the design must answer |
|---|---|---|
| Operator | Purpose, planning, and on-site judgment | Who is responsible for the operation? |
| Operations support service | Organizing plans and constraints, exchanging information | Which information is delivered, and at what quality? |
| Other services | Coordination with neighboring operations | What is shared, and how is it updated? |
| Authorities and similar bodies | The framework of rules, constraints, and authorization | How do legal authority and app permissions differ? |
| Data providers | Supplementary information such as weather and terrain | What are the freshness, accuracy, and terms of use? |
The table above is a design-level breakdown that uses the FAA concept as a starting point. Roles shift with each country's rules and each contract, so define the boundaries of responsibility concretely when you implement.
Keep intent, observation, and authorization separate
The FAA's UTM demonstrations dealt with exchanging information about operational intent and airspace activity. If we think about Airffic World from there, it is natural to hold three things separately: what was planned, what was actually observed, and the conditions the authority approved.
Source: FAA | UTM Pilot Program| Data | Example | Meaning |
|---|---|---|
| Intent | I want to use this volume of space during this time window | Plan or request |
| Observation | This position was observed at this time | Measured or received information |
| Authorization | A record of authorization under specific conditions | Legal or procedural basis |
| Assessment | This version of the inputs has a potential conflict | Result of a calculation or check |
A minimal system proposal
Don't try to manage every aircraft in the country from day one. Start by versioning your own plans, fetching constraint data, and keeping the evidence behind each decision. Connect to external services only where a usable API, a contract, and an operating arrangement are all in place.
| Component | Responsibility |
|---|---|
| Planning service | Version control of operational intent |
| Constraint service | Information tagged with its source and validity period |
| Assessment service | Check results with reasons attached |
| Audit log | A record of who confirmed what |
| External connectors | Authentication, retries, and failure contracts for each authority, peer service, weather provider, and so on |
This structure is a proposal. This site is not operating as a UTM or authorization service.
DEFINITION OF DONE
Before you ship, check these.
- Plan, observation, and authorization data are never mixed up.
- The timestamp and source of external information can be checked.
- The boundaries of responsibility between services, and who to contact on failure, are settled.
Design checkpoints for spec reviews and acceptance testing.
Check the sources
Explanations of rules and definitions draw on the references below. The screens, data models, and definition of done are our own design proposals.
- FAA | UAS Traffic ManagementThe UTM concept and cooperative traffic management
- FAA | UTM Pilot ProgramDemonstrations including the exchange of operational intent and airspace information
Sources checked on September 30, 2026. For your specific case, please confirm with the latest official information.