Viewing the logbook of: kdevies
Sign-in/Register
Avatar for kdevies
IdentifierNameCoordinatesTypeMunicipalityRegionCountry
KHZYNortheast Ohio Regional Airport41.7779712, -80.6955079Small AirportAshtabulaOhioUnited States
KAXQClarion County Airport41.2249444, -79.4421667Small AirportClarionPennsylvaniaUnited States
KYNGYoungstown-Warren Regional Airport41.2615833, -80.6803611Medium AirportYoungstown/WarrenOhioUnited States
KCAKAkron-Canton Regional Airport40.9150556, -81.4436389Medium AirportAkronOhioUnited States
38DSalem Airpark40.9480833, -80.8620833Small AirportSalemOhioUnited States
2D1Barber Airport40.9699708, -81.098667Small AirportAllianceOhioUnited States
3G6Tri-City Airport40.906, -81.0000278Small AirportSebringOhioUnited States
1G3Kent State University41.1513889, -81.4151111Small AirportStowOhioUnited 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.