Flight Log Locations

Easily identify takeoff and landing points across all your flights.

Spidertracks now automatically tags each flight with location codes and names for takeoff and landing events. This makes it easier to track aircraft movements, support dispatch operations, and review flight history with confidence.

This feature requires Flight Log events, so is only supported for Spider X, Spider 8 with ATU or aircraft sensor inputs, and Flightcell DZMx.

What is Location Detection?

Flight events (takeoff and landing) are now enriched with human-friendly location references, including:

• ICAO codes (e.g. NZCH for Christchurch)

• IATA codes (e.g. CHC)

• Other common but unofficial codes

• Your own custom locations for private or non-standard sites

Spidertracks will display the most relevant location name and code, based on your organisation’s settings.

No setup required — this is enabled automatically for all users from August 2025.

Who is this useful for?

This feature is especially valuable for operators flying into a wide range of destinations, such as Charter operators, Training schools, VIP transport services, Aeromedical teams, Infrastructure inspection crews and more.

Operators with fixed routes (e.g. tourism or utility flights) may benefit less, but can still configure custom naming for private sites.

Where are Locations Shown?

You’ll see location names and codes throughout our solution:

Flying Page (web)

When an aircraft is selected in the Aircraft list, the expanded panel includes a mini timeline of key flight events. If takeoff and landing events have occurred, and locations for these have been identified, they will be shown:

Flight History (web)

"FROM" and "TO" columns in the History table show location Codes (according to the priority preference set in your Admin settings). 

Hovering over any code to show the location Name in a tool tip;

Additional cases supported:

• '...' shows if a flight track is in progress but Takeoff or Landing events have not yet been detected.
• (no code) shows, it indicates an airport was found but there is no official code for it. The airport name will show in the tool tip.
• (unknown) shows, it indicates a takeoff or landing was detected but there was no nearby location code matched.

 

Flight Explorer (web)

The Timeline view will show any found location Codes and Names:

Notifications (coming soon)

Location codes and names will soon be available in Flight Log event notifications messages.

Aircraft Timeline (mobile) (coming soon)

We're brining Flight Logs + Locations to mobile soon. Contact our team if you want to learn more.

Update or Create a Location

The Create or Update workflow can be opened from History page or Flight Explorer:

• History: Click on the blue location code (or 'unknown' or 'no code')
• Flight Explorer: Click on the blue 'edit' pencil next to the location code (or 'unknown' or 'no code')

A list will show of any nearby known locations that can be selected, including the one that is already selected.

If the actual location is not listed, or a new Code and Name are desired, use the 'Create' row (only available if Admins have enabled).

NOTE:

• Custom Locations created by members of your organisation are only available within your organisation.
• Custom Locations will be created at the coordinates of the takeoff or landing event being referenced
• Location codes up to 10 characters are supported (alpha only)
• Names up to 30 characters are supported
• Only Aircraft Landing Area (ALA), Helicopter Landing Site (HLS) and Seaplane Base (SEA) are supported for custom locations.

Managing Locations Settings

Visit to Admin > Aircraft > Locations in the web application to manage:

Permissions

All members that have visibility of a flight will be able to update the Location code from known, nearby locations.

Admins can manage whether only they (Admins) or any user is allowed to create a new custom location.

Location Source Priority

Admins can configure how location matches are resolved using priority settings, e.g.:

• Custom > ICAO > IATA > Other (this is default)

  or

• Custom > IATA > ICAO > Other

Nearby custom locations you have created are always given first priority.

Editing or Deleting Custom Locations

All custom Locations created within your Organisation will be listed in the Custom Locations table.

You can:

• Multi-select and Delete to clean up no longer needed Locations
• Click any row to open the Edit drawer;
  • Update CODE (will retro-apply to all flights tagged with that location)
  • Update Name
  • Update Type
  • Update Coordinates (lat/lon)

How Does It Work?

When a takeoff or landing event is recorded, Spidertracks cross-references an extensive list of known locations suitable for aircraft takeoff/landing events, along with an custom Locations setup within your Organisation.

If multiple locations are found, the system selects the best match based on:

• The aircraft type and match to the Location (e.g. heliport will not be listed for fixed wing, seaplane base will not be listed for helicopter)

• Distance from event to the found Location

• Source priority preference (set by Admin)

All logic runs automatically in the background — no action is needed to enable detection.

Need Help?

If you have any questions or would like assistance managing custom locations, please contact support or reach out to your account manager.