Most Part 107 pilots know their airspace classification before wheels up. Fewer know the distance and bearing to the nearest airport — or the nearest hospital. Both numbers matter, and both require more than a quick glance at a map to calculate accurately for a hundred sites at once.
FlightDeck calculates and records both automatically for every site in your project, stored directly in your working data file so the information is always there when you need it.
Why Distance to the Nearest Airport Matters
Airspace classification tells you whether you need authorization. Distance and bearing to the airport gives you the operational picture — which direction manned traffic is likely approaching from, how close you are to approach and departure corridors, and what situational awareness your crew needs during the operation.
It also matters for your documentation. COA narratives, pre-flight checklists, and formal risk assessments typically require nearest airport information. Having it automatically populated across your entire project means you’re not manually looking up each site the night before.
FlightDeck stores two entries for each site: the nearest airport and the second-nearest airport. Each entry includes the airport name, ICAO identifier, airport type, airspace class, distance in nautical miles, and cardinal bearing. All of this is calculated using Haversine geometry — the same spherical distance formula used in aviation navigation — applied against a locally stored airport database.
Why Distance to the Nearest Hospital Matters
UAS incident response planning requires knowing where the nearest medical facility is. For inspection work in rural corridors — tower lines, pipelines, agricultural parcels — that answer isn’t always obvious, and it changes with every site.
FlightDeck records the nearest hospital and second-nearest hospital for each site, with the same distance and bearing format as the airport data. On a 200-site project spread across three states, that’s 200 hospital lookups that don’t require manual research.
This data supports your pre-flight risk assessment and is available in the same row as your airspace classification, weather, and authorization status — all in one place when you’re planning the next day’s work.
How It’s Calculated
All distance and bearing calculations use Haversine geometry applied to latitude and longitude coordinates from your site list. The airport and hospital databases are stored locally, so the lookup runs whether or not you have an internet connection.
When a site already has nearest-airport data on file, FlightDeck reads from a SituationalAwareness cache to avoid redundant calculations on re-runs. New sites and any sites missing the data are calculated fresh during the 3-phase update.
The bearing is expressed as a cardinal direction — N, NE, SW, and so on — alongside the nautical mile distance, which is what you want for communicating airspace proximity in plain language.
What This Looks Like in Practice
Before a week-long tower inspection campaign, you run the FlightDeck 3-Phase Update. By the time it finishes, every site in your project has its nearest airport and hospital populated — the distance, the direction, and the identifier. Your pre-flight checklist for each site has the information without a separate research step.
When a client or project manager asks how close Site 47 is to the nearest controlled field, you have the answer in your spreadsheet, not from memory or a map lookup.
When you’re writing a COA narrative for a controlled-airspace site, the nearest airport data is already available. When you’re doing site-by-site risk assessment, hospital proximity is part of the same dataset.
The situational awareness data FlightDeck calculates is the kind of information that takes five minutes per site to look up manually — and zero minutes per site when it’s done automatically across your entire project.
FlightDeck’s situational awareness calculations are included in every license tier. Try it free for 30 days.
