Airline System Management for Carriers and OTAs

Airline system management is the discipline of running the technology stack a carrier depends on to operate safely, commercially, and at scale. The stack covers passenger service, departure control, flight operations, fleet maintenance, crew management, revenue accounting, and customer servicing - each a distinct system with deep integration. OTAs and B2B aggregators touch a small part of this stack (mainly the reservation and ticketing layers through GDS or NDC) but the broader landscape is what keeps the airline flying. This page covers what airline system management actually entails, the major components and vendors, the role of PSS and DCS, where revenue management sits, how NDC changes the distribution layer, and what OTAs and travel platforms need to know about airline systems to integrate cleanly. The companion guides for the broader airline-side stack are airline reservation system as the cluster anchor for the commercial layer, airline ticketing system for the ticket-issuance flow, airline CRS for the central reservation system, and airline booking system architecture for the OTA-facing view. Cross-cluster reach into airline API integration covers the integration patterns that connect OTAs to the airline stack.

The Airline System Landscape

An airline runs more software than most non-aviation businesses appreciate. Eight system categories sit at the core, with deep integration across categories. Passenger Service System (PSS) is the airline's core commercial system - inventory, pricing, reservations, ticketing, and fare rules. Major providers are Amadeus Altea (broad market), Sabre SabreSonic (US and Europe), Travelport for some carriers, and Navitaire (Amadeus subsidiary for low-cost carriers). The PSS is the system that OTAs and B2B platforms see through GDS or NDC. Departure Control System (DCS) handles airport check-in, baggage tagging, weight and balance, boarding, and aircraft load control. It runs at the airport with offline failover. Common providers are Amadeus Altea Departure Control, Sabre SabreSonic Customer Service, and IBS iFly Res. Flight Operations and Crew Management covers flight planning (routes, fuel, weather), crew scheduling and tracking, dispatch, and operational control. The disruption-recovery functions (delays, diversions, cancellations) live here. Sabre Movement Manager, Lufthansa Systems NetLine, and Jeppesen are common providers. Maintenance and Engineering tracks aircraft components, inspection cycles, defects, parts inventory, and regulatory compliance. AMOS, Trax, Ramco, and IBS iMaintenance serve this layer. Revenue Accounting handles ticket revenue, interline settlements through IATA's BSP, agent commission, and refund processing. ATPCO and IATA's BSP infrastructure underpin much of this, with airline-side systems from Sabre, Amadeus, and others tying it together. Customer Relationship Management and loyalty programs run on top of the PSS, often as separate modules or as integrated CRM platforms. Cargo management runs separately for airlines that carry freight, integrating with the PSS for shared aircraft scheduling but otherwise distinct. NDC orchestration sits between the airline's PSS and external partners, exposing modern offer-and-order APIs that bypass the GDS for participating partners. The cluster guide on airline reservation system covers the PSS-side commercial layer in depth, and the integration view from the OTA side is in airline API integration.

The cluster guides below cover the airline-system components that an OTA or B2B platform interacts with and the broader integration patterns.

What OTAs Touch And What They Do Not

OTAs and B2B aggregators touch a narrow slice of the airline's system landscape, and understanding the boundary helps integration teams avoid surprises. Search and pricing calls hit the airline's PSS through the GDS or NDC. The OTA sends a search request with origin, destination, dates, and traveller count; the PSS returns available inventory and prices according to the revenue management system's current rules. Booking and ticketing calls also hit the PSS. The OTA sends a booking request with passenger details and payment confirmation; the PSS creates a Passenger Name Record (PNR), holds the seats, and returns confirmation. The ticketing call issues the actual ticket, which carries an e-ticket number the airline's systems track from then on. Webhooks and lifecycle events flow from the airline back to the OTA - schedule changes, cancellations, refund processing, fare drops, ancillary updates. The OTA's webhook receiver consumes these and propagates them to travellers. Servicing calls apply for cancellations, modifications, name changes, and re-issues. They hit the PSS and follow airline-specific business rules for fees and timing. What OTAs do not touch is everything else. The DCS at the airport runs without OTA involvement; the OTA's role ends at ticket issuance. Flight operations, crew management, maintenance, revenue accounting, cargo, and CRM systems are airline-internal. Disruption-recovery decisions (rebooking after a cancellation, irregular operations responses) are made in the airline's operations centre and propagated to OTAs through schedule-change webhooks. The integration boundaries matter for two reasons. First, the OTA cannot drive airline-internal decisions - the OTA cannot decide which aircraft flies a route, when a flight cancels, or how a disruption is recovered. The OTA's job is to consume the airline's decisions and present them to travellers. Second, the OTA's resilience patterns (circuit breakers, fallback routing, retry logic) protect against airline-system outages that the OTA cannot prevent. When an airline's PSS goes down, the OTA's job is to fail gracefully and recover when the system returns, not to attempt to compensate. The cluster guide on airline booking system architecture covers the OTA-side patterns, and the cross-cluster integration view is in real-time travel API integration.

