Airline Operations Control Centre Software
See the flying day clearly. Act on the right flight.
Give operations controllers a shared view of active flights and the decisions still open. Fx Airline Ops brings schedule times, aircraft and crew assignments, dispatch readiness, operational changes and flight actuals into a single OCC workspace.
Control becomes difficult when context is scattered
A flight number is only the start. The OCC needs to know which aircraft and crew are assigned, why a departure moved, whether release checks are clear and what happened after the flight operated.
Built around the way you work
Each capability is part of the connected FlightStratix workspace.
Flight board and flight detail
Review flights by UTC operating window, open a flight and inspect its assignments, movement times and related actions.
Change with a reason
Record departure retimes, delay minutes/codes, cancellations and diversions while retaining the relevant operational context.
Crew and aircraft readiness
Assign or change the aircraft and crew, review assignment checks and inspect operational release gates before signing.
Actuals and operational follow-through
Capture OUT/OFF/ON/IN times and review operational flight changes and status in the same record.
From start to finish
Day-of-flight control, assignments and operational actuals
Give controllers one working picture of active flights, assigned resources, release status and changes.
A daily board built around flight instances
Filter the OCC by UTC date range, open individual operational flights and work from a live record rather than a printed timetable. Each flight carries its carrier, flight number, airports, scheduled times, assigned aircraft, crew and operational status.
Record changes without losing the reason
Retime departures and arrivals with delay reason, code and minutes. Cancel a flight with a reason, record a diversion airport, and enter OUT/OFF/ON/IN actuals after operation. Revision checks are part of flight mutations to reduce stale conflicting edits.
Assignments and dispatch checks belong together
Aircraft and crew assignments are visible in the flight detail, with crew checks before saving. Dispatch review shows current gates and stored release information so controllers can see which actions need attention before operational acceptance.
Review what the day actually delivered
Close the operational loop with sector metricsoperated versus cancelled sectors, punctuality and utilisation. These reports support team reviews without confusing actual operating times with customer-booking, ticketing or revenue-management records.
What an airline controller needs from an OCC screen
Find the exact operating flight, not merely a timetable line
The OCC board filters operational flights by a selected UTC date window. Opening a flight shows the airline and flight number, operation type, airports, scheduled timing, aircraft, crew and operational state. Controllers can create ad-hoc flights when flying falls outside the recurring published schedule. The board and flight drawer are where a duty team records actual decisions, while recurring schedules live in the separate timetable workflow.
Record disruption actions with a reason
Retime a flight with a delay code, minutes and written reason. Cancel with a reason, record diversion airport when required and capture OUT/OFF/ON/IN actual times once the flight operates. Revision checks help prevent stale changes from overwriting newer data. These are useful capabilities during shift change: the next controller can see the recorded event rather than relying on an oral explanation of why the departure moved.
Link aircraft status and crew decisions to the flight
Aircraft may be assigned or removed from the operational flight, and crew assignments can be checked before saving. Shared crew records supply relevant qualifications and time-limit information, subject to the configured tools and rules. The OCC should show what changed without pretending to be the full crew rostering screen. Direct readers to crew management for detailed planning and aircraft rotations for sequential tail impacts.
Treat dispatch acceptance as a separate operational gate
The flight's dispatch review includes configured readiness conditions such as aircraft and crew suitability, technical findings, station requirements, handling and briefing material. Release records can be generated, and the assigned PIC can review or accept the relevant release in the crew portal. Significant operational changes can reopen the review. Displaying release readiness in the OCC is valuable because a departure cannot be described as ready merely because its timetable, crew and aircraft fields are filled.
Give operations a factual end-of-day report
Recorded actuals support calculations and breakdowns for operated and cancelled flights, on-time performance, delay reasons and aircraft utilisation. Sector cost and fuel fields can add operational commercial context. The reports do not replace a passenger reservations system or an audited general ledger. The page should keep the promise specific: a clearer record of the flying day with fewer separate places to reconstruct what happened.
Make each decision against the operating flight.
Keep changes and actuals in context
Review aircraft and crew assignments, recorded flight events and readiness on the relevant operating flight. A controller should be able to trace a changed plan back to the sector it affects rather than reconstructing the day from separate updates.
Explore the airline operations workspaceConnect disruption review with the rotation
When an aircraft is late or a sector is changed, inspect the later sectors before deciding what to amend. Keep the proposed response subject to operational review and retain the context of the original flight.
Explore disruption management- Open flightSelect from the OCC boardComplete
- Review assignmentsCheck aircraft and crewComplete
- 03Record changeRetime, delay or cancelIn review
- 04Dispatch reviewCheck release gatesPending
- 05Enter actualsOUT/OFF/ON/IN timesPending
See it in context
Two teams editing the same delayed flight
One controller updates the departure after an aircraft delay while another has opened the same flight to change crew. Revision handling can identify a stale edit instead of silently accepting an outdated record. Crew is rechecked, dispatch readiness is reviewed and the delay reason remains against the flight for subsequent reporting. See Airline Ops.
An operational example
At 07:30 UTC a controller notices a delayed inbound. They open the affected outbound from the OCC, record the reason, confirm the assigned aircraft and crew, and review dispatch requirements. The board remains a single reference through take-off, landing and final arrival actuals.
Where it fits in FlightStratix
Frequently Asked Questions
What is the difference between Airline Ops and the OCC page?
The Airline Ops platform covers schedules, crew planning, maintenance, governance and reporting. This page focuses on controllers managing the day-of-flight record.
Can two controllers change a flight simultaneously?
Flight mutations include expected revisions, which allow the service to detect stale edits. Exact collaboration behaviour should be verified in the deployed workflow.
Does the OCC replace the airline timetable module?
No. The timetable publishes flights; the OCC manages the operational flight once it exists.
Is every disruption resolved automatically?
No. Controllers review and apply documented changes; full network-wide automatic recovery is not established by the supplied implementation reference.
Explore FlightStratix solutions
Keep aircraft, crew and flights in the same operational picture.Book an Fx Airline Ops demo.
Book a 30-minute walkthrough tailored to your operation.