Inspect the existing AI-ATC runtime and configured Ollama requirements. Integrate AI-ATC as an optional profile capability. Start gate Do not start AI-ATC merely because RadioBridge's process is active. Wait for RadioBridge to report the simulator adapter connected and audio/PTT usable, with its gateway and the profile-required client(s) available. Also verify the configured Ollama service/model. RadioBridge owns the radio/audio/device readiness contract. Cockpit Manager consumes that contract without implementing PTT, audio routing, radio protocol or device logic. Qualification DA62/MSFS is the initial RadioBridge integration candidate. The handheld-radio review identifies an X-Plane 11 adapter, not confirmed XP12/Phenom support. Treat the RadioBridge-dependent XP12/Phenom AI-ATC path as unqualified until separately tested. Acceptance Missing simulator, gateway, required client, usable audio/PTT or Ollama dependencies prevent startup and show a clear reason. Test a connected but wrong client as well as a missing client. Specify behavior when readiness is lost after startup. Stopping respects process ownership. Refer detailed ATC behavior changes to the existing AI ATC design project. Static audit baseline (knowledge item 117) AI-ATC is Python 3.12 version 0.1.4 with /api/status on HTTP 8765. Current scenarios and acceptance tests are MSFS-oriented; only MSFS is practically tested. Ollama is local HTTP 11434. Availability of /api/status is not proof of full radio readiness. New orchestration follows the read-only preflight and the RadioBridge readiness contract.
.png?locale=nl)
05 - AI-ATC
Optional local ATC runtime, Ollama dependency and coordination with RadioBridge.
Kennis
1 itemSource: user-supplied cockpit inventory and handheld-radio Codex review, 18 September 2026. Baseline AI-ATC is an optional local runtime started with start-ai-atc.cmd. Ollama must be active locally for interpretation. The initial inventory listed AI-ATC in MSFS and X-Plane startup procedures. The more specific handheld-radio review found an X-Plane 11 adapter and no confirmed XP12/Phenom RadioBridge qualification. Do not present the RadioBridge-dependent XP12/Phenom AI-ATC path as supported until it is verified end to end. Startup dependency contract AI-ATC may start only after RadioBridge reports its simulator adapter connected and audio/PTT usable, with the gateway and required audio clients available. Process running is insufficient. Check the configured Ollama service/model as well. RadioBridge owns and reports radio/audio/device readiness; Cockpit Manager coordinates startup and displays status without duplicating radio protocol, PTT or audio-routing logic. Client readiness must respect the session profile: a connected fixed radio does not substitute for a required handheld. Define exact status transport and schema after inspecting existing code. Scope boundary This umbrella project covers lifecycle, dependencies and integration. Detailed ATC behavior belongs in the existing AI ATC design project. Keep failure reasons visible and do not report readiness based solely on script launch.