SDVOSB — Service-Disabled Veteran-Owned Small Business Ret. USAF F-15C pilot · 22-year veteran A KBM Solved IT company

Decision support for regional airlines & Part 135 operators

Earlier signals.
Human decisions.
Complete records.

KBM Air builds human-governed, auditable decision support for the operators the enterprise vendors price out — disruption recovery, dispatch workflows, and a decision record that survives review.

Nothing here flies the aeroplane and nothing here predicts the future. It surfaces the constraint earlier, shows the reasoning, and keeps the account of what your people decided and why.

Also known as “See what happens next — before it does.”

Illustrative night operations workspace with weather contours, route paths, and one amber priority signal
Illustrative Earlier signals across a connected operation.

What that actually means

Three claims, and the mechanism behind each one.

A positioning line is worth nothing if it does not name something in the software. Each of these does.

  1. Earlier signals

    The board is re-sorted by risk rather than by departure time, with the drivers behind every score named. Nothing here predicts — it is arithmetic over records you already hold, run early enough to matter.

    Deterministic scoring. Same inputs, same score, every time.

  2. Human decisions

    Nothing releases an aircraft, files a flight plan, publishes a briefing or rebooks a passenger. The software does the legwork and shows its reasoning; a qualified person decides, and the approval is recorded as a human act.

    Approval gating enforced in the engine, not added at the interface.

  3. Complete records

    Every advisory decision is written into a chained, signed record — who decided, when, and on what basis. A record altered afterwards fails verification, and the interface will show you that failure on purpose.

    Tamper-evident by construction. Verify it, then try to break it.

The problem

Airlines do not lose money on delays.
They lose money on surprises.

Every operation already holds the data that would have shown the disruption forming. What it lacks is the moment of warning — the constraint surfaced early enough to change the outcome. That gap is where the cost lives.

What operations tooling does today

  • Sort the board by scheduled departure
  • Record the disruption once it has happened
  • Explain yesterday accurately and tomorrow not at all
  • Leave the reasoning in a phone call

What KBM Air is built to do

  • Sort the board by risk, with the drivers named
  • Surface the constraint while the options are still cheap
  • Answer forward-looking questions from the same records
  • Write the decision, the person and the reasoning to a verifiable record

The portfolio

One operational core. seven places it lands.

From the dispatcher's desk to the executive floor to the passenger's phone — the same records and the same rules, applied where each decision actually gets made. Every product carries its real maturity, not its ambition.

Illustrative connected aviation operations ecosystem with eight decision-support modules around a shared operational core
Illustrative Eight operational contexts, connected by one human-governed decision core.

Nexus Dispatch

Operations control centre

Maturity:Pilot-ready

The flight that is about to break is already on the board. It is just not near the top.

A risk-sorted flight queue that scores every flight 0–100 and names the drivers — weather, crew, maintenance, ATC — so dispatchers see the constraint while there is still time, and every decision they make lands in a record that survives review.

  • 0–100 risk score per flight, with the drivers named
  • Recovery options compared against doing nothing
  • Analyst answers sourced to records, never generated
  • Tamper-evident decision record on every advisory action

Evidence tier:Demonstrated

Airline Operations Intelligence

Network & executive operations

Maturity:Prototype

Dispatchers manage flights. Leadership manages a network — usually from a report about yesterday.

The network-level view over the same operational core: traffic-management impact, forward deviation risk scored deterministically, plain-language questions answered from named records, and a decision trail a reviewer can verify rather than trust.

  • Plain-language questions answered from named source records
  • Traffic-management advisory → predicted impact → sequenced options
  • Two-hour forward deviation risk, scored deterministically
  • Verifiable decision trail built for procurement review

Evidence tier:Demonstrated

Rebound

Disruption & passenger recovery

Maturity:MVP

Legacy systems find a seat. Recovery means rebuilding the journey.

An irregular-operations reaccommodation engine that solves an entire disrupted manifest at once — priority, itinerary, duty of care and finite seats — and hands an agent a ranked plan per passenger with a written reason on every decision. Advisory tier, deterministic synthetic data, no live reservation system.

  • Whole manifest solved in parallel, not one passenger at a time
  • Own metal → interline partner → nearby airport with ground transfer
  • Duty of care applied by cause, so care is authorised only when owed
  • Finite hotel, transport and meal budgets allocated by priority

Evidence tier:Demonstrated

AeroVox

Weather communications & briefing distribution

Maturity:MVP

The observation is accurate. The briefing built from it should be too — word for word, every time.

A deterministic weather-communications layer: an authoritative observation rendered into standard phraseology by explicit rules, published as text and clear multilingual audio for briefing channels, with a human reviewing before anything is distributed.

  • Same observation in, same words out — every time, traceable to a field
  • Standard phraseology generated by rules, never by a language model
  • Four languages, each rendered natively from one neutral observation
  • Transcript published beside the audio so a reviewer can check it

