Airport management systems orchestrate hundreds of daily flight operations including gate assignment, ground handling, baggage routing, and passenger information display. The system must coordinate multiple stakeholders — airlines, ground crews, ATC, and passengers — with real-time accuracy and high availability.
Core Schema
Flight (flight_id, airline_id, flight_number, aircraft_type, origin, destination, scheduled_departure, scheduled_arrival, actual_departure, actual_arrival, status ENUM scheduled/boarding/departed/arrived/cancelled/diverted). Gate (gate_id, terminal, gate_code, compatible_aircraft_types, current_flight_id). BaggageItem (bag_id, flight_id, passenger_id, tag_number, status ENUM checked_in/loaded/in_transit/delivered/lost, last_scanned_at, last_location).
Gate Assignment Algorithm
Gate assignment considers aircraft type compatibility, terminal adjacency to the aircraft’s next scheduled flight to minimize repositioning time, buffer time between flights using the same gate (minimum 45 minutes for cleaning and boarding turnaround), and airline-preferred terminals. The algorithm is implemented as a constraint satisfaction problem solved by a greedy heuristic: flights are sorted by departure time and each is assigned to the compatible gate with the smallest buffer-violation score. Reassignment is triggered automatically by delays or schedule changes and conflict alerts are sent to the operations center.
Baggage Tracking
The baggage handling system (BHS) reads RFID or barcode tags at each conveyor segment checkpoint. Scan events are published to an ingest queue and a consumer updates BaggageItem.status and last_scanned_at. The status lifecycle is: checked_in → sort_center → load → loaded → offload → carousel → delivered. Misrouted bags are detected when a scan location is inconsistent with the bag’s destination flight. An alert is generated and the bag is flagged for manual retrieval and rerouting.
Ground Crew Coordination
The ground operations manager assigns crew teams to flights. GroundTask (task_id, flight_id, task_type ENUM fueling/catering/cleaning/baggage_loading/pushback, crew_team_id, scheduled_start, actual_start, actual_end, status). All tasks for a flight must reach completed status before departure clearance is granted. Crew members update task status via a mobile app. Delay cascade logic: if fueling is delayed, the departure_estimate is updated and downstream connection flights are reassessed for impact.
FIDS Integration
The Flight Information Display System receives flight status updates via pub/sub. A FIDS controller service maintains display boards across all terminals. Each screen is subscribed to updates for its relevant gate range. Status changes are reflected on screens within 5 seconds. Emergency announcements such as cancellations and gate changes are prioritized over routine status updates in the message queue. Screens show boarding time, gate number, and status with color coding: green for on time, yellow for delayed, and red for cancelled.
ATC Integration
Aircraft arrivals and departures are coordinated with Air Traffic Control via ACDM (Airport Collaborative Decision Making). The airport management system sends the target off-block time (TOBT) to ATC for departure slot allocation. ATC returns the assigned take-off time (ATOT) and the landing slot for arriving flights. Slot conflicts are resolved by the ACDM protocol with airline operations centers participating in the negotiation. All TOBT and ATOT updates are logged and used to measure on-time performance.
Frequently Asked Questions: Airport Operations Management System
What algorithm is used for gate assignment in an airport operations management system?
Gate assignment is a constraint satisfaction problem: each flight has an occupancy interval and constraints on gate type (wide-body, customs), terminal preference, and minimum taxi distance. A greedy first-fit algorithm produces an initial solution; a local-search metaheuristic (simulated annealing or tabu search) improves it via gate-assignment swaps. Re-optimization runs every few minutes as flights go irregular, warm-starting from the current schedule for fast convergence.
What are the tradeoffs between RFID and barcode for baggage tracking?
Barcodes require line-of-sight and achieve 80u201385% tunnel read rates; RFID (passive UHF, ISO 18000-6C) reaches 98u201399% at conveyor speed without line-of-sight and supports bulk simultaneous reads. Tradeoffs: RFID tags cost u240.15u20130.25 each vs. near-zero for printed labels; RFID infrastructure is more expensive; metal environments cause RF interference. Most hub airports deploy hybrids u2014 barcode printing at check-in, RFID at high-throughput sortation points, barcode as fallback.
How are ground crew task dependencies modeled to achieve departure clearance?
Tasks (fueling, catering, cleaning, baggage loading, boarding, cargo door closure, technical inspection) are nodes in a directed acyclic graph (DAG); edges encode ordering constraints. A DAG executor monitors real-time task state from crew mobile devices and equipment telemetry, computes the critical path, and derives the Earliest Off-Block Time (EOBT). The revised EOBT is pushed to ATC and FIDS when delays occur. Pushback authorization is issued only when all DAG nodes reach COMPLETE.
How is a 5-second update SLA achieved for Flight Information Display Systems (FIDS)?
Operational systems publish change events to Kafka with sub-second latency. A FIDS aggregation service consumes events, updates Redis, and publishes display updates to a distribution topic. Display controllers subscribe via WebSocket or reliable multicast and apply updates immediately. End-to-end p99 latency is monitored via synthetic test events. On reconnect, controllers receive a full snapshot from Redis and switch to delta updates. Dual fiber paths and controller failover preserve the SLA during partial outages.
How does ACDM coordinate TOBT and ATOT slot management between airlines and ATC?
ACDM (EUROCONTROL framework) connects airlines, ground handlers, airport ops, and ATC around shared milestones. Airlines or ground handlers set and continuously revise the Target Off-Block Time (TOBT). The Network Manager assigns a Calculated Take-Off Time (CTOT) slot. The ACDM platform derives the Target Startup Approval Time (TSAT) = CTOT minus taxi time (EXOT) and issues it to the crew. Actual Take-Off Time (ATOT) is recorded at runway crossing and fed back to refine EXOT models. All milestones are exchanged via SWIM using FIXM or AIDX XML over secured IP.”
See also: Scale AI Interview Guide 2026: Data Infrastructure, RLHF Pipelines, and ML Engineering
See also: Uber Interview Guide 2026: Dispatch Systems, Geospatial Algorithms, and Marketplace Engineering