Duty of care for the flight path —
documented.
Your security provider scores the destination. FlySafe scores the airspace the flight actually crosses — per itinerary, at booking time, with a dated snapshot your audit trail can point to months later.
Structured data for travel-policy decisions — not security, medical, or legal advice. Consular travel advice remains the authoritative source.
Sandbox free · production from $2K/mo · dated records in the Console from $99/mo. Full grid on the pricing page.
Pick a business route — the live engine scores the airspace along it as you read this.
In your workflow this lookup lands at booking time, timestamped, against the itinerary record. Informational input — not a recommendation to travel or not travel.
Where duty of care breaks down.
Corporate travel security providers focus on destination risk — crime, unrest, medical. Aviation-specific risk — overflown FIRs, GNSS interference zones, active EASA or FAA advisories — is rarely addressed in the same structured way.
A London–Delhi booking now routes via different airspace than last quarter. The destination risk for Delhi is unchanged, but the flight path has changed materially. Destination-only feeds do not flag the routing difference.
When a senior traveller books through an advisory-covered region, you need an auditable record of what advisory state existed at the time of booking. Screenshotting news articles is not audit evidence.
Legal asks what advisory state existed when the CFO's Delhi trip was approved. The file contains a screenshot of a news article and a forwarded email.
The defensible file is a dated snapshot: route, score, the regulator advisories active on the FIRs it crossed, timestamp — captured automatically at booking, retrievable exactly as it stood.
Into the travel programme in three steps.
Look up the itinerary.
Closes: the itinerary-level blindspot. Origin–destination in, aggregated index across the likely routing out — with flags for regulator advisories on the FIRs along the path. The routing layer your destination feed never sees.
Wire it into policy.
Closes: the aviation gap in your risk feed. Structured fields your policy engine evaluates against internal thresholds — "require VP approval if any FIR on the route has an active EASA CZIB" becomes an expressible rule instead of a judgment call.
File the snapshot.
Closes: documentation for audit. Every lookup returns a timestamp and advisory snapshot. Stored against the booking record, it is the evidence base for the duty-of-care file — what was known, when, from which sources.
The snapshot, field by field.
What lands against the booking record — the sellable unit is this JSON.
/v2/route/risk?from=LHR&to=DXB {
"from": "LHR", "to": "DXB",
"date": "2026-07-14",
"score": 33, "risk_level": "moderate",
"confidence": 0.85,
"coverage": { "status": "covered", … },
"scored_at": 1783641600
} Two fields drive policy: thresholds for approval tiers, risk_level for the traveller-facing note. Expressible rules, not judgment calls.
The timestamp that makes it audit evidence — this exact state, at booking time, stored with the itinerary.
Unknowns are explicit — status: "out_of_scope", score null. The file says "not monitored", never false assurance.
Illustrative values — the field shape is the exact v2 contract. Scores refresh every 5–30 minutes; always branch on coverage.status, never treat null as 0. Full contract: API docs.
Why the file holds up when someone asks.
- → 341 FIRs scored daily from public regulatory & operational data — EASA · FAA · ICAO · ADS-B · conflict-event signals
- → Regulator source-flags per FIR (CZIB · SFAR · national advisories) for the evidence trail
- → Timestamp + advisory snapshot per lookup — retrievable later exactly as it stood
- × Security or medical advice. Indices inform your travel policy; they do not recommend travel or non-travel.
- × A consular-advice replacement. Government travel advice remains separate and authoritative.
- × 100% accuracy. Brier / ECE published quarterly; every score carries confidence and coverage.
Useful references for policy wording: passenger rights on closure cancellations · reroute & refund frameworks · live briefings
How to start.
Sandbox free · Starter $2K/mo · Pro $5K/mo (SLA + webhooks)
Booking-time lookups and FIR change webhooks run on API request tiers; free sandbox to evaluate.
Check itineraries and keep dated, referenced, printable records in a signed-in workspace — no integration project. Console from $99/month, 14-day free trial, no card.
Request access — free sandbox, no card
Booking-time lookups · FIR change alerts · dated snapshot per score for the duty-of-care file.
Duty-of-care route data — FAQ
Common search queries answered with current status, FIR codes, and source citations.
- Does this replace our travel-security provider?
- No — it adds the layer they don’t cover. Destination-risk feeds score the city; FlySafe scores the airspace the flight crosses to get there. Most programmes run both: the security provider for ground risk, FlySafe for the flight path. Consular travel advice remains the authoritative source it always was.
- What does it cost?
- API sandbox is free on live data, no card. Production runs on request volume: Starter $2,000/month, Pro $5,000/month with SLA and webhooks. No integration? Dated, exportable route records ship in the Console — Solo $99/month, 14-day free trial. Full grid on the pricing page.
- How does a policy rule actually look?
- The response is structured, so your policy engine can express rules like "require VP approval if any FIR on the route carries an active EASA CZIB" or "flag itineraries where the route score exceeds your threshold." Two fields —
scoreandrisk_level— plus regulator source-flags drive it. - What do we file for the audit trail?
- Every lookup returns a timestamp and advisory snapshot — stored against the booking record, it documents what was known when the trip was approved. The Console produces the same as a referenced, printable record for programmes that want a file, not a feed.
- What about routes you don’t cover?
- The response says so explicitly:
coverage.status = "out_of_scope"withscore: null— never a guessed number. 341 FIRs are scored daily; your workflow shows "not monitored" instead of false assurance. - Is this a recommendation to travel or not travel?
- No. Indices are informational inputs to your travel policy process — not security, medical, or legal advice. The approval decision stays with your programme; the data documents its basis.
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. They are not security, medical, or legal advice. Consular travel advice from the traveller's government and professional duty-of-care counsel remain separate and authoritative sources. See Terms of Service.
Built for every aviation role
The same airspace-risk engine, tailored to how your team works.