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

Preflight weather briefing

Flight Service

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

MVP Demonstrated

Flight Service takes the public weather sources a pilot already relies on and assembles them into one briefing built around a route rather than a phone number. What is live is live and says so; what is a placeholder is badged as a placeholder in the interface rather than buried in a footnote. It issues no go/no-go verdict and it is not an official Flight Service briefing — the pilot in command retains full responsibility for the decision.

Status 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.

Request a briefing walkthrough Read what is not built first
Illustrative Conditions along a route at altitude — a diagram, not live data.

The problem

The briefing is assembled by the pilot, from four places, under time pressure.

Surface weather is in one place, winds aloft in another, temporary flight restrictions on a separate website, and the phone briefing routes on the area code of the handset rather than the route being flown — so a pilot in Alaska calling from a Texas mobile number reaches a Texas station. None of these sources is wrong. The work of putting them together lands on the person with the least time to do it.

  • Winds and temperatures aloft arrive as a coded product that has to be decoded before it is useful.
  • Temporary flight restrictions live on their own site, so checking them is a separate act of discipline rather than part of the briefing.
  • A briefing that quietly mixes live data with placeholder content is more dangerous than one that admits the gap.

The answer

One route-shaped briefing, with the provenance of every section on its face.

The service fetches surface weather, winds and temperatures aloft, route-filtered adverse conditions and temporary flight restrictions from public sources, decodes them, and lays them out against the route and altitude actually being flown. Sections that are live say so. Sections that are placeholders are badged as placeholders in the interface, not disclosed in small print. AlbertAI phrases the assembled briefing when it is configured, and the deterministic formatter produces the same briefing when it is not.

What it does · 5 capabilities

The parts of Flight Service worth watching

Each capability below exists in the build described on this page. Anything planned rather than present appears under status, not here.

  1. Live surface weather and winds aloft

    Observations and forecasts come from the public aviation weather service with no credential required, and the winds and temperatures aloft product is decoded to standard levels up to FL390 and presented against the filed altitude rather than as raw code.

  2. Adverse conditions, filtered to the route

    Significant meteorological advisories, graphical airmen advisories and centre weather advisories come from the same public source and are filtered to a padded corridor around the route. The filter is deliberately permissive: showing an advisory that turns out to be off-route is an annoyance, hiding one that is on-route is a safety failure.

  3. Temporary flight restrictions in the briefing

    Active restrictions are fetched from the public list, with geometry pulled only for the few that survive a pre-filter — folding a separate website into the briefing. The pre-filter works by state, so a restriction just across a state line can be missed, and the interface says so rather than implying completeness.

  4. Takeoff and landing performance, behind a safety gate

    Performance figures are interpolated over the published pressure-altitude and temperature grid and are never extrapolated beyond it — outside the published envelope it reports that rather than inventing a number. Every table stays marked unusable until a human has checked it cell by cell against the aircraft flight manual, because publishing a wrong takeoff distance is not a display bug.

  5. Two implementations, cross-checked

    The decoder and formatter exist twice — once in the application, once in the deployed port — and a conformance test runs shared fixtures through both and fails on any disagreement. If one side is unavailable the test reports a skip and exits non-zero rather than passing quietly.

Boundaries

What it will not do, what it touches, and how it fails.

Three questions any operator should ask before an evaluation, answered before you have to ask them.

Human control Where the authority stays

Flight Service issues no go/no-go verdict, files nothing and activates nothing. It is an advisory assembly of public data, explicitly not an official Flight Service briefing and not a substitute for one. The pilot in command retains full responsibility for every flight safety decision, and the briefing says so on its face. Performance figures stay marked unusable until a person has verified the underlying table against the aircraft flight manual — the software will not lift that gate on its own.

Privacy boundary What it touches

The service holds no accounts and no personal data. Browser geolocation is requested and captured, but nothing in the current build depends on it — no output changes based on the reported position, and it is neither stored nor transmitted onward. Route and aircraft inputs are used for the briefing being generated and are not retained. Every upstream source is a public, unauthenticated feed.

Degraded mode When something is unavailable

Weather responses are cached for ten minutes, so a brief upstream outage degrades to slightly stale data with its timestamp visible rather than to nothing. With no model credential configured, AlbertAI synthesis is inactive and the deterministic formatter produces the briefing anyway — the credential adds phrasing, not content. Sections whose sources are not wired report as placeholders instead of rendering empty. The deployed host has no application runtime, so it runs a separate port of the same logic that the conformance test holds to identical output.

The same questions answered across the whole portfolio, with dates: trust & safety

Honest status · MVP

What is built — and what is not.

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.

