Airport-Slot and Turnaround Platform Recovery Leader — Hub Operations

The mandate

During weather recovery, scheduled movement, revised slot, aircraft readiness, stand occupancy and handler milestone states diverged across the collaborative operating platform. Controllers maintained safe movement through established channels, but airlines received inconsistent departure expectations and several stand decisions required manual reconstruction. The platform executive resigned after the review challenged whether shared timestamps represented observation, estimate or accountable commitment.

The interim starts within two weeks for ten months and owns state reconciliation, recovery sequencing, winter and summer peak exercises, and permanent-leader induction. Recruitment opens after a sixty-day common-clock baseline. Six weeks of overlap are protected; the fixed term will not stretch to accommodate terminal expansion, airline commercial disputes or optional passenger-experience products.

Successful handover means every priority turn resolves scheduled, estimated, target, acknowledged and actual states across aircraft, flight, slot, stand, gate, service milestone and constraint. Two unseen disruption exercises must be commanded by the successor, and airline, handler and airport owners must reproduce decision history without personal message trails. Residual surveillance, partner-interface and legacy-airline debt will be explicitly accepted.

The leader may freeze platform releases, quarantine unreliable estimates, mandate event acknowledgement, direct the approved ₩62 billion recovery and appoint temporary control owners. Actual aircraft movement, air-traffic decisions, airline dispatch, security intervention, permanent hiring and spending beyond authority remain with authorised organisations. The platform seat cannot allocate operational safety accountability by software configuration.

Fleet scheduling, airport-capacity expansion and replacement of certified airfield or baggage control systems are excluded. The interim can require dependable interfaces and continuity evidence but will not renegotiate airport charges, handler contracts unrelated to data duty or airline schedules. Recovery is bounded to shared operational truth and decision cadence across the existing hub ecosystem.

Why this seat is open

The disruption revealed an enterprise platform problem without weakening the formal operational authorities that kept the airport safe. Its executive owner then left, and peak seasons cannot wait for recruitment. A time-bounded leader can restore credible coordination evidence while preserving air-navigation, airport, airline and handler accountability for the choices themselves.

What you will own

• Reconstruct affected turns across schedule, slot revision, inbound estimate, stand, gate, aircraft readiness, handler milestone and actual movement.
• Define each event as observation, forecast, target, commitment, acknowledgement or actual, with source clock and permissible correction.
• Decide which estimates may republish automatically, require accountable confirmation, need qualification or remain suppressed during recovery.
• Command exercises covering weather compression, late inbound, stand conflict, handler delay, gate change and missing partner feed.
• Establish continuity boards and low-bandwidth partner paths that preserve one decision record when the collaborative platform degrades.
• Govern work against reconciled turns, estimate stability, reduced voice reconstruction, partner acknowledgement and recovery-time evidence.
• Transfer command through two peak exercises and successor acceptance of surveillance, interface and participating-airline limitations.

Candidate qualifications

• Held executive airport collaborative-decision, operations-control or airline-turnaround platform authority at a high-volume international hub.
• Reconciled slot, movement, stand and servicing events across airport, airline, handler and air-navigation systems during material disruption.
• Distinguished forecast, target, operational commitment and observed actual when incompatible clocks drove consequential resource decisions.
• Commanded weather, capacity or partner-outage recovery without appropriating air-traffic, dispatch, security or ramp safety authority.
• Governed multi-party improvement where participants had unequal data maturity, incentives and contractual duties to acknowledge change.
• Handed a recovered hub platform to permanent leadership through live peak operations and adversarial disruption exercises.

Non-negotiables

• Available within two weeks for exclusive Seoul hub service, including overnight command during declared operational disruption.
• Has led a live airport or airline collaborative operating environment; generic travel technology leadership is insufficient.
• No undisclosed airline, handler, airport-platform or systems-integrator interest affecting the recovery perimeter.
• Will preserve regulated operational authority and partner evidence even when a simpler central platform decision appears faster.

1. 49 words maximum. State your Seoul availability and one airport disruption where target and actual operational states diverged.
2. 49 words maximum. How did you establish a common decision clock without overriding airline or air-navigation authority?
3. 49 words maximum. Which unseen partner-feed failure would qualify the permanent leader before your departure?