You can import multiple flights at once from a .CSV file created with Microsoft Excel (or other spreadsheet software).
Open Microsoft Excel (or a compatible app like Apple Numbers or Google Sheets) and create a new spreadsheet.
The first row of the spreadsheet is a header row that specifies which flight field corresponds to each column. For some fields, the header also indicates how the flight data in that column will be formatted. Each row after the first contains data for one flight.
Below are all the flight fields that can be imported. Note that only a few fields are required: Date, Departure airport and Arrival airport (or just Route on iOS), and Total duration. The rest are optional. Columns can be in any order.
Field | Header Text | Notes |
---|---|---|
Date | Date (m/d/yyyy) Date (yyyy-mm-dd) Date (dd.mm.yy) ... |
The header must specify the date format in parentheses. Use Examples: |
Flight number | Flight # | Example: DL777 |
Aircraft registration | Aircraft |
Aircraft registration or other identification. Example: |
Aircraft type | Aircraft Model | Example: C-172 |
Departure airport | From |
Airport code; supported types are: Examples: If Smart Logbook's airport database does not include an airport, or if there are multiple airports with the same code, add the type in parentheses to disambiguate: If multiple flights include ambiguous airport codes, you can specify the default code type in the header: For off-airport locations, enter the latitude and longitude in parentheses. Use degrees with decimals, with South latitudes and West longitudes as negative values. Example: |
Arrival airport | To | Same rules as the From column. |
Route | Route |
Multiple airport codes / locations, in order, separated by spaces or dashes. Examples:
If the From and To columns are populated, airports in this code are inserted between them as waypoint airports. If only the Route column is used, the first and last codes are used as the departure and arrival airport, respectively. |
Depart/Off time | Departed |
Use On Android, the header must specify whether times are Zulu/GMT or in the airport's local timezone. For Zulu times, add |
Arrive/On time | Arrived | Same rules as Departed column. |
Takeoff time | Takeoff Time | ... |
Landing time | Landing Time | ... |
Duty period start | Duty Start | ... |
Duty period end | Duty End | ... |
Flight duty period start | FDP Start | ... |
Flight duty period end | FDP End | ... |
Total flight duration | Total (hh:mm) Total (hh.t) |
On Android, the header must specify the duration format, either hours and minutes On iOS, you can use
|
Additional durations | Solo (duration) Night (duration) ... |
Add a column for each type of duration. In the header, enter the name of the duration field followed by The available duration fields can be found (and customized) in settings:
|
Takeoffs (day) | Takeoffs (day) | |
Takeoffs (night) | Takeoffs (night) | |
Landings (day) | Landings (day) | |
Landings (night) | Landings (night) | |
Aerotows | Aerotows | |
Powered launches | Powered Launches | |
Ground launches | Ground Launches | |
Approaches | Approaches Approaches (2) Approaches (3) ... |
Number of approaches of a specific type. An additional column, Approach Type, must be added to indicate the type of approach. If any flight contains approaches of different types, add extra Approaches and Approach Types columns with a number in parentheses. |
Approach type | Approach Type |
Specifies the type of the approach.
Examples:
You can optionally add a semicolon, followed by notes after the approach type. Example: The available approach types can be found (and customized) in settings:
|
Holding procedures | Holds | Number of holding procedures. |
Crew members | PIC/Captain (crew) FO/Copilot (crew) Student (crew) ... |
Add a column for each crew position. If any flight has multiple crew members in the same position (e.g. In each flight row, enter the crew member's name as either The available crew positions can be found (and customized) in settings:
|
Remarks | Remarks | |
Distance | Distance (NM) | |
Passengers | Passengers | |
Simulator | Simulator |
Indicates if a row represents a simulator session. Examples:
|
Custom fields | IMC (yes/no) Missed approaches (number) Rate (decimal) Weather (text) ... |
Add a column for each custom field. In the header, enter the name of the field followed by its type:
Custom fields can be added in settings:
|
To see examples of some of these, download the Excel import template:
This template can be used as a starting point for creating your own import file. Just delete the example flights and update columns as needed.
Smart Logbook cannot import an Excel spreadsheet file (.xlsx) directly. Instead, you must first convert your spreadsheet to a .CSV file.
Use any method you like to transfer the .CSV file to your phone or tablet. For example, you can:
If the import succeeds, the flights are added to your logbook. However, they aren't permanently committed until you verify that they are correct.
If there are problems with your .CSV file, a screen appears that describes the problems and where in the file they are located. If there are only warnings (e.g. unknown fields), you can tap Import to continue and import the flights anyway. If there are errors (e.g. required fields missing), you must correct the problems and then try the import again.
If you get stuck and need assistance, just email us at feedback@thesmartlogbook.com and we'll be happy to help you!
© 2024 Kviation, Inc.