Is this for you?
- You operate on routes or in regions where GNSS interference has been reported, or you are about to, and want numbers rather than anecdotes.
- You are designing a UAS or eVTOL that depends on GNSS and on being seen by ADS-B, and your certification or safety case needs an evidence-based view of the environment.
- An authority, insurer or customer has asked how you assess navigation and surveillance risk, and your answer today is "we read the NOTAMs".
- You run a safety management system and want GNSS and surveillance exposure entered as hazards with a likelihood you can defend.
What you get
- Exposure maps. Where GNSS gaps, position deviations and ADS-B anomalies occurred in your regions and along your routes, by month, at the resolution the data supports.
- Rates against a global baseline. Events per flight hour for your operating area compared with the traffic-normalized baselines of the GET-25 benchmark across 260 Flight Information Regions, so you know whether your exposure is unusual or ordinary.
- Ranked exposures. The routes, regions and time windows that matter most for you, with the evidence behind each.
- Recommendations. Procedures, training points, dispatch or planning rules, and, for developers, design and requirement implications, written for the people who will act on them.
- Data appendix and walkthrough. The tables behind the charts, in a form you can drop into a risk register or a safety case, and a 45-minute call to go through it.
How it runs
- Day 1Scoping callYou name the regions, routes, aircraft types and period. I confirm coverage and what the data can and cannot show.
- Days 2–8Data and analysisI pull global ADS-B surveillance data for your scope, process it with the same Global Envelope Thresholding method as my published work, and build the exposure picture. If you can share your own flight data or GNSS logs, they are added, but they are not required.
- Days 9–12ReportMaps, rates, ranked exposures and recommendations, reviewed for plain language.
- Day 14Walkthrough45 minutes with your operations or engineering lead. Follow-up questions answered by email for a month.
What I need from you
A list of routes or regions, the period you care about (I suggest the last twelve months), your aircraft types, and any incidents or crew reports you want checked against the data. Nothing else. No access to your systems.
Questions I get asked
Do you need our flight data?
No. The analysis runs on public ADS-B surveillance data at global scale, the same source as the published research. Your own ADS-B logs or GNSS receiver data, if you have them, sharpen the picture for your fleet, but the engagement does not depend on them.
Does the data cover my region?
Coverage depends on the density of ADS-B receivers, which is excellent over Europe and North America and thinner over oceans and parts of Africa, Asia and South America. During scoping I state the coverage confidence for each region you name, and the report says where the evidence is strong and where it is indicative.
How current is it?
The analysis uses the most recent complete months available at the time of the engagement, and the historical record goes back several years, so seasonal and year-on-year patterns are visible.
Can this feed our safety management system?
Yes. The exposures are written as hazards with an observed likelihood, and the appendix gives the numbers behind them, so they can be entered directly in a risk register or referenced in a safety case.
Start with a 45-minute readiness call
Tell me what you build or operate. You leave the call with your three most important next steps, whether or not we work together; if this engagement fits, a fixed-scope proposal and quote follow within a few days.
Ask about an exposure analysis
Founder of Mevocopter Aerospace. M.Sc. in Aviation and Aerospace Sustainability with a specialization in Aviation Cybersecurity from Embry-Riddle; Ph.D. researcher in Data Science at the University of Essex; earlier career in computer support and network security. Full biography · Publications