Viewing the logbook of: Maverick13
Sign-in/Register
Avatar for Maverick13
IdentifierNameCoordinatesTypeMunicipalityRegionCountry
H96BentonNoneNot Known
PIAPeoriaNoneNot Known
CGICape GirardeauNoneNot Known
STLSt LouisNoneNot Known
3LFLitchfieldNoneNot Known
PAHPaducahNoneNot Known
PJYPinckneyvilleNoneNot Known
POFPoplar BluffNoneNot Known
DYRDyresburgNoneNot Known
OWBOwensboroNoneNot Known
EVVEvansvilleNoneNot Known
MTOMattoonNoneNot Known
VLAVandaliaNoneNot Known
SUSSpirit of St LouisNoneNot Known
MWAMarionNoneNot Known
TAZTaylorvilleNoneNot Known
MDHCarbondaleNoneNot Known
LOTLewis UniversityNoneNot Known
ARRAuroraNoneNot Known
DPADupageNoneNot Known
C09MorrisNoneNot Known
DLLBarabooNoneNot Known
MRJMineral PointNoneNot Known
OVSBoscobelNoneNot Known
SGSSouth St PaulNoneNot Known
JVLJanesvilleNoneNot Known
SFYSavannaNoneNot Known
CWIClintonNoneNot Known
91CSauk-PrairieNoneNot Known
C47PortageNoneNot Known
EFTMonroeNoneNot Known
RFDRockfordNoneNot 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.