Skip to main content

CSV Template

Download the template below and follow the field instructions to ensure a successful import.

Download Template

Before you import

  • Keep the header names exactly as they are in the template.
  • Comma, semicolon or tab separators all work, so a file saved from Excel or Numbers in a European locale imports fine.
  • "Required" means the column must be in the header row. On simulator rows, leave the airports and total_flight_time empty.
  • Each row needs at least one time: total_flight_time, a role time or simulator_time.
  • Enter all times in UTC, not local time.

Example

One flight and one simulator session, with only the columns that matter here.

flight_datedeparture_airportdeparture_time_utcarrival_airportarrival_time_utcaircraft_makeaircraft_modeltotal_flight_timepic_timesimulator_timename_pic
Flight2025-03-15LFPN09:00LFRK10:30Cessna1721:301:30SELF
Simulator2025-03-202:00

Field Reference

Flight Details

Field: flight_date
Format: Date
Example: 2025-03-15
Required: Yes
Description: Date of the flight. 2025-03-15 is the safe choice. Also accepted: 2025/03/15, 15/03/2025, 15.03.2025, 15-03-2025 and US 03/15/2025. Two-digit years work with slashes and dots. Skyden reads the whole file to tell day-first from month-first, and asks you when it cannot tell.
Field: departure_airport
Format: ICAO or IATA
Example: KJFK or JFK
Required: Yes
Description: ICAO (4-letter) or IATA (3-letter) airport code. Leave empty on simulator rows.
Field: departure_time_utc
Format: HH:MM, UTC
Example: 14:30 or 14:30:00
Required: No
Description: Recommended. Departure time in UTC, 24-hour clock. Do not enter local time: it shifts every flight by your UTC offset.
Field: arrival_airport
Format: ICAO or IATA
Example: KLAX or LAX
Required: Yes
Description: ICAO (4-letter) or IATA (3-letter) airport code. Leave empty on simulator rows.
Field: arrival_time_utc
Format: HH:MM, UTC
Example: 17:45 or 17:45:00
Required: No
Description: Recommended. Arrival time in UTC, 24-hour clock. Do not enter local time: it shifts every flight by your UTC offset.
Field: stop_airports
Format: ICAO or IATA
Example: KORD,KDEN or ORD,DEN
Required: No
Description: Comma-separated list of intermediate stops
Field: flight_number
Format: Text
Example: UA123
Required: No
Description: Flight number
Field: operator_name
Format: Text
Example: United Airlines
Required: No
Description: Operator/airline name

Aircraft

Field: aircraft_registration
Format: Text
Example: N12345
Required: No
Description: Recommended. Aircraft registration/tail number
Field: aircraft_make
Format: Text
Example: Cessna
Required: No
Description: Recommended. Aircraft manufacturer
Field: aircraft_model
Format: Text
Example: 172
Required: No
Description: Recommended. Aircraft model
Field: aircraft_variant
Format: Text
Example: S
Required: No
Description: Aircraft variant/series
Field: aircraft_category
Format: airplane | sailplane | helicopter
Example: airplane
Required: No
Description: Aircraft category (auto-detected from make/model when blank)
Field: aircraft_engine_type
Format: piston | turboprop | jet | electric | not_applicable
Example: piston
Required: No
Description: Engine type (auto-detected from make/model when blank)

Simulator

Field: simulator_time
Format: Duration
Example: 2:00, 2:00:00, 2.0 or 2,0
Required: No
Description: Time in a simulator device (FNPT, FFS). Filling it makes the row a simulator session: leave total_flight_time and both airports empty. For hood or foggles time in a real aircraft, use simulated_instrument_time.
Field: simulator_make
Format: Text
Example: CAE
Required: No
Description: Simulator manufacturer
Field: simulator_model
Format: Text
Example: 7000XR
Required: No
Description: Simulator model

Flight Times

Field: total_flight_time
Format: Duration
Example: 1:30, 1:30:00, 1.5 or 1,5
Required: Yes
Description: Total flight time. Leave empty on simulator rows. Each row needs at least one time: total_flight_time, a role time (PIC, SIC, dual, instructor) or simulator_time.
Field: pic_time
Format: Duration
Example: 3.2 or 3:12
Required: No
Description: Pilot in Command time
Field: sic_time
Format: Duration
Example: 1.5 or 1:30
Required: No
Description: Second in Command time
Field: dual_time
Format: Duration
Example: 1.5 or 1:30
Required: No
Description: Dual instruction received
Field: instructor_time
Format: Duration
Example: 1.5 or 1:30
Required: No
Description: Flight instruction given
Field: night_time
Format: Duration
Example: 1.0 or 1:00
Required: No
Description: Night flight time
Field: ifr_time
Format: Duration
Example: 2.0 or 2:00
Required: No
Description: IFR flight time
Field: actual_instrument_time
Format: Duration
Example: 1.5 or 1:30
Required: No
Description: Actual instrument conditions
Field: simulated_instrument_time
Format: Duration
Example: 0.5 or 0:30
Required: No
Description: Hood or foggles time during a real flight. For time in a simulator device, use simulator_time.
Field: cross_country_time
Format: Duration
Example: 3.2 or 3:12
Required: No
Description: Cross-country flight time

Crew Names

Field: name_pic
Format: SELF or name
Example: SELF
Required: No
Description: Name of PIC. Write SELF for yourself. Any other text adds a crew member with that name.
Field: name_sic
Format: SELF or name
Example: Jane Doe
Required: No
Description: Name of SIC. Write SELF for yourself. Any other text adds a crew member with that name.
Field: name_dual
Format: SELF or name
Example: John Smith
Required: No
Description: Name of student (if dual). Write SELF for yourself. Any other text adds a crew member with that name.
Field: name_instructor
Format: SELF or name
Example: Captain Jones
Required: No
Description: Name of instructor. Write SELF for yourself. Any other text adds a crew member with that name.

Landings & Takeoffs

Field: landings_day
Format: Number
Example: 2
Required: No
Description: Total day landings
Field: landings_full_stop_day
Format: Number
Example: 1
Required: No
Description: Day full-stop landings
Field: landings_night
Format: Number
Example: 1
Required: No
Description: Total night landings
Field: landings_full_stop_night
Format: Number
Example: 1
Required: No
Description: Night full-stop landings
Field: takeoffs_day
Format: Number
Example: 2
Required: No
Description: Day takeoffs
Field: takeoffs_night
Format: Number
Example: 1
Required: No
Description: Night takeoffs

Approaches & Procedures

Field: approaches
Format: Text
Example: 2 ILS, 1 VOR or ILS x2
Required: No
Description: Approach types and counts (e.g., ILS, VOR, NDB, RNAV, LPV, Visual)
Field: holding_procedures
Format: Number
Example: 2
Required: No
Description: Number of holding procedures
Field: intercepting_tracking_courses
Format: Number
Example: 6
Required: No
Description: Number of intercepting and tracking courses (instrument currency)

Flight Flags

Field: is_multi_pilot
Format: Boolean
Example: true or yes
Required: No
Description: Multi-pilot operation
Field: was_pilot_flying
Format: Boolean (leave blank if N/A)
Example: true, false, or blank
Required: No
Description: Pilot Flying role on multi-pilot operations. Leave blank when not applicable.
Field: was_picus
Format: Boolean
Example: true or yes
Required: No
Description: PIC Under Supervision
Field: was_spic
Format: Boolean
Example: true or yes
Required: No
Description: Student PIC
Field: was_safety_pilot
Format: Boolean
Example: true or yes
Required: No
Description: Acting as safety pilot
Field: was_examiner
Format: Boolean
Example: true or yes
Required: No
Description: Acting as examiner
Field: was_checkride
Format: Boolean
Example: true or yes
Required: No
Description: Checkride/practical test
Field: was_ipc
Format: Boolean
Example: true or yes
Required: No
Description: Instrument Proficiency Check
Field: was_solo
Format: Boolean
Example: true or yes
Required: No
Description: Solo flight

Remarks

Field: remarks_endorsements
Format: Text
Example: First solo XC
Required: No
Description: Remarks and endorsements