To assist you in understanding each field within the ForeFlight Logbook Template, here are formatting notes for the fields:
AIRCRAFT TABLE FORMATTING
FIELD | FORMATTING NOTES |
AircraftID | The aircraft’s registration, or “tail number.” Example: N201TH |
TypeCode | This is the aircraft's ATC flight plan code. Usually, four characters. Example: Piper Archer = P28A. Find your aircraft's code here. |
Year | YYYY format. Example: 1997 |
Make | The manufacturer of the aircraft. Example: Cessna |
Model | The aircraft’s model name. Example: 172 |
Category | Use one of the following: Airplane, Rotorcraft, Glider, Lighter Than Air, Powered Lift, Powered Parachute, Weight-Shift-Control, Simulator. The aircraft’s “Class” field must correlate to this field. |
Class | Use one of the following codes: ASEL (Airplane Single Engine Land), AMEL (Airplane Multi Engine Land), ASES (Airplane Single Engine Sea), AMES (Airplane Multi-Engine Sea), RH (Rotorcraft Helicopter), RG (Rotorcraft Gyroplane), Glider, LA (Lighter Than Air Airship), LB (Lighter Than Air Balloon), Powered Lift, PL (Powered Parachute Land), PS (Powered Parachute Sea), WL (Weight Shift Control Land), WS (Weight Shift Control Sea), FFS (Full Flight Simulator), FTD (Flight Training Device), ATD (Aviation Training Device) |
GearType | Use one of the following codes: AM (Amphibian), FC (Fixed Tailwheel), FT (Fixed Tricycle), RC (Retractable Tailwheel), RT (Retractable Tricycle), Floats, Skids |
EngineType | Choose from: Diesel, Electric, Non-Powered, Piston, Radial, Turbofan, Turbojet, Turboprop, Turboshaft |
Complex | This is a true or false field. We suggest a simple ‘x’ if the airplane is complex. |
HighPerformance | This is a true or false field. We suggest a simple ‘x’ if the airplane is high-performance. |
Pressurized | This is a true or false field. We suggest a simple ‘x’ if the airplane is pressurized. |
FLIGHT TABLE FORMATTING
FIELD | FORMATTING NOTES |
---|---|
Date | The date of the flight in YYYY-MM-DD format. Example: 2002-01-02 |
AircraftID | The aircraft’s registration, of “tail number.” Example: N201TH |
From | The code for the departure airport. Example: KBVU |
To | The code for the destination airport. Example: KVGT |
Route | The points between departure and destination, separated by a space. Example: KCDC 67L |
TimeOut | Hours and minutes in 24-hour format. Example: 1823 |
TimeOff | Hours and minutes in 24-hour format. Example: 1823 |
TimeOn | Hours and minutes in 24-hour format. Example: 2137 |
TimeIn | Hours and minutes in 24-hour format. Example: 2137 |
OnDuty | Hours and minutes in 24-hour format. Example: 1700 |
OffDuty | Hours and minutes in 24-hour format. Example: 2200 |
TotalTime | Duration of flight in decimal format. Example: 3.6 |
PIC | Duration in decimal format. Example: 3.6 |
SIC | Duration in decimal format. Example: 0.0 |
Night | Duration in decimal format. Example: 1.2 |
Solo | Duration in decimal format. Example: 3.6 |
CrossCountry | Duration in decimal format. Example: 5.4 |
Distance | Nautical miles in decimal format: Example: 135.0. You have the option to use this field to track a total route distance or the distance to the furthest landing for training purposes. Whichever you choose, be consistent on all entries. |
DayTakeoffs | A whole number. Example: 2 |
DayLandingsFullStop | A whole number. Example: 2 |
NightTakeoffs | A whole number. Example: 1 |
NightLandingsFullStop | A whole number. Example: 1 |
AllLandings | The total number of landings. Example: 3 |
ActualInstrument | Duration in actual IMC in decimal format: Example: 1.8 |
SimulatedInstrument | Duration with a view limiting device, or “hood” in decimal format. Example: 0.0 |
HobbsStart | Aircraft Hobbs reading at beginning of flight: Example: 250.4 |
HobbsEnd | Aircraft Hobbs reading at end of flight: Example: 255.2 |
TachStart | Aircraft tachometer reading at beginning of flight: Example: 200.15 |
TachEnd | Aircraft tachometer reading at end of flight: Example: 204.42 |
Holds | A whole number. Example: 1 |
Approach1,2,... | The approach(es) you flew, with details separated by semicolons. The format expected is #;type;runway;airport;comments Choose from the following approach types: ASR/SRA, GCA, GLS, ILS, ILS CAT II, ILS CAT III, LDA, LOC, LOC BC, MLS, NDB, PAR, RNAV (GPS), RNAV (RNP), SDF, TACAN, VOR. Example: 1;ILS;12L;KVGT;Broke out at 350 AGL. |
DualGiven | Flight instruction you provided. Duration in decimal. Example: 0.0 |
DualReceived | Flight instruction provided to you. Duration in decimal. Example: 0.0 |
SimulatedFlight | Simulator time. Duration in decimal. Example: 0.0 |
GroundTraining | Ground training you received. Duration in decimal. Example: 0.0 |
InstructorName | First and last name. Example: Mark Wallace |
InstructorComments | Your instructor’s notes on the event: Example: “BAI, Unusual Attitudes, IFR lost comm procedures.” These may also be placed in the “PilotComments” field if you choose. |
Person1,2,... | Other people on board the aircraft with their role for that flight. Expected format is Name;Role;Email. Choose from the following roles: PIC, SIC, Instructor, Student, Safety Pilot, Examiner, Passenger. Example: Robert Hale;Student;Bob@example.com |
FlightReview | This is a true or false field. We suggest a simple ‘x’ if a flight review was conducted. |
CheckRide | This is a true or false field. We suggest a simple ‘x’ if a successful checkride occurred. |
IPC | This is a true or false field. We suggest a simple ‘x’ if an instrument proficency check was conducted. |
CustomFields | Custom Fields: If you need to carry over any custom fields, change the name and type of that field as appropriate. Choose from the following field types: Text, Numeric, Hours, Counter, Date, DateTime, or Toggle. Format: [FieldType]CustomFieldName. Example: [Hours]JumpPilot. |
PilotComments | This is a standard text field where you can place the contents of “Comments,” “Remarks,” or other similar fields from your logbook. Example “Instrument checkride - PASSED!” |
Last Updated: