Back to support

GlideSpace guide

Uploading airspace data to GlideSpace

For glider pilots preparing Garmin watch airspace warnings with GlideSpace.

GlideSpace does not carry a built-in airspace database. Instead, you load the airspace file you trust for the area you fly, pick a focused region, and sync that compact warning set to the watch.

Why GlideSpace uses your own airspace file

Airspace is not generic background decoration. It changes, it has local rules, and pilots need to know which source they are using. A bundled global database can look convenient, but it can also become stale or include airspace that is irrelevant for the flight you are planning.

GlideSpace keeps the source explicit. You start with a Naviter .cub file, choose the flying area you need, and sync that selected data to the watch.

The basic workflow

  1. Prepare or download the current airspace for your region in .cub format.
  2. Open the GlideSpace uploader and select the file.
  3. Choose the area you want to carry on the watch.
  4. The uploader prepares a compact data set and gives you a short sync code.
  5. Enter the code in GlideSpace on the watch to download the selected airspace.

After that, GlideSpace can watch your position against the airspace you loaded and warn when you get close laterally or vertically.

Why the selected area matters

A Garmin watch has limited memory. That is fine for a focused cockpit tool, but it means you should load the airspace you are likely to use, not an entire continent. Smaller, relevant areas are faster to sync, fit more reliably, and are easier to reason about before takeoff.

Newer watches with more memory can carry larger data sets. Older button watches may still be useful, but they need a tighter selection. The uploader shows the practical limit for your watch model before you sync.

What the watch checks in flight

GlideSpace uses GPS for position and the watch barometer for altitude. It checks both horizontal distance and vertical margin, because airspace awareness only makes sense when both are considered together.

MSL limits are compared using your QNH setting. Flight-level limits are compared on the standard 1013 hPa datum. When you approach your configured margin, GlideSpace warns with a banner, vibration and tone.

Keep the data current

The app can only warn against the data you loaded. Before flying, make sure your .cub file is current for the day, region and rules that apply to your flight. GlideSpace is an awareness layer on the wrist, not a replacement for official briefing, charts, NOTAMs, radio, or pilot judgement.

Used that way, it gives you a small but useful second check: the airspace around you, visible on your wrist, with the data source you chose before takeoff.

View GlideSpace Open GlideSpace uploader