OAG Role in Providing Flight Schedule Data

Aviation runs on data—but it’s highly fragmented. OAG is one of the main providers that brings it together to power airport screens and travel apps. In this article, we’ll explain what OAG does and how it compares to other flight data providers.

What is OAG?

OAG (Official Aviation Guide) is the world’s leading provider of digital flight information. It acts as the central aggregator for the global aviation ecosystem, covering 99 percent of scheduled flights and providing millions of real-time status updates daily.

Founded in 1929, it originally published printed flight schedules—literally books used by airlines, airports, and travel agents. Today, OAG operates a massive cloud-based data network, managing a database of over 900 airlines and 4,000 airports.

What does OAG do?

OAG provides the standardized technical infrastructure that allows airlines, airports, and other travel companies to exchange flight data in a universal format. It validates, standardizes, and distributes this data across the industry, focusing on two main categories.

Schedules – planned data about what is expected to happen months or weeks from now. OAG’s schedule database contains around 55-60 million flights departing over the next two years.

Flight status – operational data about what is actually happening right now, including delays, cancellations, gate changes, etc. OAG processes over 1 billion status updates yearly – that’s around 40 per second.

Beyond that, OAG also provides datasets on fares, passenger bookings, emissions, and over 20 years of historical flight data, along with a range of analytical services.

Why is OAG important?

There are hundreds of airlines and thousands of airports, each using different internal software. Without a central hub like OAG, a flight search engine (like Google Flights) would have to build a separate technical connection with every airline in the world just to know their flight times.

Instead, airlines send both their schedules and operational updates—like delays or cancellations—to OAG. OAG processes and distributes this information, so other players can rely on a single, consistent source for both planned and real-time flight information.

The role of OAG

To better understand the role of OAG, let’s trace the flow of data from an airline’s internal planning to the final offer seen by a traveler.

Data ingestion

The lifecycle of a flight begins up to 365 days before departure. Airlines define their routes and assign aircraft types within their internal scheduling and network planning systems.

While these plans are set months in advance, they are dynamic. Schedules change frequently (due to maintenance, crew shifts, or seasonal demand), with the highest volume of updates occurring in the 24 hours leading up to takeoff.

To have the most current and accurate information, OAG ingests data from several sources.

Airlines. The majority of OAG's data comes directly from airlines. Carriers share their schedules months in advance and send real-time operational updates during an active flight window.

Airports. When airlines don't provide data directly, OAG uses airport feeds to fill gaps in real-time status, such as gate changes or actual landing times.

Government and industry bodies. OAG integrates data from civil aviation authorities and air traffic control organizations (such as the FAA and EUROCONTROL) to track delays and industry standards.

Data normalization

OAG doesn't just pass through raw files. It acts as a processing layer that cleans and prepares data for downstream systems. It involves three key stages.

Standardization – converting different airline-specific formats into a clean, unified, and industry-standard database.

Validation – running over 350 data integrity checks to flag conflicting info or logic errors (e.g., if an airline claims a flight arrives before it departs).

Adjustment – fixing incorrect data and adding missing pieces (e.g., terminal codes).

OAG also applies Minimum Connection Times (MCT) rules to ensure connections are feasible. For example, if an airline says a connection in Heathrow takes 20 minutes, but the airport rule says 60, OAG adjusts the data so that an “impossible” ticket is not created.

Data distribution

OAG then sends clean, verified data to the Global Distribution Systems (GDSs) via two main feeds.

Bulk schedules feed. Once or twice a day, OAG sends a massive file update to the GDS to update the planned schedules (flight numbers, aircraft types, and departure times for the next year).

Real-time status feed. OAG pushes live updates to the GDS (e.g., “Landed” or “Delayed for 20 min”) to reflect current operational reality.

The GDS combines this OAG data with fares from ATPCO and real-time seat availability from the airline’s Passenger Service System (PSS) to build the final bookable offer for travel resellers.

This is the common flight data flow in a typical travel booking scenario. In addition to GDSs, OAG provides flight information to 250+ airlines and 300+ airports.

On top of that, it also supplies this data to other entities, including metasearch engines, hospitality companies, car rentals, travel tech providers, financial analysts, researchers, etc.

Comparison with other flight data providers: OAG, Cirium, FlightAware, Flightradar24, direct airline integrations

OAG is not the only flight data provider. However, while most providers offer similar core datasets (schedules and status), they are different in focus and technical architecture.

OAG pros and cons

