What is VibePilot ATC?

The core idea

Most ATC simulation begins by scripting controller behavior: assigning phraseology, building trigger conditions, simulating radio exchange. The result resembles aviation. VibePilot does not begin there.

Before any instruction is issued, something must already be true: the controller must know where the aircraft is, what surface it occupies, and whether that surface is clear, contested, or in transition. Without that knowledge, controller speech is not simulation — it is theater.

VibePilot builds spatial certainty layer by layer. ATC authority emerges only after the geometry beneath it is stable. No runway is hardcoded. No condition is triggered. Runway identity and clearance decisions follow entirely from measurable spatial constraints.

How it works — the signal pipeline

The system processes live aircraft telemetry at 1Hz through a seven-layer architecture. Each layer transforms data into a richer form of spatial understanding before passing it upward. No layer activates before the one beneath it is stable.

A concrete example — final approach at LSZH Runway 28:

• [IN] — Raw telemetry: lat=47.4481, lon=8.6649, hdg=278°, gs=138kt, alt=2920ft, vs=−720fpm
• [GEO] — Geometry resolved: distToThreshold=4.8nm, xTrack=−12m, headingDelta=0.8°, aligned=RWY28, candidates 38→6
• [RIS] — Intent derived: phase=FINAL_APPROACH, corridor=VALID, stableApproach=true, lateralConf=0.94, runway=28
• [OUT] — ATC decision: assignedRunway=28, intent=LANDING, clearance=AWAITING→Tower, touchdown ~122s

No runway was hardcoded. No condition was triggered. The clearance follows from the geometry.

The seven architecture layers

VibePilot's architecture is structured as seven sequential layers. The first five are operational. Layer six is in active development. Layer seven is planned.

• Layer 01 — Simulator Intake (Operational): Receives UDP socket payloads from X-Plane, validates and normalises raw telemetry into internal field names via NetworkService and XPlaneMetadataBridge.
• Layer 02 — Aircraft State Construction (Operational): Constructs a stable, continuous aircraft state object from normalised telemetry, preserving previous sample for delta calculations (deltaTime, previousPosition, track).
• Layer 03 — Geometry Core (Operational): Converts aircraft state into runway-relative geometry. Computes cross-track error, along-track distance, bearing to threshold, heading delta, and runway alignment using GeoMath, GeoCalculator, MagneticModel, and RunwayHeadingResolver.
• Layer 04 — Reference Dataset (Operational): Persistent runway reference layer. Parses X-Plane apt.dat data into 47,824 airports and 75,000+ runways via AptDatLoader and RunwayRepository, with fast spatial lookup via AirportSpatialIndex. Feeds Layers 03 and 05 continuously.
• Layer 05 — RISEngine: Runway Intelligence (Operational): Converts geometry into runway intent. Orchestrates RunwayPhaseResolver, ApproachCorridorDetector, RunwayLateralDetector, ApproachStabilityMonitor, and RunwayIntentPredictor. Emits RunwayIntentState with assigned runway, flight phase, lateral confidence, and occupancy prediction.
• Layer 06 — Surface Interpretation (In Development): Extends runway intelligence into ground operations. Parallel surface detectors (LineupDetector, RunwayCrossingDetector, BacktrackDetector, DepartureRollDetector) resolved under SurfaceIntentResolver.
• Layer 07 — ATC Controller Decision (Planned): Controller roles (GroundController, TowerController, ApproachController) deriving clearances after spatial certainty is established. Includes PhraseologyLayer and VoiceRenderer converting decisions into standard ATC language and voice output.

The five design principles

VibePilot is governed by five principles that define when the system earns the right to act. They are ordered deliberately — each principle earns the next.

• Spatial Truth Precedes Speech. No instruction is issued until the aircraft's geometric position is verified and held. Controller voice is consequence, not cause.
• Authority Rises in Layers. Telemetry becomes state. State becomes geometry. Geometry becomes judgment. No layer assumes authority before the one beneath it has earned trust.
• Context Certainty Precedes Authority. Knowing where an aircraft is and knowing what that position means are different questions. Controller logic cannot engage until both are resolved.
• Determinism Governs Trust. The same inputs must always produce the same spatial truth. Repeatability is not optimisation — it is the condition under which everything else holds.
• Realism Licenses Expansion. VibePilot does not expand by accumulation but by proof. Each new layer is permitted only after the one beneath it has demonstrated it can carry operational weight.

Current development status

VibePilot is in early active development. The geometry core and runway intelligence engine (Layers 01–05) are operational and continuously validated. Surface Interpretation (Layer 06) is currently being validated — specifically lineup, crossing, backtrack, and departure roll detection.

The ATC controller decision and voice output layer (Layer 07) is planned for after lower layers demonstrate stable operational weight. Updates are issued only when the system meaningfully evolves, not on a fixed schedule.

X-Plane 12 is the first target platform. MSFS support follows after core maturity.

How VibePilot compares to existing ATC tools

Supported platforms and availability

VibePilot ATC targets Windows as its first operating environment. X-Plane 12 is the first supported simulator, connected via UDP telemetry. Microsoft Flight Simulator (MSFS) is planned for after core system maturity.

The project is in independent development and a waitlist is open at flyvibepilot.com for updates when the system meaningfully evolves.

Further reading

• System Architecture — full seven-layer breakdown with component details
• Design Principles — the five conditions under which VibePilot earns the right to act
• Live Terminal — signal trace and layer resolution monitor
• Overview — homepage with core logic demonstration