KBM Solved IT · Aviation Voice AI

The airport weather robot, finally human.

KBM AeroVox replaces the robotic weather voice every pilot hears with a clear, natural broadcast — generated live from the real observation, in any language, updated on the ATIS cycle.

Live real-time weather 4+ languages, native Any airport — towered or not Updates on the ATIS cycle Deterministic & auditable Deploys in days to weeks, not years

The AI is the voice, never the author.

Intended for

Designed for airports, aviation authorities, federal agencies, and defense innovation programs.

Pre-customer · Pilot program open
Built on
Render · AI voice synthesis engine · FastAPI · Cloudflare
Data sourced from
FAA · NWS · ICAO
Part of the KBM Nexus family
Albert 911 · Nexus Federal · KBM Solved IT
11
Airports modeled
TX · SD · Federal · Intl · Flagship
4
Native languages
EN · ES · FR · PT
FAA/NWS
Authoritative weather
METAR, live, every cycle
30min
Default re-voice cadence
Matches the ATIS cycle
0gen
Generative content
AI voices the script. It never writes it.
99.9%
Uptime target
Pilot SLA, pre-deployment
// Interactive demo
Hear it live
Pick a region, then an airport. You'll hear today's robotic broadcast, then the same real observation in the AeroVox voice.
// Why airports buy AeroVox
Designed for adoption, not disruption

AeroVox slots in next to the broadcast you already run. Same observation data, same ATIS cycle, same phraseology rules — delivered in a voice pilots actually want to listen to.

Reduce staffing burden

Broadcasts re-bake automatically on the ATIS cycle — every half hour by default, and on any special observation. No one re-records overnight, on weekends, or during a weather event.

Improve consistency

Every broadcast is generated by the same deterministic rule set — same phraseology, same unit conventions, same cadence. The AI is the voice, never the author, so output is auditable line-by-line.

Multilingual delivery

The same observation is spoken in English, Spanish, French, and Portuguese today — native phrasing, native voice, no translation lag. Serve international, military exchange, and flight-school traffic from one feed.

Keep existing procedures

AeroVox reads the same METAR the official broadcast already uses and follows your facility's phraseology. No workflow change for controllers, FBOs, or airport ops — it's the broadcast you have, in a better voice.

// Architecture
From observation to broadcast, in five auditable stages
  1. 01 · Ingest

    Live observation

    METAR pulled from FAA / NWS at the source. No human re-keying, no scraping intermediaries.

    INPUT: METAR TAF
  2. 02 · Parse

    Deterministic parse

    Raw observation decomposed into typed fields — wind, vis, ceiling, altimeter, remarks — with units normalized.

    OUTPUT: structured fields
  3. 03 · Phraseology

    Rules engine

    Fixed FAA-pattern templates compose the script. No model invention, no paraphrase — every clause maps to a field.

    RULESET: FAA / ICAO
  4. 04 · Render

    Per-language script

    Same structured fields rendered into English, Spanish, French, and Portuguese against locale-aware phraseology tables.

    EN · ES · FR · PT
  5. 05 · Voice

    Broadcast audio

    Neural voice reads the approved script at measured ATIS pace. Re-baked on the ATIS cycle (default 30 min).

    OUTPUT: .mp3 / stream

Every spoken word traces to a field in the authoritative observation. The AI is the voice, never the author.

// How it works
Real data in, clear voice out
1

Live observation

Pulls the airport's real, current METAR — the same data the official broadcast uses.

2

Deterministic engine

Converts to proper ATIS phraseology by fixed rules, in any language. The AI is the voice, never the author.

3

Natural voice

Speaks it in a clear human voice at a measured ATIS pace — updated on the cycle, like a real reissue.

// Deployment options
Deploy where you operate

Same deterministic engine, same voice quality, same multilingual coverage. Three operating models for three buyer realities.

Cloud Fastest to deploy

Managed AeroVox running in KBM infrastructure. We handle the METAR ingestion, the deterministic phraseology engine, the voice synthesis cache, and the broadcast endpoint.

  • ForRegional and municipal airports without on-site IT
  • IncludesHosted broadcast URL, SLA monitoring, 30-min re-bake cycle
  • Stand-upTarget: days from contract to first broadcast
On-premise Most control

AeroVox installed in your data center or private cloud. Your METAR feed, your network boundary, your retention policy. We deliver the container stack and the operations runbook.

  • ForAuthority-owned operations, large hub IT, hosted-tenant providers
  • IncludesContainer images, deterministic engine source-of-truth, audit logging hooks
  • Stand-upTarget: under 30 days with standard infrastructure
Air-gapped Highest assurance

Fully isolated install with no outbound network. Voice models, phraseology rules, and METAR ingestion all run inside the enclave. Designed for federal, military, and sovereign-AI requirements.

  • ForDoD ranges, federal facilities, allied program offices
  • IncludesOffline voice bundle, signed deterministic ruleset, reproducible build artifact
  • Stand-upScoped per accreditation path
