Terminal Weather Services SystemCurrent
UTC

Private technical preview / pilot access

Verify the feed.
Keep the evidence.

Evaluate how METAR messages reach your data pipeline, where source paths diverge and what timestamp evidence is available—before a feed becomes a production dependency.

Prepare a pilot request

Evaluation shape

A bounded technical pilot.

The purpose is to test collection, provenance and operational fit with a real upstream path. Commercial terms, data rights and implementation boundaries are agreed before licensed data is connected.

01 / COVERAGE

10–25 aerodromes

A configured European station set, with Madrid–Barajas and Stockholm Arlanda available as initial reference stations.

02 / DURATION

60–90 days

Long enough to inspect scheduled reports, corrections, missing observations and normal source-path variation.

03 / EVIDENCE

Exact TAC retained

Original representations, fingerprints and distinct observation, source and Terminal Weather timestamps.

04 / DELIVERY

Workspace first

A scoped operational view for station state, source evidence and investigation. API access remains a planned pilot option.

05 / SUCCESS

Measured criteria

Completeness, source-path freshness, revision handling, representation integrity and collector availability.

06 / BOUNDARY

Non-safety-critical

Analytics and infrastructure evaluation only. Not for navigation, pilot briefing, aircraft control or operational meteorology.

Evaluation plan

A decision at the end—not an open-ended trial.

The schedule is adapted to the upstream delivery method, but the evidence gates stay fixed. A 60-day evaluation covers the core observation period; days 61–90 are used only when a longer baseline or integration review is useful.

  1. 00 / BEFORE START

    Define the boundary

    Agree stations, data rights, message types, source-clock semantics, delivery cadence and written success criteria.

  2. 01 / DAYS 1–10

    Connect and verify

    Validate exact TAC capture, timestamp provenance, correction handling and source-failure behaviour.

  3. 02 / DAYS 11–60

    Observe the baseline

    Measure completeness, path freshness, revisions and content variants across the configured aerodromes.

  4. 03 / DAYS 61–90

    Review and decide

    Where required, extend the baseline, test the proposed integration and document findings against the agreed criteria.

Initial traffic assumptionMETAR and SPECI only · 10–25 aerodromes · event-driven delivery preferred · any polling interval and request cap agreed with the upstream provider before connection.

Request pilot access

Start with the pipeline you need to verify.

Tell us enough to determine whether the preview is a sensible fit. The request opens as an email on your device, so you can review it before sending.

Stage
Private technical preview
Budget fit
Focused paid evaluations; scope agreed before work begins
Reply from
Terminal Weather Services, Stockholm, Sweden

Evaluation brief

No account is created and this website does not store these entries. Submitting prepares a message addressed to the pilot team in your email application.

If your mail application does not open, send the same brief directly to pilot@terminalweather.com.