FAQ
Frequently asked questions
Straight answers on procurement, onboarding, data ownership, and offline behavior. If procurement is the open question, request a demo and we'll take it from there.
About Glidepath
Who is Glidepath for?
Airports and airfields of any size: general aviation, reliever, and municipal airports and FBOs, FAA Part 139 airports, airport authorities with more than one field, and military airfields. Smaller fields turn on the modules they use and leave the certification modules off.
Is every module included?
Yes. Every module is included at every size, with no nickel-and-diming for capabilities. Turn on the parts you use and leave the rest off.
Is Glidepath the same as GlidePathCX, GlidePath Air, or Glidepath Group?
No. Glidepath is airport and airfield operations software built in Michigan. It is not affiliated with GlidePathCX (airport loyalty), GlidePath Air (indoor navigation), or Glidepath Group and BEUMER Glidepath (baggage handling).
Procurement
How do we buy Glidepath?
Contact us. We'll work with your contracting or purchasing office on whatever process your organization already uses to buy software.
What does Glidepath cost?
Contact us for pricing. Glidepath is priced for smaller airports, and every module is included at every size. Your price is set for your airport, with no nickel-and-diming for capabilities. Turn on the parts you use.
Can we evaluate it first?
Yes. Request a demo, and the walkthrough runs on scenarios like yours instead of a generic script.
Onboarding
How long does it take to stand up a new airfield or airport?
The guided base setup wizard steps through configuration in order: runways, lighting, species, and which modules you need. Most of the day-one setup work happens inside the wizard itself.
How do users get accounts?
Admins invite users by email and pick their role at the time of invite. There's no self-signup.
Do we need to install anything?
No. Glidepath runs in the browser, and it installs as an app on phones and tablets directly from the browser.
Data ownership
Who owns the records?
The customer does. Glidepath stores and serves the records; it doesn't own them.
Can we get our data out?
Yes. Records exports are available on demand in CSV and PDF, built for records custodians.
Do documents pass through third parties?
No. PDFs generate in the browser on your own machine; nothing routes through a third party to build the file.
Offline capability
What happens when the connection drops on the airfield?
Supported writes queue locally and retry when connectivity returns. Previously loaded supported screens remain available, but some actions need a connection. Check Pending sync for unsent work and pending photo uploads; cached status is not a fresh observation.
Does it work on mobile?
Yes. Glidepath installs as an app on phones, tablets, and desktops, so the same experience is available wherever you are on the airfield.
Is offline data safe if the device is lost?
The offline queue lives inside your signed-in browser session on that device. Access is account-gated, and an admin can disable the account if a device is ever lost.
Security
Who can see a base's records?
People that base's own permission matrix grants, and nobody else. The check is enforced in the database on every read and write, and installations never see into each other.
Do documents transit anyone else's servers?
Reports and exports are generated on the device that requests them. If you email a report from the platform, it goes out through our mail provider like any other message; saving or distributing it any other way stays inside your own procedures.
What authorizations does Glidepath hold today?
Glidepath is a commercial cloud product and holds no U.S. government cloud authorization today. If your environment requires one, ask us where that path stands.