Deploy as
☁ Cloud ⬛ On-Premise 🔒 Air-Gapped 🛡 Sovereign Infrastructure
Same deterministic phraseology engine across all four modes — the AI is the voice, never the author. Four-language native output, live re-bake on the ATIS cycle, auditable script trail per broadcast. Sovereign and air-gapped options are scoped per accreditation path; contact us for requirements. Operational reliability & security details →
// ROI calculator
Run the math on your airport

Adjust to your situation. All inputs are estimates. This is not a quote.

Re-record frequency 7 × / week
How often your team re-records or updates the AWOS broadcast (including after-hours calls)
Time per update 30 min
Includes re-record, coordination, after-hours phone-up, QA listen
Loaded hourly rate $55 / hr
Staff or contract rate including benefits burden. Part-time controller rates typically $40–$80/hr.
Languages needed 1 (English only)
AeroVox delivers EN · ES · FR · PT — each additional language is zero marginal labor
Estimated annual impact
Broadcast labor hours / year
Broadcast labor cost / year
Multilingual gap (languages not currently served)
Estimated AeroVox annual (indicative)

Indicative net position
Estimate only · figures derived from your inputs, not customer data. AeroVox has no completed pilots. Final pricing on quote. Labor offset assumes AeroVox eliminates manual re-record burden; AWOS hardware maintenance costs not included.
What the calculator doesn't capture
  • Intelligibility on first listen — fewer "say again" calls and FBO phone-ups
  • 24/7 coverage with no overnight body in the seat
  • Deterministic phraseology — every word auditable to a METAR field
// First-deployment program
Q3 2026 cohort — design partners

We are taking a small number of first-deployment partners. You get the engineering attention of a pre-product-market-fit team; we get the operational data to prove the case.

What's included
  • Integration with your existing AWOS / ASOS / METAR feed
  • Voice tuning & phraseology pass against your local conventions
  • Up to four languages on the same broadcast cycle
  • 30 / 60 / 90‑day operational review with our team
  • Direct line to engineering — not a ticket queue
Who we're looking for
  • GA, regional, or part-141 airport — towered or non-towered
  • Or: military / federal program office evaluating multilingual ATIS
  • A named operational owner (airport manager, ATM, ops chief)
  • Willingness to share anonymized operational feedback
Pricing framing

Pilot fee covers integration and the 90‑day evaluation. Fully credited against year-one contract if you convert. Walk-away at day 90 with no obligation. Written terms before any signature.

Request a briefing → Cohort size: small · Reply within 2 business days
Pre-customer · AeroVox is open for first deployments. The 11 airports on this demo are live broadcasts on real weather, not customer installations.
// The communications gap
Aviation became digital. The voice didn't.
1990s – 2000s Aircraft avionics and cockpit systems Modernized
2000s – 2010s Navigation — GPS, RNAV, RNP approaches Modernized
2010s – 2020s Weather data feeds, SWIM, ADS-B Modernized
2010s – 2020s Airport operations — FIDS, gate management, biometrics Modernized
1970s – today AWOS / ASOS weather broadcasts — the voice pilots copy from Unchanged
The data is live.
The weather sensors are live.
The voice is 30 years old.

Every other layer of the aviation information stack has been digitized, automated, and modernized. METAR data flows in real time from sensors to cockpits. Aircraft know their exact position to the meter. Passengers check gate status on their phones.

But the broadcast a pilot copies — the voice that tells them wind, visibility, ceiling, altimeter — is still produced by a system designed in the 1970s, voiced by a machine that sounds like it. At most airports, that broadcast was last re-recorded whenever someone remembered to do it.

AeroVox is the first step toward closing that gap. Not just a better voice — a modern aviation communications layer that treats the spoken broadcast as data, not a recording.

// Platform roadmap
Voice today. Platform tomorrow.

ATIS-style weather is the wedge, not the ceiling. AeroVox is being built as an airport communications platform — the same deterministic engine, the same multilingual voice layer, applied to every spoken broadcast a field generates. Voice is the feature. Operational automation is the business.

Available today Module 01

ATIS-style weather voice

Live METAR → deterministic FAA / ICAO phraseology → native voice in four languages → broadcast on the ATIS cycle. Eleven airports modeled, on real weather, in the demo above.

  • SourceFAA / NWS METAR · live, every cycle
  • OutputEN · ES · FR · PT · native phraseology, native voice
  • CadenceRe-baked on the ATIS cycle · default 30 min
  • DeployCloud, on-prem, or air-gapped · pilots open
The AI is the voice, never the author.
Module 02 Roadmap

NOTAM narration

Read field NOTAMs aloud on demand, in any of the supported languages. Same deterministic phraseology approach — the model voices the authoritative NOTAM text, never paraphrases it.

Module 03 Roadmap

Runway condition narration

