All 25 Monitored FIRs
| # | FIR | Region | Index | Level | 24h Δ |
|---|---|---|---|---|---|
| 1 | OAKX | Kabul FIR Afghanistan | 97 | critical | → 0 |
| 2 | OLBB | Beirut FIR Lebanon | 97 | critical | → 0 |
| 3 | OJAC | Amman FIR Jordan | 97 | critical | → 0 |
| 4 | OEJD | Jeddah FIR Saudi Arabia | 86 | critical | → 0 |
| 5 | OPLR | Lahore FIR Pakistan | 86 | critical | → 0 |
| 6 | LLLL | Tel Aviv FIR Israel | 72 | high | → 0 |
| 7 | OSTT | Damascus FIR Syria | 71 | high | → 0 |
| 8 | OIIX | Tehran FIR Iran | 70 | high | → 0 |
| 9 | ORBB | Baghdad FIR Iraq | 69 | high | → 0 |
| 10 | OYSC | Sanaa FIR Yemen | 68 | high | → 0 |
| 11 | HCSM | Mogadishu FIR Somalia | 68 | high | → 0 |
| 12 | OMAE | Emirates FIR UAE | 67 | high | → 0 |
| 13 | OTBD | Doha FIR Qatar | 57 | high | → 0 |
| 14 | OPKR | Karachi FIR Pakistan | 56 | high | → 0 |
| 15 | LTBB | Istanbul FIR Turkey | 55 | high | → 0 |
| 16 | OKAC | Kuwait FIR Kuwait | 55 | high | → 0 |
| 17 | LTAA | Ankara FIR Turkey | 55 | high | → 0 |
| 18 | HSSS | Khartoum FIR Sudan | 54 | high | → 0 |
| 19 | OISS | Shiraz FIR Iran | 54 | high | → 0 |
| 20 | OOMM | Muscat FIR Oman | 53 | high | → 0 |
| 21 | OEDF | Riyadh FIR Saudi Arabia | 52 | high | → 0 |
| 22 | HLLL | Tripoli FIR Libya | 50 | moderate | ↑ +1 |
| 23 | OBBB | Bahrain FIR Bahrain | 43 | moderate | → 0 |
| 24 | LCCC | Nicosia FIR Cyprus | 32 | moderate | → 0 |
| 25 | HEGC | Cairo FIR Egypt | 7 | low | → 0 |
Snapshot generated 28 Jun 2026, 06:00 UTC. Scores are 72-hour-horizon predictions from FlySafe pipeline. Δ = change vs previous run. Sparkline = daily-max value over last 30 days. Click FIR code for region briefing.
GPS interference is tracked in detail — per-FIR, aggregated daily — on the GPS Interference Regional Map →
Methodology Summary
FlySafe numerical indices are computed deterministically from publicly available sources. The pipeline aggregates EASA Conflict Zone Information Bulletins, FAA SFARs and prohibitory NOTAMs, ICAO publications, national civil aviation authority NOTAMs, ADS-B telemetry (NIC / NACp position-quality reports), conflict-event databases (UCDP, ACLED), GDELT news signals, satellite hotspot data (NASA FIRMS), weather reports, and operator advisories.
Each FIR receives a numerical index on a 0–100 scale, segmented into four levels: low (<25), moderate (25–49), high (50–74), critical (≥75). The index is a structured aggregation, not a risk assessment, opinion, or operational recommendation.
Full methodology reference: /methodology/. Source-cited supporting datasets: GPS interference, closure timeline.
Coverage & Known Limitations
- 25 FIRs covered. Coverage focuses on conflict-zone-adjacent FIRs in Middle East, Sahel, South Asia, Caucasus periphery. Coverage roadmap: expanding to 50 FIRs (Q3 2026).
- Snapshot, not real-time. This page refreshes daily. Operational customers needing real-time updates use the FlySafe API (continuous, sub-minute latency). For custom routes and per-route scoring, API access is required.
- No per-route, no per-carrier scoring on this page. FIR-level only. Route-level (e.g. DEL–LHR) and carrier-specific scoring are programmatic-only via API.
- Index ≠ certainty. Higher index reflects more concurrent operational considerations from public sources. Specific operational decisions remain the responsibility of operators and aviation authorities.
- Data lag. Public source ingestion has variable latency (minutes for ADS-B, hours for news, days for some conflict databases). Snapshot reflects last successful pipeline run.
- Methodology calibration ongoing. Backtest accuracy reporting is in development and will be published once calibration stabilises across all monitored FIRs.
Free snapshot: 25 conflict-zone FIRs. API subscription: 270+ FIRs.
Same daily-refreshed scoring, expanded to the full operational FIR universe — with per-route queries, score-change webhooks, and 7d / 30d forecast horizons.
Unlock 270+ FIR coverage
Free Sandbox keys for evaluation. Paid tiers add per-route scoring, webhook alerts, and historical access.
How to Cite or Access
Cite as: FlySafe airspace indices, snapshot of 28 Jun 2026, 06:00 UTC with a link to this page. Numbers are CC-BY 4.0; reuse permitted with attribution to FlySafe and the underlying primary sources.
Programmatic access via the FlySafe API: per-FIR current index, 72h / 7d / 30d horizons, full factor breakdown, historical trend. Authenticated access for airlines, ops platforms, and underwriters.
Request API access →Related Resources
Airspace Indices — Frequently Asked Questions
Common search queries answered with current status, FIR codes, and source citations.
- What is a FlySafe numerical airspace index?
- A 0–100 integer that summarises operational considerations affecting commercial aviation in a specific Flight Information Region (FIR). The index is computed automatically from public sources (EASA Conflict Zone Information Bulletins, FAA SFARs and NOTAMs, ICAO publications, ADS-B telemetry, conflict-event databases, GNSS interference reports) using a deterministic methodology. Higher values indicate more operational considerations are concurrently active.
- How often is the index updated?
- This public snapshot refreshes daily (typically around 06:00 UTC). The underlying data pipeline runs continuously (sub-minute updates for some signals such as ADS-B). Operational customers requiring real-time updates use the FlySafe API; this page is a daily reference snapshot. The exact snapshot timestamp is shown at the top of the page.
- What is the difference between this page and the FlySafe API?
- This page shows a daily FIR-level snapshot freely accessible to anyone, suitable for journalists, researchers, and general reference. The FlySafe API provides real-time updates, per-route scoring (e.g. DEL–LHR through all transit FIRs), historical access, custom queries, and programmatic integration with operator systems. API access requires authentication and is intended for airlines, ops platforms, insurers, and partners.
- Is this a risk assessment?
- No. FlySafe produces numerical indices — automated computation of public data into a structured score. Indices are raw computational output and do not represent opinions, assessments, recommendations, or operational advice. They do not replace official NOTAMs, SIGMETs, AIPs, or communications from aviation authorities. Operators must independently verify current airspace status through official channels. See Terms of Service.
- How do I cite these numbers?
- Cite as "FlySafe airspace indices, snapshot of [date]" with a link to this page. For permanent archival or programmatic access, use the FlySafe API (see access page). Each index has a horizon (72h shown here), a level (low / moderate / high / critical), and a score-delta vs the previous run.
- Why are some FIRs not shown?
- This snapshot covers 25 FIRs where FlySafe maintains continuous monitoring. Coverage is expanding. FIRs with no recent prediction data, insufficient sample size, or known data-pipeline issues are excluded from this view. The /briefings/ section provides per-region context for monitored FIRs.
- What does the score-delta column mean?
- Score-delta is the change in numerical index since the previous run of the same FIR (typically 24h ago). An upward arrow with a positive value indicates the index has risen; downward with a negative value indicates it has decreased; flat (→) indicates no material change since the prior run.
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 do not replace official NOTAMs, SIGMETs, AIPs, or communications from aviation authorities. Operators must independently verify current airspace status through official channels. Reuse permitted under CC-BY 4.0 with attribution. See Terms of Service.