| Identifier | Name | Coordinates | Type | Municipality | Region | Country |
| H96 | Benton | None | Not Known | |||
| PIA | Peoria | None | Not Known | |||
| CGI | Cape Girardeau | None | Not Known | |||
| STL | St Louis | None | Not Known | |||
| 3LF | Litchfield | None | Not Known | |||
| PAH | Paducah | None | Not Known | |||
| PJY | Pinckneyville | None | Not Known | |||
| POF | Poplar Bluff | None | Not Known | |||
| DYR | Dyresburg | None | Not Known | |||
| OWB | Owensboro | None | Not Known | |||
| EVV | Evansville | None | Not Known | |||
| MTO | Mattoon | None | Not Known | |||
| VLA | Vandalia | None | Not Known | |||
| SUS | Spirit of St Louis | None | Not Known | |||
| MWA | Marion | None | Not Known | |||
| TAZ | Taylorville | None | Not Known | |||
| MDH | Carbondale | None | Not Known | |||
| LOT | Lewis University | None | Not Known | |||
| ARR | Aurora | None | Not Known | |||
| DPA | Dupage | None | Not Known | |||
| C09 | Morris | None | Not Known | |||
| DLL | Baraboo | None | Not Known | |||
| MRJ | Mineral Point | None | Not Known | |||
| OVS | Boscobel | None | Not Known | |||
| SGS | South St Paul | None | Not Known | |||
| JVL | Janesville | None | Not Known | |||
| SFY | Savanna | None | Not Known | |||
| CWI | Clinton | None | Not Known | |||
| 91C | Sauk-Prairie | None | Not Known | |||
| C47 | Portage | None | Not Known | |||
| EFT | Monroe | None | Not Known | |||
| RFD | Rockford | None | Not Known |
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] |
