CSV Template
Download the template below and follow the field instructions to ensure a successful import.
Download TemplateBefore 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_date | departure_airport | departure_time_utc | arrival_airport | arrival_time_utc | aircraft_make | aircraft_model | total_flight_time | pic_time | simulator_time | name_pic | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Flight | 2025-03-15 | LFPN | 09:00 | LFRK | 10:30 | Cessna | 172 | 1:30 | 1:30 | | SELF |
| Simulator | 2025-03-20 | | | | | | | | | 2:00 | |
Field Reference
Flight Details
Field:
flight_dateFormat: Date
Example:
2025-03-15Required: 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_airportFormat: ICAO or IATA
Example:
KJFK or JFKRequired: Yes
Description: ICAO (4-letter) or IATA (3-letter) airport code. Leave empty on simulator rows.
Field:
departure_time_utcFormat: HH:MM, UTC
Example:
14:30 or 14:30:00Required: 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_airportFormat: ICAO or IATA
Example:
KLAX or LAXRequired: Yes
Description: ICAO (4-letter) or IATA (3-letter) airport code. Leave empty on simulator rows.
Field:
arrival_time_utcFormat: HH:MM, UTC
Example:
17:45 or 17:45:00Required: 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_airportsFormat: ICAO or IATA
Example:
KORD,KDEN or ORD,DENRequired: No
Description: Comma-separated list of intermediate stops
Field:
flight_numberFormat: Text
Example:
UA123Required: No
Description: Flight number
Field:
operator_nameFormat: Text
Example:
United AirlinesRequired: No
Description: Operator/airline name
Aircraft
Field:
aircraft_registrationFormat: Text
Example:
N12345Required: No
Description: Recommended. Aircraft registration/tail number
Field:
aircraft_makeFormat: Text
Example:
CessnaRequired: No
Description: Recommended. Aircraft manufacturer
Field:
aircraft_modelFormat: Text
Example:
172Required: No
Description: Recommended. Aircraft model
Field:
aircraft_variantFormat: Text
Example:
SRequired: No
Description: Aircraft variant/series
Field:
aircraft_categoryFormat: airplane | sailplane | helicopter
Example:
airplaneRequired: No
Description: Aircraft category (auto-detected from make/model when blank)
Field:
aircraft_engine_typeFormat: piston | turboprop | jet | electric | not_applicable
Example:
pistonRequired: No
Description: Engine type (auto-detected from make/model when blank)
Simulator
Field:
simulator_timeFormat: Duration
Example:
2:00, 2:00:00, 2.0 or 2,0Required: 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_makeFormat: Text
Example:
CAERequired: No
Description: Simulator manufacturer
Field:
simulator_modelFormat: Text
Example:
7000XRRequired: No
Description: Simulator model
Flight Times
Field:
total_flight_timeFormat: Duration
Example:
1:30, 1:30:00, 1.5 or 1,5Required: 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_timeFormat: Duration
Example:
3.2 or 3:12Required: No
Description: Pilot in Command time
Field:
sic_timeFormat: Duration
Example:
1.5 or 1:30Required: No
Description: Second in Command time
Field:
dual_timeFormat: Duration
Example:
1.5 or 1:30Required: No
Description: Dual instruction received
Field:
instructor_timeFormat: Duration
Example:
1.5 or 1:30Required: No
Description: Flight instruction given
Field:
night_timeFormat: Duration
Example:
1.0 or 1:00Required: No
Description: Night flight time
Field:
ifr_timeFormat: Duration
Example:
2.0 or 2:00Required: No
Description: IFR flight time
Field:
actual_instrument_timeFormat: Duration
Example:
1.5 or 1:30Required: No
Description: Actual instrument conditions
Field:
simulated_instrument_timeFormat: Duration
Example:
0.5 or 0:30Required: No
Description: Hood or foggles time during a real flight. For time in a simulator device, use simulator_time.
Field:
cross_country_timeFormat: Duration
Example:
3.2 or 3:12Required: No
Description: Cross-country flight time
Crew Names
Field:
name_picFormat: SELF or name
Example:
SELFRequired: No
Description: Name of PIC. Write SELF for yourself. Any other text adds a crew member with that name.
Field:
name_sicFormat: SELF or name
Example:
Jane DoeRequired: No
Description: Name of SIC. Write SELF for yourself. Any other text adds a crew member with that name.
Field:
name_dualFormat: SELF or name
Example:
John SmithRequired: No
Description: Name of student (if dual). Write SELF for yourself. Any other text adds a crew member with that name.
Field:
name_instructorFormat: SELF or name
Example:
Captain JonesRequired: No
Description: Name of instructor. Write SELF for yourself. Any other text adds a crew member with that name.
Landings & Takeoffs
Field:
landings_dayFormat: Number
Example:
2Required: No
Description: Total day landings
Field:
landings_full_stop_dayFormat: Number
Example:
1Required: No
Description: Day full-stop landings
Field:
landings_nightFormat: Number
Example:
1Required: No
Description: Total night landings
Field:
landings_full_stop_nightFormat: Number
Example:
1Required: No
Description: Night full-stop landings
Field:
takeoffs_dayFormat: Number
Example:
2Required: No
Description: Day takeoffs
Field:
takeoffs_nightFormat: Number
Example:
1Required: No
Description: Night takeoffs
Approaches & Procedures
Field:
approachesFormat: Text
Example:
2 ILS, 1 VOR or ILS x2Required: No
Description: Approach types and counts (e.g., ILS, VOR, NDB, RNAV, LPV, Visual)
Field:
holding_proceduresFormat: Number
Example:
2Required: No
Description: Number of holding procedures
Field:
intercepting_tracking_coursesFormat: Number
Example:
6Required: No
Description: Number of intercepting and tracking courses (instrument currency)
Flight Flags
Field:
is_multi_pilotFormat: Boolean
Example:
true or yesRequired: No
Description: Multi-pilot operation
Field:
was_pilot_flyingFormat: Boolean (leave blank if N/A)
Example:
true, false, or blankRequired: No
Description: Pilot Flying role on multi-pilot operations. Leave blank when not applicable.
Field:
was_picusFormat: Boolean
Example:
true or yesRequired: No
Description: PIC Under Supervision
Field:
was_spicFormat: Boolean
Example:
true or yesRequired: No
Description: Student PIC
Field:
was_safety_pilotFormat: Boolean
Example:
true or yesRequired: No
Description: Acting as safety pilot
Field:
was_examinerFormat: Boolean
Example:
true or yesRequired: No
Description: Acting as examiner
Field:
was_checkrideFormat: Boolean
Example:
true or yesRequired: No
Description: Checkride/practical test
Field:
was_ipcFormat: Boolean
Example:
true or yesRequired: No
Description: Instrument Proficiency Check
Field:
was_soloFormat: Boolean
Example:
true or yesRequired: No
Description: Solo flight
Remarks
Field:
remarks_endorsementsFormat: Text
Example:
First solo XCRequired: No
Description: Remarks and endorsements