NDC, Direct Connect, And The Distribution Shift

The airline distribution layer is changing because airlines want more control over the offer-and-order flow than the GDS gives them. NDC (New Distribution Capability) is the IATA standard for direct distribution that lets airlines expose richer offers, ancillaries, and dynamic pricing through a modern XML or JSON API. NDC sits on top of the airline's PSS and exposes the same inventory through a different channel. Airlines that have invested in NDC offer commission tiers favourable to OTAs that integrate directly. Direct connect is the broader term that includes NDC plus any pre-NDC direct API a carrier built. Some airlines (especially major carriers in mature markets) maintain direct APIs alongside NDC. The migration arc at most airlines is gradual. The PSS stays in place; NDC is added as a layer that progressively absorbs more of the distribution. Some airlines now route a majority of their distribution through NDC for partners that have integrated; others remain GDS-heavy with NDC as supplementary. The pace varies by region, by carrier strategy, and by the cost of GDS distribution to the airline. For OTAs and aggregators, the NDC integration decision is per-airline and per-route. The commission spread between NDC and GDS rates, the OTA's volume on each airline, and the engineering cost of integrating NDC for that airline drive the priority. Most modern OTAs run NDC on a handful of airlines where the spread justifies the work and GDS for the rest. Engineering cost of NDC is real. Each airline implements NDC with its own quirks; the standard is more consistent than pre-NDC direct APIs but still requires per-airline adapters. A typical NDC integration takes 3 to 6 months for a major carrier and adds ongoing maintenance burden. The cluster guide on OTA commission on airline tickets covers the channel economics, and the broader API integration patterns are in airline API integration. The distribution future appears to be hybrid - GDS remaining important for the long tail of airlines and routes, NDC growing for major carriers and high-value routes, and pre-NDC direct APIs surviving on a few airlines that have not migrated. OTAs and aggregators that maintain capability across all three channels stay flexible as the mix evolves. The airlines that move fastest on NDC capture the savings on GDS segment fees; the OTAs that move fastest on NDC capture the commission upside.

Operational Reality And The Integration Mindset

An airline is a 24-hour operation with low tolerance for system failure. The systems behind the airline reflect that operational discipline, and any OTA or B2B platform integrating with airline systems should take the same view. Reliability expectations at major airlines target 99.9 percent or higher availability for the PSS during peak travel periods. The operational impact of an outage is hours of disrupted travellers and recovery costs measured in millions per major incident. The OTA's integration cannot match this reliability on its own (the OTA depends on the airline's reliability) but should not contribute to outages either - the OTA's circuit breakers, retry logic, and rate-limit respect protect the airline from cascading load during operational stress. Schedule changes are constant. Airlines republish schedules months in advance and adjust them constantly for operational, commercial, and regulatory reasons. Over a typical 6-month booking window, 5 to 15 percent of bookings see a schedule change of some kind. The OTA's webhook handling for schedule-change events decides whether the traveller learns about the change in time or at the airport. Build the webhook receiver as production-grade infrastructure, not as an afterthought. Disruption events (weather, mechanical, crew availability, regulatory) cancel or reroute hundreds of flights per major incident. The OTA's job during disruptions is to consume cancellation events promptly, communicate to affected travellers, support refund or rebooking flows through the airline's policies, and keep the OTA's own status visible to travellers searching for new bookings. Disruptions are when integrated infrastructure proves itself. Compliance in airline systems is heavy. PCI for payment, GDPR for personal data, IATA standards for distribution, FAA or local equivalent for safety, and country-specific privacy and cyber-security laws layered on top. The OTA's compliance posture has to align with the airline's expectations as defined in distribution contracts. Settlement through IATA's BSP and airline-specific reporting is the financial discipline that closes the loop. Daily settlement files match ticketed bookings against the OTA's records; mismatches are investigated and resolved. Modern OTAs run reconciliation against settlement files on automated infrastructure rather than manual export, and surface discrepancies to a queue with SLA. The integration mindset that works is treating the airline's systems with respect for their operational complexity. The OTA cannot drive airline-internal decisions; the OTA's job is to integrate cleanly, fail gracefully, and recover quickly. OTAs that build integrations as production infrastructure with the same discipline the airlines bring to their own systems run reliably and earn trust with carriers. OTAs that treat airline integration as a marketing feature break under load and lose access. The cluster anchor on flight reservation system covers the broader OTA-facing view, and the cross-cluster integration patterns are in real-time travel API integration. Airline system management is not the OTA's domain, but understanding it shapes how an OTA builds its own integration so the two operate together rather than against each other.