Built and exercisable today

  • Live surface observations and forecasts from the public aviation weather service, cached and timestamped.
  • Live winds and temperatures aloft, decoded to standard levels up to FL390 and presented against the filed altitude.
  • Route-filtered adverse conditions — significant meteorological, graphical airmen and centre weather advisories — from the same public source.
  • Temporary flight restrictions from the public list, with geometry fetched only for candidates that survive a state pre-filter, and that pre-filter limitation stated in the interface.
  • Takeoff and landing performance interpolation that refuses to extrapolate beyond the published envelope and marks unverified tables unusable.
  • A conformance test that runs shared fixtures through both implementations and fails on any disagreement.

Not built — named, not hidden

  • Notices to airmen are placeholder strings, badged as such in the interface. There is no live notice integration — the official interface for it is access-gated.
  • Special use airspace is not queried at all. The interface reports it as not checked rather than implying it was cleared.
  • Geolocation is collected in the browser but no output depends on it. Treat the reported position as decoration until that changes.
  • Briefing synthesis by AlbertAI is implemented but inactive without configuration; the deterministic formatter is what runs by default.
  • No flight plan filing and no search-and-rescue activation. Filing is deliberately out of scope — the liability without an official integration is not acceptable.
  • No official status of any kind. This is not FAA Flight Service, is not approved or accepted by any authority, and is not a substitute for an official preflight briefing.
  • The self-hosted deployment path is written but has never been exercised. Treat those files as a proposal, not a runbook.

Claims and evidence

Every claim, at the tier its evidence supports.

If a claim below is worded more strongly than its basis justifies, it is a defect and we want to hear about it.

Flight Service — claims and their basis
Claim Tier Basis
Surface weather and winds and temperatures aloft come from live public sources, not fixtures. Demonstrated Public aviation weather service ingestion, no credential required; winds decoded to standard levels to FL390.
Adverse conditions and temporary flight restrictions are fetched from public sources and filtered to the route. Demonstrated Route-corridor filtering over the public advisory feed and the public restriction list. The restriction pre-filter is by state and can miss one just across a boundary — stated in the interface.
Performance figures are never extrapolated beyond the published data, and an unverified table is reported as unusable. Demonstrated Interpolation clamped to the published grid; a verified flag gates usability per table.
Both implementations of the decoder produce the same output, or the test suite fails. Demonstrated Shared-fixture conformance test across both ports; a missing runtime reports a skip and exits non-zero.
Notices to airmen and special use airspace are not live, and the interface says so. Concept Placeholder strings and a "not checked" label — named here and badged on the surface.
Routing a briefing by position rather than by telephone area code is the better model. Modeled Product argument from how the existing service routes callers. No comparative study has been run.

Fair questions

What people push back on — and the honest answer

These are the objections this product actually gets. None of them has a clever answer, which is why they are worth printing.

  • Is this a replacement for an official preflight briefing?

    No, and it must not be used as one. It is not FAA Flight Service, holds no approval or acceptance from any authority, and issues no go/no-go verdict. It assembles public data into one place, labels what is live and what is not, and leaves the decision — and the responsibility — with the pilot in command. Anything stronger would be a regulatory claim we do not have.

  • Your notices to airmen are placeholders. Why ship that at all?

    Because the alternative was to hide the gap. The section is badged as a placeholder in the interface, listed under what is not built on this page, and carried in the claim register at the CONCEPT tier. The official notice interface is access-gated, which is a real dependency rather than a coding task. A briefing tool that quietly renders placeholder content as though it were live is the actual danger; one that shows you exactly which section it cannot yet fill is usable with your eyes open.

  • Why would I trust computed takeoff and landing numbers from a website?

    You should not, until a person has verified the table. That is why the module marks every performance table unusable until someone has checked it cell by cell against the aircraft flight manual, and why the interpolation refuses to extrapolate past the published envelope rather than producing a plausible number. If you ever find a table presented as usable that has not been verified, that is a defect and we want the report.

Who buys this

Who Flight Service is built for

The operators whose problem this product is actually shaped around. Each has its own path from first contact to a decision.

Flight crews & pilots

The people the rest of this portfolio is ultimately about — pilots and cabin crew, whether flying a scheduled regional line, an on-demand charter leg, or a light aircraft on a private flight.

Part 135, charter & fractional

On-demand and fractional operators flying short-notice missions where the schedule is written the night before and rewritten in the morning.

Airports & FBOs

Airport operators and fixed-base operators responsible for the weather information that reaches pilots and operations staff on the ground.

Next step

Request a briefing walkthrough

Best judged on a route you actually fly. We open with the sections that are placeholders, because how a briefing tool handles the data it does not have tells you more than how it handles the data it does.

Request a briefing walkthrough