Spoken RCR / runway contamination / braking action reports built from the existing surface observation, in the same voice and cadence as the weather broadcast.

Module 04 Roadmap

Operational alerts

Bird activity, equipment outages, special-event advisories — voiced from the operations log against a controlled alert vocabulary, not free-form generation.

Module 05 Roadmap

Airport information broadcasts

Non-METAR field information — fuel availability, FBO status, customs hours, after-hours contact — in the same multilingual voice layer as ATIS.

Module 06 Roadmap

Multilingual passenger advisories

Terminal-side announcements in N languages from the same engine that voices the airside broadcast. One source of truth — airside and landside — one voice identity.

Part of the KBM Nexus operational-intelligence family. Roadmap items above are not shipping today · no completed pilots · sequencing follows first-customer demand.

// Why now
Four forces converging in 2025 – 2027

AeroVox isn't early. The infrastructure is ready, the pain is documented, and the pressure on airports is accelerating. Here's what's changed.

Force 01
Neural voice synthesis reached parity

A natural-sounding voice indistinguishable from a human controller was not technically feasible at scale until 2022–2023. The voice models that power AeroVox did not exist five years ago. The same quality that required a professional recording studio now runs deterministically on commodity cloud infrastructure, on-demand, in any language.

The technology gate is open. Now.
Force 02
Airport staffing pressure is structural

The post-pandemic aviation labor market is tight across every function. Small and regional airports are operating leaner than at any point in the last decade. Manual broadcast re-recording — an after-thought task in well-staffed operations — is now genuinely burdensome. The constituency for automating it has never been larger.

GA airport staff vacancy rates ~18% above 2019 levels.
Force 03
International passenger traffic is growing

Approximately 25% of U.S. commercial passenger volume involves non-native English speakers — and that share is rising at regional airports with growing international charter, military exchange, and flight-school populations. English-only AWOS was adequate when international traffic was rare. It is no longer adequate.

~25% of U.S. passengers non-native English speakers.
Force 04
Modernization mandates are arriving

FAA's NextGen program, the DOT's digital infrastructure agenda, and state aviation modernization funds are directing capital toward exactly this problem. Defense innovation programs (AFWERX, DIU) are actively evaluating AI-augmented voice systems for airfield operations. The procurement pathway is open for the first time.

FAA NextGen + state modernization funds actively deployed.
The question airports will face in the next 24 months isn't whether to modernize. It's which vendor becomes the standard they adopt. AeroVox exists to answer that question first.
// Common questions
Questions we hear from airport directors
Short, direct answers. For anything specific to your facility, request a briefing.
How much does it cost?
Pricing depends on number of airports, language coverage, and deployment model. Pilots start in the low five figures; multi-airport subscriptions scale from there. There is no per-broadcast metering. Contact us for a fitted quote.
How difficult is deployment?
Software-defined. Days, not months. At airports already running AWOS, ASOS, or SWIM, we integrate with the existing observation feed — no new weather hardware required. The deterministic engine and voice layer run remotely; the broadcast is delivered into the existing audio chain.
How long does a typical deployment take?
Target timeline for a single-airport pilot is two to four weeks from signed agreement to first on-air broadcast. Most of that window is integration testing and language QA; the engine itself is operational on day one.
What happens if internet connectivity fails?
The existing AWOS or ATIS source remains the authoritative fallback throughout — AeroVox never displaces the official broadcast path. A local cache and edge-deployment option are on the roadmap for environments that require offline resilience; the current managed-service tier is cloud-hosted with Cloudflare CDN.
Who maintains it?
Fully managed by KBM Solved IT under a service agreement. Monitoring, engine updates, voice model refreshes, and additional language packs are included. On-site staff training is available as an option.
Is FAA approval required?
Phased. For non-towered AWOS voice modernization, the existing observation source and authority chain are unchanged — no new approval is required. For full ATIS modernization at towered fields, we work alongside the FAA during the pilot phase. Military and international deployments follow the equivalent local authority process.
What weather data sources do you use?
The airport's own observation. In the US that is FAA / NWS METAR pulled directly from the same feeds the official broadcast uses. Internationally, the local ICAO METAR source. The data in, and the data out, are the same — only the voice changes.
Does it require new hardware at the airport?
None for the standard managed-service tier. For air-gapped, on-prem, or military-restricted environments, an edge-deployment configuration is on the roadmap — contact us to discuss requirements for your accreditation path.
Can we hear it on our own airport before signing anything?
Yes — and you can do it self-serve in about 10 seconds. Enter your airport's ICAO code on our sample broadcast page and pick a language. We pull the current real METAR, run it through the same deterministic engine that powers the live demo, and bake a broadcast in the AeroVox voice. The audio is for your evaluation only — it does not touch your live frequency. If you'd prefer the audio delivered by email with our cohort-lead context attached, request it on the briefing form instead.
Something we didn't cover? Send us the question directly.