Clear Path

Menu

Request access

Contact

Clear Path helps airfield, planning, and engineering teams rapidly screen proposed objects against supported obstruction-evaluation criteria, identify likely conflicts, and generate defensible planning reports before formal coordination or final approval.

For single-use evaluation requests, team rollout questions, agency use, or legal/privacy contact, contact Clear Path through the support channel below.
One supported contact path
Use the public support inbox for access, billing, report, privacy, legal, and launch-support questions.

Support Email

support@airspaceevaluator.com

Typical response: within 2 business days.

This is the public support inbox for access, billing, report, privacy, and launch-support questions.

Company updates: LinkedIn company page

Support Categories

  • Access/account issue
  • Billing or invoice question
  • Report question
  • Airport/runway data issue
  • Criteria/supportability question
  • Bug or technical issue
  • Demo/access request

What to Include in an Access Request

  • Organization name
  • Your role
  • Intended use case
  • Airport or airfield type
  • Criteria family needed: Part 77, FAA AC, UFC / DoD, or unsure
  • Access interest: demo, single-use, team, agency, or enterprise

Send these details by email so the team can respond with the appropriate access path.

Bug or Report Question Template

  • Airport identifier or airport name
  • Runway pair and runway end / reference end
  • Criteria profile used
  • Object latitude/longitude
  • Ground elevation and object height AGL
  • Screenshot or exported report, if available
  • What looked wrong, unclear, or blocked
  • Account email if the issue is access or billing related

Include report timestamp, app/version metadata, and the criteria profile when they are available. That context makes support and report interpretation materially faster.

Operational Notes

This page provides the public support, privacy, and legal contact path. Use it for account issues, billing questions, report interpretation, airport data questions, and supported-use reviews.

Commercial and Billing Posture

Demo access is generally no-charge unless separately agreed in writing. Single-use purchases are generally non-refundable once access, evaluation, or report delivery has occurred, except for duplicate charge, billing error, required law, or written agreement.

Monthly plans may be canceled before renewal; access continues through the paid term; no prorated refunds are generally provided except for billing error, required law, or written agreement. Annual plans may cancel renewal; refunds are provided only by written agreement, billing error, or required law. Enterprise and manual billing arrangements follow the applicable written order, quote, or contract.

Sample invoice availability, purchase-order discussion, and manual invoice handling are available through this contact path. W-9 and capability statement materials can be provided on request when ready.

Before discussing paid rollout or support needs, review the first-evaluation guide to understand the current supported workflow.

For airport, engineering, planner, consultant, or government-adjacent teams, use this contact path to discuss supported criteria, single-use needs, or organization rollout.

References to FAA, DoD, UFC, Part 77, or airport criteria on this site describe source criteria only and do not imply endorsement, sponsorship, authorization, or official status by any government or airport authority.

Escalation if the Primary Path Fails

  • If the issue is account access, password reset, or billing related, use a subject line that starts with Access, Billing, or Invoice so it can be routed quickly.
  • If you do not receive a response within 2 business days, resend the request with Follow-up in the subject and include the original send date and time.
  • If the issue involves security, privacy, or suspected unauthorized access, mark the subject Security/Privacy Review and include only the minimum details needed to investigate safely.
  • If the public inbox route appears unavailable, use the same support address from a second sender or mail client and reference the prior failed attempt in the message body.

Additional References

Review the disclaimer, terms, and privacy policy before public use.