OAG is often considered the industry’s “Gold Standard” for schedules and verified airport operations.

Pros:

• Schedule authority – widely recognized as the most accurate database for planned schedules and MCT
• Cloud native – offers direct data, real-time sharing through Snowflake
• Rich context – provides operational details like gate assignments, terminal changes, and baggage carousel IDs
• Historical database – holds flight data since 2004
• Diverse market intelligence – integrates diverse datasets, including airfare and emission analytics

Cons:

• Cost – positioned as a premium enterprise solution with higher entry costs
• Tracking latency – while real-time, it focuses on event-based status rather than the high-frequency positional tracking found in satellite-first providers.

Data available via:

• RESTful JSON APIs
• Direct data sharing in the cloud via Snowflake
• Push service via Azure Event Hubs
• Flat file transfers

Best for: GDSs, major booking engines, and airports that require verified schedule integrity and on-the-ground accuracy.

Cirium (including FlightStats) pros and cons

Cirium (a RELX brand) represents the industry’s most significant consolidation of aviation data assets, including legacy brands like FlightStats (status), Innovata (schedules), and Ascend (valuations).

Pros:

• Real-time tracking – integrates satellite data from the Aireon ADS-B network for global visibility
• Multi-source verification – uses the Cirium Core model that cross-references over 2,000 global sources to ensure data integrity
• Fleet data – includes exhaustive aircraft specifications (age, engine type, ownership), vital for finance and maintenance sectors
• Historical database – owns 20+ years of schedules and status data

Cons:

• Integration complexity – the sheer volume of available data fields and legacy brand integrations can make initial API implementation more complex for smaller teams
• Cost – enterprise-grade datasets typically require opaque, long-term contract negotiations

Data available via:

• APIs (REST-based access in JSON/XML)
• Cirium Sky data streams
• Flat file transfers
• Cloud sharing through Snowflake and Amazon Redshift

Best for: Financial institutions, fleet managers, and consultants focused on asset valuations, network planning, and emissions reporting.

FlightAware pros and cons

FlightAware is the global leader in aircraft tracking and predicting ETAs, powered by a massive terrestrial ADS-B network and satellite data.

Pros:

• Predictive intelligence – their Foresight engine provides highly accurate ETAs based on weather, taxi times, and air traffic congestion
• Superior tracking – considered best-in-class for mid-flight positioning using the Aireon constellation
• Developer-friendly – offers AeroAPI with a clear, self-service pay-as-you-go pricing model that is accessible for startups

Cons:

• Operational context – historically less focused on airport-side data (like baggage belts or check-in counters) than OAG or Cirium
• Geographic focus – most extensive coverage in North America
• Data rights – public tiers have strict limits on data storage and redistribution

Data available via:

• RESTful JSON APIs
• Firehouse data streaming

Best for: Logistics companies, flight-tracking apps, and startups needing high-frequency positional data and rapid API deployment.

Flightradar24 pros and cons

Flightradar24 is primarily focused on visual, real-time global tracking through its massive crowdsourced receiver network.

Pros:

• Visual experience – features high-quality AR views and 3D flight tracking
• Global ADS-B coverage – superior real-time coverage in Europe and Asia due to its vast receiver network
• Military and non-standard tracking – frequently displays details for military and private aircraft that other sites might filter or hide
• Detailed overlays – business plans include advanced weather and airspace layers (turbulence, icing, lightning)

Cons:

• Operational context – less focused on airport-side data
• Geographic focus – largest coverage in Europe, Asia, and Oceania

Data available via:

• APIs (REST, gRPC)
• WebSockets data streaming

Best for: Enthusiasts, media outlets, and spotters requiring the most immersive visual tracking experience.

Direct airline feeds

Bypassing aggregators to source data directly from airlines provides the rawest version of the truth, but comes with heavy overhead.

Pros:

• Latency – eliminates the aggregator processing delay (though OAG/Cirium have reduced this to seconds)
• Cost efficiency – removes the middleman fee for high-volume users

Cons:

• Integration complexity – every airline has different technical standards (AIDX, SSIM, proprietary APIs)
• Maintenance – engineering costs for managing hundreds of individual connections often exceed aggregator subscription fees
• No cross-verification – there is a high probability of data conflicts or inaccuracies that aggregators resolve by cross-referencing data from multiple sources

Data available via (depends on the airline):

• Flat file transfers
• APIs
• AIDX XML messages

Best for: Tier-1 Airlines and mega-hubs managing their own internal operations where every millisecond of latency is critical.