How do I import a flight log from SkyDemon, ForeFlight or Garmin Pilot?
Kai reads the track file your flight app already produces and uses it to pre-fill a usage log.
Supported files: .kml (SkyDemon, ForeFlight) and .gpx (Garmin Pilot, ForeFlight), up to 10MB.
Importing on the web
- Open Usage Logs from the menu
- Click Log usage, then choose Import flight log
- If your group has more than one aircraft, pick the aircraft
- Drag the track file in, or click to select it
- Check the parsed times and airports in the preview
- Click Continue to usage log
- Add your meter readings, landings and any other fields your group requires
- Click Save usage log
Importing on mobile
On iPhone and iPad, Kai registers as a destination for .kml and .gpx files. Tap Share in ForeFlight, SkyDemon or Garmin Pilot, choose Kai, and the import screen opens directly. You can also open the import from the Usage Logs screen.
On Android, open Usage Logs and use the import icon to pick the file from your device.
What gets filled in automatically
- Block out and block in — the first and last point in the track
- Takeoff and landing — the first and last point more than 15 metres above the departure field's elevation, so taxi time is not counted as flight time
- Block time and flight time — in decimal hours
- Departure and arrival airports — the nearest airport to your first and last coordinates, as an ICAO code
- The route — the flown track, for the group's Flights Map
What you still enter yourself
- Hobbs and tach readings. A GPS track cannot see a meter, and these numbers drive your invoices and maintenance intervals, so Kai never guesses them.
- Landings, function and nature of flight
- Passengers and anyone sharing the cost
- Fuel, oil and landing fees
Nothing is saved until you press save. The import pre-fills the form, it does not file the log for you.
Troubleshooting
"Invalid file" — the file must end in .kml or .gpx. A screenshot or PDF of a flight log cannot be imported.
"Could not extract track data" — the file has no timestamped track. Export the track log or flight trace from your app rather than a route or flight plan, which has no times attached.
The source shows as "Unknown" — the file came from an app Kai does not recognise by name. This is harmless; everything else works the same as long as the track has timestamps.
The airport code looks wrong — airports are matched to the nearest field in Kai's airport database. For a private strip that is not listed, or two fields close together, correct the code before saving.
The file is too large — the limit is 10MB. The mobile apps trim the extra sensor data out of long tracks before uploading, so importing from your phone or tablet usually solves this.