What Are Custom Locations in DigiPlog?

When logging a flight, one of the first things any pilot looks for is the departure and arrival location. DigiPlog comes preloaded with a database of over 30,000 airports, covering most of the published and public-use airfields across Europe and the U.S. — but what if your landing site isn’t in the system?

Whether you’re flying into a private farm strip, a helicopter landing pad, or a remote grass field, DigiPlog gives you the ability to add custom locations.

Here’s how it works.

✈️ Why You Might Need a Custom Location

In general aviation, not every landing is at a towered or charted airport. You might be:

• Landing at a private airstrip not in the public ICAO database
• Visiting a friend’s grass strip for a weekend fly-in
• Logging a flight to a non-published helipad
• Flying to a military or industrial site not included in standard airport lists
• Training at a temporary or field-based landing site

In these cases, you need a way to record where you flew, even if it’s not a registered ICAO/IATA airport. That’s where DigiPlog’s custom location feature comes in.

🛬 How to Add a Custom Location in DigiPlog

If you can’t find your landing or departure site when entering your flight, here’s how to add it:

1. Tap the plus icon in the airport search bar
2. Enter the name of the location (e.g. “Smith’s Farm Strip”)
3. Pin it on the map
4. Save it — and it’s now available for your logbook entries

Your custom locations are private to you. You can manage your custom locations under Settings.

🛠️ What if My Location Is Added Later?

If a new airport or site is added to the global database later, you can update or merge your custom location with the new official one, without losing your log entries.