Check any route. Decide.
Keep the proof.
The Console is a signed-in workspace on the FlySafe scoring engine: score any route for any date, record your decision with a rationale, and walk away with a dated, referenced, verifiable record — for the trip file, the audit, the quote file, the board pack.
No integration, no procurement call — it runs in the browser on the same engine the API serves.
Free for 14 days — the full Console, no card, no plan choice up front. Then Solo $99/month (one seat) or Team $399/month (five seats, shared journal). Compare plans →
What a seat buys.
Everything below ships on both plans — Team adds seats and the shared journal.
Origin–destination with up to 3 via-stopovers, each leg scored separately. Departure dates up to 30 days out, with the “today vs your date” delta shown side by side.
Every saved check gets a reference (FS-RRA-…), a UTC timestamp, the author, your decision — reviewed / proceeding / not proceeding — and a written rationale. Proceeding on an elevated-risk route requires one.
Printable PDF with the full per-FIR basis and cited sources; CSV named by reference for the file or the filing. The document states what it is: an index input, not operational advice.
Each record carries an authenticity link anyone can open — no account, no login. Hand the PDF to a client, broker, or auditor; the link answers years later, subscription or not.
Pin the FIRs and routes you care about — the Console emails you when a risk level changes, never score noise. Trip watches expire after the trip date on their own.
Paste a book — aircraft, airport, limit — and peak exposure aggregates per airport with current risk attached, plus the CSV for the War & NCBR return.
The record, block by block.
This is what a check becomes when you save it — scroll through the actual artifact.
Route airspace-risk report
Route ZRH→DXB carries a risk index of 64 / 100 — HIGH band. A lower-risk reroute is available (see §2). Highest exposure at OIIX (78).
| # | FIR | Name | CC | Score | Level |
|---|---|---|---|---|---|
| ZRH | origin · departure | — | — | ||
| 1 | LSAS | Switzerland | CH | 12 | low |
| 2 | LIRR | Rome | IT | 11 | low |
| 3 | LGGG | Athens | GR | 24 | low |
| 4 | HECC | Cairo Official NOTAM | EG | 41 | moderate |
| 5 | OEJD | Jeddah Official NOTAMTraffic anomaly | SA | 38 | moderate |
| 6 | OIIX | Tehran Regulator bulletinGPS jammingConflict activity | IR | 78 | high |
| 7 | OMAE | Emirates Official NOTAM | AE | 31 | moderate |
| DXB | destination · arrival | — | — |
2,551 nm direct routing. A lower-risk reroute is available via LGGG → HECC → OEJD (+6% distance, max FIR risk 41) — avoids OIIX entirely.
- FACTOverflight restriction — several Western-registered carriers restricted in OIIX. since 2024-04 · source ↗
- FACTEASA advisory — Conflict Zone Information Bulletin, Tehran FIR · do not fly below FL320 CZIB-2026-04 · publ. 2026-05-12 · EASA ↗
- FACTActive NOTAMs — 14 active on route: OIIX (6) · OEJD (4) · HECC (3) · OMAE (1). Issuer text below; “notable” is our classifier, not the issuer’s grading.A0231/26 NOTAMN Q) OMAE/QRTCA/IV/BO/W/000/999/ A) OMAE B) 2607141200 C) 2607282359 E) RESTRICTED AREA ACTIVE. AIRSPACE CLSD BLW FL140 WI 25NM…
- OBSERVEDFlySafe monitoring — 2 FIRs with a higher-than-usual share of low position-accuracy (NACp) reports. Our own inference from ADS-B / telemetry — no cause implied, not an external report.
Data as of 2026-07-18. NOTAMs current to 2026-07-18. “FlySafe monitoring” items are inferences from telemetry, not external sources.
- [a] Bilateral overflight registry — FlySafe curated
- [b] EASA Conflict Zone Information Bulletins
- [c] FAA & national NOTAM offices
- [d] USGS earthquake feed · FlySafe ADS-B monitoring
Proceeding (documented) — southern routing via HECC → OEJD avoids the elevated segment; PIC briefed, owner informed.
An index with its uncertainty attached
0–100 with band, confidence, coverage tier and the trend to the chosen date — recomputed continuously from 30+ public sources across 341 FIRs. An input to your decision, never a verdict.
Every FIR on the route, signal by signal
The full corridor with per-FIR scores and signal tags — and when a lower-risk routing exists, the report names it: via which FIRs, at what detour cost, avoiding what.
Sources, dated and cited — not “trust us”
Citations behind every elevated FIR: regulator bulletin references, raw NOTAM text, restriction registries — with our own telemetry marked separately as OBSERVED. Facts and inferences never blur.
Who decided, on what basis, when
Your decision with a written rationale, name and UTC timestamp. Recording “proceeding” on an elevated-risk route requires the rationale — that discipline is what makes the journal a process.
Verifiable by anyone you hand it to
Every saved record carries a public authenticity link — a client, a broker, an auditor opens it without an account, years later, subscription or not.
Solo $99/mo · Team $399/mo · no card · first record in ~10 minutes
Built to be questioned.
- → 341 FIRs scored daily from public regulatory & operational data — EASA · FAA · ICAO · ADS-B · conflict-event signals
- → Dated citations per elevated FIR inside every record — facts and inferences marked apart
- → Published methodology; Brier / ECE calibration quarterly
- × A verdict. The index informs; the operator, underwriter, or manager decides — and the record documents that judgment.
- × A replacement for official sources. NOTAMs, AIPs, SIGMETs and authority communications stay authoritative.
- × 100% accuracy. Every score ships with confidence and coverage tier, so you can see how solid the ground is under it.
Shaped to your desk.
Same Console, different job. Your role page shows it against your pains — with a live check to try.
Per-leg checks for the owner file and the SMS / IS-BAO audit
War & NCBR return pack on live data
Reroute rationale, documented
Dated records for SMS and board reporting
The itinerary file that survives an audit
How to start.
You don't choose a plan today — the trial is the full product.
- 1
Enter your email — the workspace opens in about two minutes. No card, no sales call.
- 2
Use the full Console for 14 days — check routes, save records, export, verify. Your first record takes about 10 minutes.
- 3
Pick a plan when you've seen your usage: Solo $99/mo — one seat, or Team $399/mo — five seats with a shared journal. Annual billing saves two months.
The same engine ships as a REST API — one GET per route, ~50ms, webhooks on thresholds. Sandbox free, production from $2K/month.
Console — FAQ
Common search queries answered with current status, FIR codes, and source citations.
- What exactly is in a saved record?
- Reference number, route and date, the 0–100 score with confidence and coverage tier, the per-FIR breakdown with contributing signals and dated citations, your recorded decision and rationale, who recorded it and when (UTC), and a public verification link. Exportable as PDF and CSV.
- Is this a go/no-go authority?
- No. The Console documents your judgment — the score is a numerical index input, and every record says so explicitly. It does not replace NOTAMs, AIPs, trip-support briefs, or the pilot-in-command’s authority.
- How does the 14-day trial work?
- Sign up with an email — no card, no sales call, no plan choice up front. You get the full Console for 14 days; pick Solo or Team once you’ve seen your own usage. Annual billing saves two months.
- Solo or Team — what’s the difference?
- Solo ($99/month) is one seat. Team ($399/month) is up to 5 seats with a shared journal — everyone sees the same records, decisions carry their author’s name. Same engine, same features otherwise.
- Who can verify a record I hand out?
- Anyone holding the document — the verification link is public by design and shows the record’s authenticity attributes without exposing your account or journal. It keeps answering even if your subscription ends: records must outlive subscriptions to be worth filing.
- When do I need the API instead?
- When a system, not a person, consumes the scores — quoting tools, dispatch boards, booking flows, policy engines. Same engine, delivered as JSON: the API product page has the details. Many teams run both: API for the pipeline, Console for the humans and the records.
- Where do the scores come from?
- 341 FIRs scored daily from public regulatory and operational data — EASA, FAA, ICAO, ADS-B telemetry, conflict-event and operator signals — per the published methodology. Calibration (Brier / ECE) is published quarterly, and every score carries its confidence and coverage tier.
FlySafe provides automated computation of numerical indices from publicly available data. Indices are raw computational output and do not represent opinions, assessments, recommendations, or advice of any kind. Records document the account holder's own decisions. They do not replace official NOTAMs, AIPs, SIGMETs, or communications from aviation authorities. See Terms of Service.