Evidence tier:Demonstrated

Flight Service

Preflight weather briefing

Maturity:MVP

Flight Service routes a briefing by the area code of the phone you are calling from, not by where you are flying.

A preflight briefing that pulls live public surface weather, winds and temperatures aloft, route-filtered adverse conditions and temporary flight restrictions into one place — with every section labelled live or placeholder on the surface. Advisory only, and not an official briefing.

  • Live public surface weather and winds/temps aloft to FL390
  • Adverse conditions filtered to the route, biased toward showing too much
  • Takeoff and landing performance behind a hard safety gate
  • Every section badged live or placeholder, on the surface

Evidence tier:Demonstrated

CREW Downtime

Crew layover support

Maturity:Concept

A nine-hour overnight and a twenty-two-hour layover are not the same trip.

A designed — not built — layover companion for airline crew: a profile it already knows, a position it reads automatically, a clock it respects, and an interpreter for the times the crew member does not speak the language. Nothing has been demonstrated.

  • Designed: a profile captured once, applied on every layover
  • Designed: position read automatically, no city picker
  • Designed: everything filtered by arrival time and time remaining
  • Designed: two-way voice interpreter and camera sign translation

Evidence tier:Concept

Universal Flight Companion

Traveller decision support

Maturity:Prototype

Nobody loses sleep because they cannot see their aircraft.

A clickable prototype of a passenger-side assistant that explains what is happening to a trip and what to do about it — connection risk, delay causes, and an assistant that states its uncertainty and never acts on its own.

  • Connection risk scored, with the levers that change it
  • Delay explained by cause, not just reported as a time
  • Source, freshness and confidence on every panel
  • A watcher view for the person doing the airport pickup

Evidence tier:Concept

Compare all seven side by side →

The platform

Not seven tools. One operational core.

Every product sits on the same foundation, which is why a risk driver on a dispatcher's screen and a figure on an executive dashboard mean the same thing.

Sourced, never asserted

Every fact a KBM Air product surfaces is traceable to the record it came from — an observation, a crew state, a maintenance entry, an advisory. The analyst layer explains risk; it does not invent it.

Deterministic where it counts

Safety-relevant text and safety-relevant scoring are produced by explicit rules, not by generative models. The same inputs produce the same output, every time, and every phrase traces to a field.

Human decision, machine legwork

No KBM Air product takes a safety-relevant action. Aircraft release, flight-plan filing, broadcast transmission and passenger rebooking all require a qualified human, and the approval is recorded as a human act.

How the platform is built →

Who it is for

Built for the operators legacy vendors skip.

Regional carriers and Part 135 operators carry the same regulatory weight and the same disruption physics as a major, on a fraction of the staff. That is a product problem, not a discount problem.

Proof, at its real tier

Every claim on this site is worded at the evidence behind it.

No customer logo proves a platform works; software you can sit down and exercise does. Here is exactly where each product stands today — including the parts that are not built.

Product maturity and evidence tier
Product Maturity Evidence Where it actually stands
Nexus Dispatch Maturity:Pilot-ready Evidence tier:Demonstrated Working demonstration surface over a working engine, running on seeded and public data. No airline is operating it.
Airline Operations Intelligence Maturity:Prototype Evidence tier:Demonstrated Prototype surface built to industry-standard operational reporting schemas, running as a labelled simulation. No live data feed, no partner relationship.
Rebound Maturity:MVP Evidence tier:Demonstrated MVP at the advisory tier on deterministic synthetic data. It proposes; an agent approves. It neither connects to nor writes to any live passenger service or distribution system.
AeroVox Maturity:MVP Evidence tier:Demonstrated Working proof of concept on live public weather data — thirteen airports, four languages. Not an ATIS or AWOS replacement, not connected to any transmitter, and not certified for operational use.
Flight Service Maturity:MVP Evidence tier:Demonstrated MVP with live public weather. Notices to airmen are placeholder strings and special use airspace is not queried — both badged on the surface. Not an official briefing.
CREW Downtime Maturity:Concept Evidence tier:Concept Concept and scaffold only. Nothing has been built or demonstrated — every capability on this page is design intent.
Universal Flight Companion Maturity:Prototype Evidence tier:Concept Phase-zero clickable prototype on mock data. No live flight feed, no accounts, no backend. The prototype labels itself as mock data on every screen.

The full evidence framework → Trust & safety, dated →

Next step

See it run against your operation's reality.

Tell us what you operate and what keeps surprising you. Forty minutes, driven live on synthetic or public data, ending with what would have to be true for this to work where you are. We reply within two business days with an agenda, not a brochure.

Request a walkthrough

Or write directly to air@kbmsolvedit.net.