FAQs

Q1. What is airline system management?

Airline system management is the discipline of running the technology stack a carrier uses to fly aeroplanes safely, sell tickets, manage staff, maintain fleet, and report to regulators. The stack includes Passenger Service System (PSS), Departure Control System (DCS), Maintenance and Engineering, Flight Operations, Crew Management, Revenue Accounting, and Customer Servicing.

Q2. What is a Passenger Service System (PSS)?

PSS is the airline's core commercial system. It handles inventory and pricing, reservations, ticketing, and fare rules. Major PSS providers are Amadeus Altea, Sabre SabreSonic, and Navitaire (for low-cost carriers). The PSS is the system OTAs and B2B aggregators interact with through GDS or NDC channels for search, book, and ticketing.

Q3. What does a Departure Control System (DCS) do?

DCS handles airport check-in, weight and balance, boarding, and aircraft load control. It runs at the airport and integrates with the PSS for passenger lists and with ground-handling agents for physical operations. DCS is the system passengers see at the check-in counter and at boarding; the PSS is the system they see during booking.

Q4. How does an airline reservation system relate to airline system management?

The reservation system is one component of the broader system landscape - specifically the part of the PSS that handles bookings and inventory. Airline system management covers the reservation system plus the systems around it (DCS, ops, fleet, crew, accounting). OTAs and B2B platforms touch the reservation system primarily through GDS or NDC.

Q5. What systems do OTAs and B2B aggregators touch?

OTAs and aggregators touch the airline's reservation and ticketing system through GDS connections (Amadeus, Sabre, Travelport) or NDC connections directly to the carrier's API. They do not touch DCS, ops, fleet, or crew systems. Webhooks from the airline's reservation system inform the OTA of schedule changes, cancellations, and lifecycle events.

Q6. What is the role of revenue management in airline systems?

Revenue management adjusts seat availability and pricing across cabin classes and dates to maximise total revenue per flight. The revenue management system reads booking pace, competitor pricing, and historical patterns and writes inventory and price decisions back to the PSS. OTAs see the result through fare variations across booking class.

Q7. How does NDC change airline system management?

NDC moves the offer-and-order layer from the GDS to the airline's own systems, letting the carrier expose richer offers and ancillaries directly. The airline's NDC implementation sits on top of the PSS and reservation system, exposing a modern XML or JSON API to OTAs and B2B platforms. NDC does not replace the PSS; it adds a modern distribution channel.

Q8. What is the relationship between airline systems and ground handling?

The DCS integrates with ground-handling agent systems for baggage handling, aircraft turnaround, and ramp operations. At many airports the airline outsources ground handling to a third party who runs their own systems that interoperate with the airline's DCS. Disruption recovery flows between the two through standardised messaging.

Q9. How does an airline manage maintenance and engineering systems?

Maintenance and Engineering systems track aircraft components, scheduled inspection cycles, defect reports, parts inventory, and regulatory compliance. They feed flight operations decisions and integrate with crew management systems for engineer assignment. Major providers include AMOS, Trax, and Ramco for aviation maintenance.

Q10. Can a small airline use the same systems as a major carrier?

Smaller airlines often use lighter-weight versions of the same vendors or specialised systems for low-cost and regional carriers. Navitaire is common for low-cost carriers; Hitit, Crane, and others serve regional and start-up airlines. The system functionality is similar; the depth of customisation, integration, and operational maturity differs.