Flight Log Locations

Easily identify takeoff and landing points across all your flights.  

Fleet Manager 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?

Takeoff and landing events are now enriched with easy-to-read 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

• Fleet Manager 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.

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.

How it works

Flight Log locations are assigned automatically when an airport is detected near a takeoff or landing event. If no nearby airport is found, you’ll need to create a Custom Location. Custom Locations are applied automatically from the time they are created.

When a takeoff or landing event is recorded, Fleet Manager cross-references the event against an extensive list of known locations suitable for aircraft operations, along with any Custom Locations configured within your organisation.

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

• Aircraft type compatibility (for example, heliports are excluded for fixed-wing aircraft, and seaplane bases are excluded for helicopters)

• Distance between the event and the candidate location

• Source priority preferences set by an administrator

All matching logic runs automatically in the background, no manual setup or action is required to enable location detection.

Note:

• Entries will not be retroactively applied to past events near that location.

Where are the Locations Shown?

A. 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:

B. 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;

Notes:

'...'	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.

 

C. Flight Explorer (web)

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

Update or Create a Location

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

1. Click Admin.

2. Click History. 

3. Click '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

Please Note - This page is purely for the management of settings, you can not add locations from this page, this must be done from the History Page where you can Update or Create a Location.

1. Click Admin.

2. Select Organisation.

3. Select Aircraft dropdown.

4. Click Locations.

 

A	Location Source Priority	Admins can configure how location matches are resolved using priority settings, e.g.: Custom > ICAO > IATA > Other (this is default) Custom > IATA > ICAO > Other Nearby custom locations you have created are always given first priority.
B	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.
C	Editing or Deleting Custom Locations	All custom Locations created within your Organisation will be listed in the Custom Locations table to: Multi-select and Delete to clean up no longer needed Locations Click any row to open the Edit drawer to: Update CODE (will retro-apply to all flights tagged with that location) Update Name Update Type Update Coordinates (lat/long)

 

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.

Need Help?

If you have any questions please contact [e-mail] or reach out to your account manager.