Viewing the logbook of: openiduser1035
Sign-in/Register
Avatar for openiduser1035
IdentifierNameCoordinatesTypeMunicipalityRegionCountry
KRMGRichar B Russell34.35, -85.16Small AirportRomeGeorgiaUnited States
KPDKDekald-Peachtree33.88, -84.3Medium AirportAtlanta, GAGeorgiaUnited States
KCNICherokee County34.31, -84.42Small AirportCantonGeorgiaUnited States
KWDRBarrow County33.98, -83.67Small AirportWinderGeorgiaUnited States
KWDRBarrow County33.98, -83.67Small AirportWinderGeorgiaUnited States
KLZUGwinnett county- briscoe field33.98, -83.96Small AirportLawrencevilleGeorgiaUnited States
KRHPWestern Carolina Regional35.2, -83.86Small AirportAndrewsNorth CarolinaUnited States
KANDAnderson Regional34.49, -82.71Small AirportAndersonSouth CarolinaUnited States


Above is a list of custom locations that you have defined. A custom location is a place you have flown to or flown over that does not have an official FAA/ICAO/IATA identifier. If you are trying to log a flight to an airport which is not in the FlightLogg.in airport database, a better solution is to go to OurAirports and create a new page for that airport. The data will eventually make its way into FlightLogg.in's database from there.

To use a custom location in a flight, just use the identifier you have defined above. To force the use of a custom location, prefix the identifier with a "!". For instance, a flight from "DEN - !DEN - DEN" would be from Denver, to a custom identifier you have defined as "DEN", then back to Denver.

To use a custom location as a flyover point, prefix it with a "@". So a flight from Denver, then flying over a custom point called "CUS", then landing back at Denver would be "DEN - !@CUS - DEN". It is important to log fly-over points accurately to differentiate between flights that quality for Point to Point XC.