Aviation Data Exchange Standards - Consolidated Field Reference

Version: 2.0 Date: 2026-03-29 Purpose: Cross-reference of equivalent field names across aviation data exchange standards

FIXM Migration Complete (2026-03-29): VATSWIM now uses FIXM 4.3.0-aligned field naming in its REST API. Legacy OOOI column names (out_utc, off_utc, on_utc, in_utc) remain in the database for backward compatibility but the API returns FIXM-aligned names (actual_off_block_time, actual_time_of_departure, actual_landing_time, actual_in_block_time). See VATSWIM_FIXM_Field_Mapping.md for the complete DB-to-API mapping.

API Response Structure

The VATSWIM REST API returns flight data as nested JSON objects aligned with FIXM 4.3.0. The VATSWIM column in tables below shows the API response field path (e.g., identity.aircraft_identification). Database column names are noted in parentheses where they differ from the API field.

GET /api/swim/v1/flights?format=fixm
Authorization: Bearer {api_key}  or  X-API-Key: {api_key}

Response: 98 fields across 8 object groups
  gufi, flight_uid, flight_key          (root)
  identity.*                            (9 fields)
  flight_plan.*                         (18 fields)
  position.*                            (10 fields)
  progress.*                            (8 fields)
  times.*                               (17 fields)
  tmi.*                                 (13 fields)
  metering.*                            (15 fields)
  + 5 metadata fields at root

Data pipeline: VATSIM_ADL (6 normalized tables, 274 columns) -> 2-min sync -> SWIM_API.swim_flights (213 columns) -> SQL select ~65 cols -> formatFlightRecordFIXM() -> 98 API fields.

Supported formats: fixm (default), xml, geojson, csv, kml, ndjson

1. Flight Identification

GUFI format: VAT-YYYYMMDD-{callsign}-{dept}-{dest} (computed column in swim_flights)

2. Aircraft Information

Wake Turbulence Categories (wake_category column)

FAA Weight Classes (weight_class column)

Additional Aircraft Fields (DB only, not in API response)

3. Departure Information

4. Arrival Information

5. Route & Trajectory

Route Progress (VATSWIM extension)

6. Time Fields

6.1 Departure Times

6.2 Arrival Times

6.3 ETA Computation (VATSWIM extension)

6.4 SimTraffic Departure Phase Times (VATSWIM extension)

6.5 OOOI Times (Out-Off-On-In)

6.6 Time Prefixes (TFMS Convention)

6.7 Additional Time Fields (DB only, 97 columns in adl_flight_times)

The ADL stores extensive time data not exposed in the standard API response:

7. Flight Status & Phase

7.1 Flight Status (API progress.flight_status)

7.2 Active Status

8. Position & Track Data

* Mapping note: position.track is sourced from DB column heading_deg (not track_deg). The ADL stores both heading_deg (magnetic heading) and track_deg (true track angle) in adl_flight_position, but the API maps heading_deg to the track response field. This is a known semantic mismatch inherited from the VATSIM data feed which provides heading, not track.

Airspace Position (VATSWIM extension)

Additional Position Fields (DB only, 24 columns in adl_flight_position)

9. TMI (Traffic Management Initiative) Data

9.1 TMI Types

9.2 TMI Fields

9.3 Delay Status Codes (TFMS)

9.4 Additional TMI Fields (DB only, 43 columns in adl_flight_tmi)

10. Metering & Sequencing (TBFM/SimTraffic)

This section covers arrival metering data, typically sourced from SimTraffic or TBFM-like systems.

11. A-CDM Milestones (Airport Collaborative Decision Making)

CDM Source Tracking (DB only)

12. ECFMP Flow Control (EUROCONTROL-style, VATSWIM extension)

These fields are populated when flights interact with ECFMP (European Centre for Flow Management on VATSIM). Not currently exposed in the REST API.

13. NAT Track Resolution (VATSWIM extension)

These fields track North Atlantic Organized Track System (OTS) assignments. Not currently exposed in the REST API.

14. SimBrief OFP Integration (DB only)

15. Airspace & Facility References

Additional Airspace (DB only)

16. Weather Integration

VATSWIM Weather Fields (DB only)

IWXXM/METAR Standards Reference

17. Response Envelope Standards

VATSWIM JSON Response (REST API)

{
  "success": true,
  "data": [
    {
      "gufi": "VAT-20260329-UAL123-KJFK-KLAX",
      "flight_uid": "12345",
      "flight_key": "1234567|UAL123|KJFK|KLAX|1430",
      "identity": { ... },
      "flight_plan": { ... },
      "position": { ... },
      "progress": { ... },
      "times": { ... },
      "tmi": { ... },
      "metering": { ... },
      "data_source": "vatcscc",
      "first_tracked_time": "2026-03-29T14:25:00+00:00",
      "position_time": "2026-03-29T16:45:00+00:00",
      "logon_time": "2026-03-29T14:20:00+00:00",
      "last_sync_time": "2026-03-29T16:45:15+00:00"
    }
  ],
  "pagination": {
    "total": 2735,
    "page": 1,
    "per_page": 500,
    "total_pages": 6,
    "has_more": true
  },
  "timestamp": "2026-03-29T19:10:25+00:00"
}

FIXM XML Envelope

<fx:Flight xmlns:fx="http://www.fixm.aero/flight/4.3"
           xmlns:fb="http://www.fixm.aero/base/4.3"
           xmlns:nas="http://www.faa.aero/nas/4.3">
  <fx:gufi>VAT-20260329-UAL123-KJFK-KLAX</fx:gufi>
  ...
</fx:Flight>

AIDX XML Envelope

<aidx:IATA_AIDX_FlightLegNotifRQ
    xmlns:aidx="http://www.iata.org/IATA/2007/00"
    Version="22.1">
  <aidx:FlightLeg>
    ...
  </aidx:FlightLeg>
</aidx:IATA_AIDX_FlightLegNotifRQ>

18. Quick Reference: VATSWIM API Fields

Complete mapping of all 98 API response fields to their standards equivalents.

Root Fields

Identity Block

Flight Plan Block

Position Block

Progress Block

Times Block

TMI Block

Metering Block

19. Database Schema Summary

swim_flights Table (SWIM_API database)

Total columns: 213 (denormalized from 6 ADL source tables) Update frequency: Every 2 minutes via swim_sync_daemon.php Change detection: SHA1 row hash on 21 volatile columns skips no-op updates

ADL Source Tables (VATSIM_ADL database)

Additional swim_flights Columns (DB only, not in API response)

These columns exist in swim_flights but are not exposed in the REST API formatFlightRecordFIXM() response.

Flight Plan / Route:

Position / Airspace:

Times:

TMI:

SimTraffic / Metering:

Internal / Sync (not meaningful for consumers):

Related Tables (not in swim_flights)

20. Namespace Reference

Appendix A: API Query Filters

Document version 2.0 -- updated 2026-03-29 from verified production database schemas (213 swim_flights columns, 274 ADL columns) and live API response (98 fields).