US Department of Transportation
DOT
Overview
The US Department of Transportation (DOT) provides the T-100 Domestic Segment Data, which contains detailed information on non-stop domestic flight segments.
Example use cases:
Evaluate airline market share and performance
Analyze domestic air traffic patterns
Conduct economic assessment of the aviation sector
Understand trends in usage of particular aircrafts
Key Attributes
Geographic Coverage | United States (domestic segments) |
Entity Level | Aircraft Carrier, Aircraft, Airport |
Time Granularity | Monthly |
Release Frequency | On a monthly basis, US DOT provides a month of data with a 2.5 month lag. For example, April 2024 data was added on July 15, 2024. It also updates previous data. For example, on July 15, 2024, data from February 2023 to March 2024 were updated. For real-time details, see here under T-100 Domestic Segment (U.S. Carriers). |
History | 1990- |
As with all Public Domain datasets, Cybersyn aims to release data on Snowflake Marketplace as soon as the underlying source releases new data. We check periodically for changes to the underlying source and, upon detecting a change, propagate the data to Snowflake Marketplace immediately. See our release process for more details.
Description
Getting Started with the Data
US_DEPARTMENT_OF_TRANSPORTATION_TIMESERIES
table notesFLIGHT_TYPE_ID
is a unique ID (primary key) for the timeseries table. It is an MD5 hash created by the components that make a domestic segment unique -- the aircraft carrier, aircraft, origin airport, and destination airport.AIRCRAFT_CARRIER_ID
can be joined to theAIRCRAFT_CARRIER_INDEX
table for more details on the carrier type and specifications (e.g., American Airlines).AIRCRAFT_ID
can be joined to theAIRCRAFT_INDEX
table for aircraft specifications (e.g., Boeing 737-300).ORIGIN_AIRPORT_ID
andDESTINATION_AIRPORT_ID
are joinable toAIRPORT_ID
in theAIRPORT_INDEX
table, which provides the airport alpha code (e.g, JFK), airport name (e.g., John F. Kennedy International), and geographic location details, joinable to Cybersyn's geography tables.
EAV Model: All Cybersyn products follow the EAV (entity, attributes, value) model with a unified schema. Entities are tangible objects (e.g. geography, company) that Cybersyn provides data on. Index tables contain all entities of a certain type. Timeseries tables contain all timeseries' dates and values that refer to an entity type. Additional tables, such as the relationships table and attributes table, are used to describe the entities and timeseries. Data is joinable across all Cybersyn products that have a GEO_ID.
Refer to Cybersyn Concepts for more details
Tables & Sources
Tables | Sources |
---|---|
|
Cybersyn Products
Tables above are available in the following Cybersyn data products:
Examples & Sample Queries
Evaluate the usage of Boeing airplanes (and their models) over time in the US.
Disclaimers
The data in this product is sourced from US Department of Transportation (DOT). Cybersyn is not endorsed by or affiliated with any of these providers. Contact support@cybersyn.com for questions.
Last updated