Identifier | Name | Coordinates | Type | Municipality | Region | Country |
KHZY | Northeast Ohio Regional Airport | 41.7779712, -80.6955079 | Small Airport | Ashtabula | Ohio | United States |
KAXQ | Clarion County Airport | 41.2249444, -79.4421667 | Small Airport | Clarion | Pennsylvania | United States |
KYNG | Youngstown-Warren Regional Airport | 41.2615833, -80.6803611 | Medium Airport | Youngstown/Warren | Ohio | United States |
KCAK | Akron-Canton Regional Airport | 40.9150556, -81.4436389 | Medium Airport | Akron | Ohio | United States |
38D | Salem Airpark | 40.9480833, -80.8620833 | Small Airport | Salem | Ohio | United States |
2D1 | Barber Airport | 40.9699708, -81.098667 | Small Airport | Alliance | Ohio | United States |
3G6 | Tri-City Airport | 40.906, -81.0000278 | Small Airport | Sebring | Ohio | United States |
1G3 | Kent State University | 41.1513889, -81.4151111 | Small Airport | Stow | Ohio | United 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.
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.
New Location | [X] |