CONTROL operations control software
FlightAtom CONTROL is an Aurora add-on that brings configured flight, crew, passenger, and disruption context into a source-aware OCC review workflow. It can present candidate recovery options; authorized controllers validate the operational state and approve any action.
See where CONTROL fits around Aurora.
CONTROL is a connected add-on for Aurora. Add it when you need disruption response and recovery review; the exact data and workflow connections are configured for your operation.
See it in action
Interface preview with fictional sample data. Final screens, fields, and connected sources vary by operator configuration.
User View
- Flight Status: Live flight monitoring feed
- Alert Feed: Real-time operational notifications
- Comm Hub: Team communication center
Admin View
- OCC Dashboard: Operations control center overview
- Disruption Manager: Manage irregular operations
- Resource Allocation: Gate, crew, and aircraft assignments
Coordinate disruption response with shared context
Source-Aware Monitoring
Flight and delay monitoring using available connected sources, with freshness and source state kept visible for operational review.
Disruption Management
Reviewed irregular operations workflows with recovery options and impact context drawn from configured sources.
Crew Reassignment
Candidate crew changes using configured qualification, duty-time, location, and rest context, with reviewed update workflows.
Aircraft Swap
Candidate aircraft substitutions using configured MEL status, range, capacity, and downstream operational context.
NOTAM Integration
Supported NOTAM-source filtering that surfaces potentially relevant restrictions for operational review.
Decision Support
Candidate disruption options using configured cost, passenger-impact, and operational-constraint context for authorized OCC review.
Decision support across configured network context
CONTROL brings available network context into one reviewed workspace, helping OCC see disruption exposure and compare recovery options without replacing operational authority.
Combines configured aircraft, crew, gate, weather, and ATC context
Builds a source-dependent view of configured interdependencies and can surface downstream exposure, such as a possible misconnect several rotations after a late inbound, for OCC review.
Candidate scenarios using configured operating objectives
When disruptions hit, CONTROL can present scenarios ranked by configured passenger-impact, cost, and operational objectives, with rationale and source context. Operators approve actions; downstream handoffs depend on configured integrations.
Surfaces short-horizon operational risk
When supported sources provide weather, ATC flow, and crew-positioning context, CONTROL can highlight possible near-term pressure points. OCC validates the signals and decides whether any protective action is appropriate.
Attention Required Across The Network
Fictional sample data showing the type of reviewed priority feed CONTROL can present to an OCC.
-
LFPG ATC flow restriction effective 14:00–17:00Z: 18 sectors at risk, 4 priority recovery plans staged with cost ranking.
-
Hub bank at LGW from 18:30: 2 inbounds with crew nearing duty limits, candidate swaps checked against configured FTL and recency records for controller review.
-
Snow event probability 70%+ at AMS tomorrow: pre-cancellation candidates ranked by reaccommodation cost and customer impact.
-
Recovery from FA118 diversion to MAN: passengers re-protected with 92% same-day rebook.
-
6 sectors flagged for possible protection via rotation swap: estimated downstream delay exposure: 142 minutes.
Airline operations control software FAQs
What is IROPS and how does FlightAtom CONTROL support review?
IROPS (Irregular Operations) includes disruptions such as delays, cancellations, and diversions. FlightAtom CONTROL can combine available flight, crew, passenger, and disruption context and present candidate recovery options. Coverage depends on connected sources; authorized controllers validate the state and approve any action.
How does crew reassignment work during disruptions?
When disruptions occur, CONTROL can surface candidate crew changes using configured qualification, duty-time, location, and fatigue context. Authorized controllers review and approve any reassignment and associated communication or schedule update.
What decision support does the AI provide?
CONTROL can compare supported disruption options using configured financial and operational inputs. Coverage, freshness, and relevance depend on connected data, and authorized OCC personnel validate the options and retain the decision.
How does FlightAtom Control handle aircraft swaps?
CONTROL can compare candidate aircraft substitutions using configured MEL status, range, capacity, and downstream context. Authorized OCC personnel validate source state and operational effects before approving a swap.
Does FlightAtom Control integrate NOTAMs?
When integrated with supported NOTAM sources, CONTROL can filter notices against configured routes and flights and surface potentially relevant restrictions for review. Dispatch or OCC personnel validate applicability and decide what action to take.
What forward-looking indicators can CONTROL surface?
When configured sources provide aircraft, crew, gate, weather, and ATC context, CONTROL can surface short-horizon operational risk indicators. These source-dependent signals are not event predictions; authorized OCC personnel validate them and decide whether any protective action is appropriate.
Does CONTROL replace approved dispatch or OCC systems?
No. FlightAtom CONTROL is a decision-support and coordination workspace. It does not replace approved dispatch releases, operational communications, controlling records, or authorized OCC judgment; system authority and handoffs are defined for each implementation.
Where this fits: plan, operate, recover
FLIGHTS, OPS, and CONTROL provide context at different points in the operating day; configured sources and authorized users define each workflow boundary.
| Flight | Ops | Control | |
|---|---|---|---|
| What it supports | Synchronized flight records and performance review | Configured day-of-operations coordination | Reviewed disruption and recovery options |
| Typical timing | Across and after operational activity | During routine day-of-operations activity | During disruption and recovery review |
| Primary user | Flight operations / performance teams | Ops controller / duty officer | OCC / network operations |
| Core context | OOOI records, post-flight documents, fuel, and performance | Turns, delays, tracking, weather, and NOTAM review | IROPS exposure and candidate crew or aircraft changes |
The full handoff (Plan → Release → Operate → Recover → Analyze) is on the platform overview.
Coordinate disruption recovery with clearer context
Shared source context and candidate recovery options for authorized OCC review.
Discuss CONTROL