DALLAS — You are sitting in the cabin, waiting. Idle time, you fear. The aircraft has not left the gate, and you begin to wonder whether you will be asked to gather your belongings and board another airplane. If that's the case, for the airline, finding an available aircraft is only the beginning of a recovery plan.
To replace a delayed flight’s airplane, an airline also needs a qualified crew able to work the revised schedule, a workable flight plan and airport teams prepared to handle the departure. A change that solves one problem can create another elsewhere in the operation.
SITA’s proposed purchase of Flightscape offers a way to examine those connections. On October 26, CAE agreed to sell its airline operations software business for an enterprise value of US$500m, subject to customary adjustments. Closing is expected in the first half of 2027, conditional on regulatory approvals and other closing requirements. Flightscape continues operating as usual until then.
For airlines, the practical question is how information reaches the systems and people making recovery decisions, and how an accepted decision reaches everyone who must carry it out.
Flightscape spans flight planning, crew management, operations control, ground activities and in-flight services. SITA says its software is used daily by more than 90 airlines. The buyer’s acquisition announcement identifies a gap between information shared across aviation and the systems where airlines make operational decisions.
These functions have different jobs. Crew software manages people and their assignments. In its Flightscape product description hosted by IBM, CAE describes tools for planning rosters, tracking qualifications and repairing disrupted crew assignments, with configurable rules covering regulatory, labor and company requirements. The listing is supplier-provided information, rather than an IBM validation of performance.
Flight planning addresses the journey the aircraft will make. Jeppesen’s flight-planning and dispatch portfolio brings together route optimization with weather, weight-and-balance and tracking tools. An aircraft assignment and a crew roster therefore provide only part of the information needed to prepare a departure.
Consider an illustrative recovery decision: an inbound aircraft is late, and controllers identify another airplane for its next flight. Crew control must check whether the proposed crew is qualified and whether the revised assignment fits the applicable rules. Dispatch must assess the flight using the replacement aircraft and current conditions. Ground teams need the revised aircraft and departure information.
If the crew cannot operate that assignment, the aircraft solution needs revisiting. If conditions change while those checks are underway, the proposal needs checking again. This is the integration problem: each function must assess a compatible version of the plan, then receive the changes that follow.
Airport coordination provides a documented example of why shared information needs agreed procedures. Schiphol describes a collaborative decision-making process in which the airport, airlines, ground handlers and air traffic control share operational information through a common portal.
Expected landing, taxi and gate times help partners predict when aircraft and resources will be needed. Better departure estimates also help EUROCONTROL allocate scarce slots. Schiphol explicitly observes that making each participant’s own process efficient does not, by itself, produce the desired efficiency across the whole operation.
That distinction matters for airline software. A revised departure time has value only if partners can use it to adjust their work. A shared display can improve awareness; carrying out a recovery also requires procedures that determine who updates the plan and who acts on it.
SITA is expanding on the airport side, too. As Airways reported, its separate agreement to acquire Collins Aerospace Airport Solutions covers passenger-processing, baggage and airport operations technology. That transaction also remains subject to closing conditions. The two proposed purchases broaden SITA’s intended reach, but do not establish that their systems already operate together.
SITA’s June acquisition of Big Blue Analytics added OCC Assistant Manager, or OCCam. SITA describes the platform as evaluating aircraft, crew, passenger and maintenance constraints together and producing recovery plans in minutes. Those are the supplier’s claims about its existing platform, not demonstrated results from a completed Flightscape integration.
Generating a proposal also leaves operational responsibility in place. For U.S. domestic operations under Part 121, the pilot in command and aircraft dispatcher share responsibility for preflight planning, delay and dispatch release. In a 2020 memorandum considering dispatchers working from home, the FAA called for procedures addressing coordination with other airline units, including maintenance control.
For the proposed combination, useful evidence would show which systems supply current constraints, how controllers accept or amend a proposal, and whether accepted changes reach the operational systems that execute them. Performance should be assessed through completed recoveries, including subsequent revisions and passenger consequences. The speed of producing an initial plan measures only one part of that work.
SITA says integration will start after closing, proceed in stages with customers, and preserve modular, open products that connect to airlines’ existing systems. Its announcement does not provide a detailed deployment schedule or explain the interfaces and decision controls for the combined offering.
Those details will determine what the acquisition changes inside an airline. The meaningful demonstration will be a recovery decision that survives crew and dispatch checks, reaches airport partners and remains usable when the next operating update arrives.


.webp)