UTM Architecture and Components

NASA UTM Reference Architecture

The NASA UTM reference architecture, developed through years of research and flight testing, provides the foundational framework adopted globally. This architecture is built on several key principles that distinguish it from traditional air traffic management:

• Distributed Services: Rather than centralized control, multiple independent service providers (USS) offer UTM capabilities
• Automation-First: Digital systems handle routine operations; humans intervene only for exceptions
• Scalable Design: Architecture supports growth from hundreds to tens of thousands of simultaneous operations
• Open Standards: Public APIs and data formats enable interoperability and innovation
• Layered Approach: Clear separation between data, services, and operations layers

Three-Layer Architecture Model

Layer 1: UAS Operations

The operational layer includes actual drones, pilots/operators, and ground control stations. Drones broadcast Remote ID, follow flight plans, and maintain connectivity with their USS. Operators interact with USS interfaces to plan flights, obtain authorizations, and monitor operations.

Layer 2: UTM Services (USS Network)

The service layer consists of USS providers offering flight planning, authorization requests, conformance monitoring, alerts, and coordination. Multiple USS compete while sharing critical safety information through standardized interfaces. This layer represents the core innovation of UTM—commercial service provision of safety-critical airspace management functions.

Layer 3: Government Services (FIMS)

The authoritative layer provides airspace constraints, approves/denies operations, interfaces with traditional ATC, and coordinates between USS. FIMS acts as the single source of truth for regulatory constraints while enabling the competitive USS marketplace below.

Flight Information Management System (FIMS)

FIMS serves as the government-operated authoritative component connecting USS networks to traditional aviation infrastructure. While USS providers handle day-to-day operations, FIMS maintains overall safety through several critical functions:

Core FIMS Capabilities

FIMS Data Flows

FIMS continuously publishes authoritative datasets that USS must consume and respect:

• UAS Facility Maps (USFM): Gridded airspace data showing altitude ceilings near airports based on surface type and proximity
• Temporary Flight Restrictions (TFRs): Dynamic no-fly zones for emergencies, VIP movements, sporting events, etc.
• NOTAMs: Notices to Airmen adapted for UAS operations, including hazards and restrictions
• Special Use Airspace Status: Real-time activation status of military operations areas, restricted zones, etc.
• Weather and Environmental Data: Precipitation, winds, visibility affecting safe UAS operations

When a USS submits an operation request, FIMS performs automated compliance checking against these constraints. Simple operations in uncongested airspace receive instant approval; complex operations near airports or in constrained airspace may require additional review or coordination with ATC.

UTM Service Suppliers (USS) - Detailed Architecture

USS Core Services

USS providers implement a comprehensive suite of services supporting the complete operational lifecycle:

1. Strategic Deconfliction

Before flight, USS compares planned operations against accepted operations from all USS (received via USS-USS data exchange). The system identifies potential conflicts—situations where two operations would occupy overlapping 4D volumes (3D space + time). Conflicts must be resolved before authorization, either by adjusting flight times, altitudes, or routes.

2. Flight Planning and Optimization

USS provides tools for operators to plan routes considering airspace constraints, weather, terrain, obstacles, and operator preferences (speed, efficiency, noise). Advanced USS use AI/ML to optimize routes automatically, suggesting alternatives that reduce flight time or avoid congested areas.

3. Authorization Request Processing

USS submits operation requests to FIMS on behalf of operators. The request includes operation details: geographic bounds, altitude range, start/end times, drone capabilities, operator credentials. FIMS responds with approval, denial, or conditional approval requiring modifications.

4. Real-Time Conformance Monitoring

During flight, USS monitors drone positions (from Remote ID or direct telemetry) against authorized flight volumes. Deviations trigger alerts to the operator and potentially to other USS if safety margins are exceeded. USS may implement automated mitigation, such as commanding return-to-home if the drone leaves its authorized area.

5. USS-to-USS Coordination

USS exchange critical safety information including accepted operations, activated operations, and position reports. This federated data sharing enables each USS to maintain airspace awareness without centralized control. The ASTM F3548 standard defines these exchange protocols.

6. Alerts and Notifications

USS informs operators of relevant events: new TFRs affecting their route, weather deterioration, proximity to other operations, equipment anomalies. Multi-channel notifications (app, SMS, email) ensure critical information reaches operators immediately.

USS Technical Requirements

To maintain safety and interoperability, USS must meet stringent technical requirements:

• Availability: 99.9% uptime for critical services; redundant infrastructure
• Latency: Position data updates at least every second; alerts delivered within 2 seconds
• Security: TLS 1.3+ for all communications; OAuth 2.0 authentication; encrypted data at rest
• Data Integrity: Cryptographic signing of critical messages; tamper detection
• Scalability: Support for thousands of simultaneous operations in coverage area
• Standards Compliance: Implementation of ASTM F3548, F3411; API conformance testing

Data Exchange Standards and APIs

ASTM F3548 - USS Network Standards

The ASTM F3548 standard defines how USS exchange data, enabling the federated architecture. Key aspects include:

Operation Intent Exchange: USS share planned operations using standardized JSON schemas. An operation intent includes:

{
  "operation_id": "uuid",
  "uss_base_url": "https://uss.example.com",
  "state": "Accepted | Activated | Ended",
  "volumes": [
    {
      "volume": {
        "outline_polygon": {
          "vertices": [[lat, lng], ...]
        },
        "altitude_lower": {"value": 50, "reference": "W84", "units": "M"},
        "altitude_upper": {"value": 120, "reference": "W84", "units": "M"}
      },
      "time_start": "2025-01-15T14:00:00Z",
      "time_end": "2025-01-15T14:30:00Z"
    }
  ],
  "uas_state": "Nominal | Contingent | NonConforming"
}

Remote ID Data Formats (ASTM F3411)

Remote ID messages broadcast from drones include:

• Basic ID: UAS serial number or session ID; UA type (airplane, helicopter, etc.)
• Location: Latitude, longitude, geodetic altitude, height above takeoff; velocity; timestamp; accuracy estimates
• System: Operator location; altitude; classification; area count; category; emergency status
• Auth: Cryptographic authentication enabling verification of data source

FIMS API Endpoints

USS interact with FIMS through REST APIs:

• POST /operations - Submit new operation request
• PUT /operations/{id} - Update operation details
• DELETE /operations/{id} - Cancel operation
• GET /constraints - Retrieve current airspace constraints
• GET /uss-registry - List active USS providers and coverage areas
• POST /notifications - Receive push notifications of constraint changes

Supporting Systems and Technologies

Geospatial Information Systems

UTM relies heavily on GIS technologies to manage complex 3D airspace. Systems process terrain elevation data, obstacle databases, building heights, vegetation, and temporary structures to create accurate operational volumes. Advanced implementations use LiDAR-derived digital elevation models for centimeter-level accuracy.

Weather Integration

Weather significantly impacts small UAS operations. UTM integrates weather data at unprecedented granularity—hyperlocal forecasts for specific flight corridors, wind shear alerts at low altitudes, icing conditions. Machine learning models predict micro-weather phenomena affecting drone operations.

Identity and Access Management

Robust authentication ensures only authorized operators and certified drones access airspace. Systems verify pilot credentials, drone registration, insurance, and operational permissions. Integration with government databases enables automated compliance checking.