GeoSky
Geospatial Airspace & Obstruction Analysis
FAR Part 77 analysis, TERPS evaluation, obstruction mapping, and regulatory compliance — plus arrival/departure procedure evaluation, airspace structure review, and route analysis for airports, real estate, wind farms, and commercial development.

Whether it is a new hangar, a downtown tower, or a wind farm, anything tall near an airport has to be evaluated against the airspace around it. GeoSky brings that evaluation into one geospatial workspace for airports, real estate developers, and energy projects.
It performs FAR Part 77 analysis and TERPS evaluation, maps obstructions, checks regulatory compliance, and reviews arrival and departure procedures, airspace structure, and routes — including line-of-sight.
Capabilities
Airspace analysis for anything that rises
FAR Part 77 analysis
Imaginary surfaces are generated for the airport, and proposed structures are tested against them.
TERPS evaluation
Proposed structures are assessed for their effect on instrument procedures and minimums.
Obstruction mapping
Existing and proposed obstructions are mapped in 3D against the airspace surfaces.
Procedure and route review
Arrival and departure procedures, airspace structure, and routes are reviewed alongside the obstruction picture.
Line-of-sight
Line-of-sight from towers and facilities is evaluated for proposed development.
Compliance reporting
Results are documented for regulatory filing and stakeholder review.
Architecture
How it works
1 · Ingest
Airport geometry, terrain and elevation data, obstruction data, and published procedures are loaded into Helios.
2 · Model
Part 77 surfaces and TERPS criteria are generated and evaluated against each proposed structure or site.
3 · Deliver
Interactive 3D maps, penetration analysis, and compliance reports.
Technical profile
At a glance
- Data inputs
- Airport geometry, terrain / DEM, obstruction data, published instrument procedures
- Standards
- 14 CFR Part 77; FAA TERPS criteria
- Core methods
- 3D surface generation, penetration analysis, procedure impact assessment, line-of-sight
- Outputs
- Surface penetration results, obstruction maps, compliance reports
- Delivery
- Web application and Helios APIs
- Platform
- Helios — Cignus’s AWS-native aviation data and AI platform
- Access
- Role-based, enforced per request at the Helios API layer — not inside the application
FAQ
Common questions
Does GeoSky replace an FAA filing?
No. It supports the analysis and documentation behind a filing and helps identify problems before one is made; the FAA’s determination is still the authority.
Who uses GeoSky besides airports?
Real estate developers, wind and energy projects, and anyone siting a tall structure near an airport or under a procedure.
How is access controlled?
By role, at the API layer. Every request to Helios passes through interceptors that check the caller’s role and scope before any data is returned, so the same rules apply whether the request comes from the application, an API client, or an integration. Nothing is governed inside the application itself.
Work with GeoSky
Sign in with your Cignus account to launch it, or request access for your organization.