FAQ

Q: Can I make a year in review?

Yes. Import a logbook with dates and another show, Year, joins Journey and Network in the panel’s Show row. It replays one year a month at a time: every flight in a month takes off together, a caption names it, and the lines stay up as the year fills in. It closes on a card of the flights, routes, airports and distance you flew.

Q: Which files can I import as a flown track?

A FlightAware "Export to Google Earth" KML, a GPX from your own logger, or a Flightradar24 per-flight CSV whose header has a Position column. KMZ is not read: unzip it and import the KML inside. One track per file, and the file is read in your browser and never uploaded. The track is drawn in grape and replaces your route list; an A-to-B track keeps the great circle it flew as a dashed reference, and the track card prints the distance actually flown, that great circle, and the difference between them. A round trip has no great circle, so it is drawn on its own.

Q: What is in the logbook CSV?

One row per leg with the day in front: date, route, from, to, bearing_deg, distance_km and count. The distance column follows the units you are working in, bearing_deg is that leg’s initial course, and count folds the day’s flights into the route’s own repeat. Export CSV sits beside the logbook line under Collections, in the panel’s Saved row. The file re-imports through Import CSV as routes.

Last updated: 9 September 2026

This page is about what goes into Voyarc (typed routes, CSV files of legs, flown-track files) and what comes back out in the logbook export. Every file is read in your browser and never uploaded.

How do I type a route list?

A route is three-letter IATA airport codes joined by dashes, and the box takes as many routes as you like:

SYD-LAX-JFK, SYD-LHR
MEL-PER
SYD-MEL x40

Routes are separated by a comma, a semicolon or a new line. Case does not matter: syd-mel is SYD-MEL.
Stops inside one route are separated by a hyphen, an en or em dash, a slash or a space: SYD-LAX-JFK, SYD/LAX/JFK and SYD LAX JFK are the same three-airport itinerary, drawn as two legs.
Direction is part of the route: SYD-MEL and MEL-SYD are two different routes.
The order you type them in is the order Voyarc flies them, and it picks the opening show: a list that reads as one trip, each leg starting where the last one landed, opens as a Journey. Anything else opens as a Network: an airline's routes, an airport's, or the same trip typed out of order. A flown track opens Race, or Trace if it lands where it took off.
A repeat count says how many times you flew it. Write it SYD-MEL x40; ×40, *40, (40) and [40] are read the same way, and the bracketed forms need no space. A bare x must not be glued to a code: SYD-LAX40 is a typo, not forty flights. The largest count is 9999.
The same route typed twice is one route with the counts added, so SYD-MEL, SYD-MEL is SYD-MEL x2.

A count changes the figures, not the picture: the map draws each route once and the show flies it once, while the totals count every flight.

If you do not know a code, the search box under the route box finds an airport by city or name, and picking a result adds its code to the end of the list.

Which CSV files can I import as routes?

Import CSV in the panel reads a table of flights and turns it into routes. Most spreadsheets already qualify; the first row decides how the file is read.

The one rule: a `from` column and a `to` column

Any CSV whose header names an origin column and a destination column imports. Origin is from, origin, dep, departure, orig, source or start; destination is to, dest, destination, arr, arrival or end. Every other column is ignored, so a file with too much in it costs nothing.

from,to,notes
SYD,MEL,commute
JFK,LHR,holiday

Three variations on the same file are read too:

A single route column named route, routes, path or itinerary, holding a whole itinerary (SYD-LHR or SYD LHR DXB), with an optional count column for how many times it was flown.
A headerless two-column file, where the first two cells of every row are airport codes and nothing else needs to be said.
Voyarc's own routes export, which is just a from/to file with extra columns: it carries a route column as well, and the from/to pair wins, because that is the leg the map drew.

A Flightradar24 "My Flights" export

The account export, unchanged: nineteen columns, every cell quoted. Voyarc reads three of them, From, To and Date. Airline, flight number, registration, aircraft, seat and the rest are ignored.

Date,Flight number,From,To,Dep time,Arr time,Duration,Airline,Aircraft,Registration,Seat number,Seat type,Flight class,Flight reason,Note,Dep_id,Arr_id,Airline_id,Aircraft_id
"2026-01-04","ZZ101","Sydney / Kingsford Smith (SYD/YSSY)","Melbourne / Tullamarine (MEL/YMML)","06:00:00","07:35:00","01:35:00","Nowhere Air (ZZ/ZZZ)","Boeing 737-800 (ZZ-ZZA)","ZZ-ZZA","12A","1","1","1","","3286","2452","0","B738"
"2026-01-06","ZZ202","Melbourne / Tullamarine (MEL/YMML)","Sydney / Kingsford Smith (SYD/YSSY)","17:00:00","18:30:00","01:30:00","Nowhere Air (ZZ/ZZZ)","Airbus A320-200 (ZZ-ZZB)","ZZ-ZZB","4C","2","1","1","","2452","3286","0","A320"

The sample rows are invented for illustration: the airline, flight numbers, registrations and times belong to no real operator or flight.

Nothing to import yet? Download the sample logbook: a whole file in this shape, three years of flying for an airline that does not exist, out of airports that do.

The rules that apply to all of them

The delimiter is detected from the first row: comma, semicolon or tab. A leading byte-order mark is ignored.
Quoted cells may hold the delimiter, a doubled "" for a literal quote, and a line break.
An ICAO code beside the IATA one is dropped: Sydney (SYD/YSSY), Sydney (SYD) and SYD all read as SYD.
A leg that appears on several rows becomes one route with a count on it.
A row with no pair of codes, or with a code we don't have an airport for, is skipped and named in the report under the route box.
One import maps at most 500 unique legs, on every tier: past that it is a database, not a map.
The free tier maps the first 25 unique legs of an import; Pro maps the whole logbook. Routes are never split: an itinerary longer than the cap still maps completely. See Pricing.

Repeats inside a CSV come from the file, not from the route box's x40 suffix, which is not read inside a cell. A count column carries them, and so does the same row appearing again. Five rows of MEL-SYD, or one row with a count of 5, fold into one leg marked ×5: one arc on the map, and one leg of the cap. Direction counts, so MEL-SYD and SYD-MEL are two legs.

Narrowing a logbook to one year

If your file has a date column (Date, Flight date, Departure date, Dep date, Departed, Flown, When or Year), Voyarc reads the date off each row. When a logbook spans more than one year the import report gains a Year picker: choose a year to map just those legs, or "All years" to bring the whole logbook back. Either way the file is already read, so there is nothing to import again.

The date stays in the panel: the year and the month feed the picker and the Year in review show. Your routes, the link you share and the map itself carry no dates. With Pro, Add to my logbook is the one thing that saves dates, and only when you press it.

Can I make a year in review?

Yes: import a logbook with dates and another show, Year, joins Journey and Network in the panel's Show row. It replays one year a month at a time. Every flight in a month takes off together, a caption names it, and the lines stay up as the year fills in. It closes on a card of the flights, routes, airports and distance you flew. The Guide's year in review section covers which year it picks and how long one runs.

With Pro you can file a dated import into your saved logbook and open that logbook on the map whenever you like, so the review runs again without the file.

Which files can I import as a flown track?

Track, in the panel's Map row, takes the path an aircraft actually flew and draws it in grape, replacing your route list. An A-to-B track keeps the great circle it flew as a dashed reference; a round trip is drawn on its own. One track per file: several track segments in one file are joined into a single line.

Files are read in your browser and never uploaded. Import only tracks you have the right to use: your own recordings, or exports whose terms allow it. Check your source's terms. Nothing here is for navigation.

A FlightAware "Google Earth" export

Open any flight's page on FlightAware and its track history offers Export to Google Earth. That link downloads a .kml file, and Voyarc reads it as it comes. There is nothing to convert.

Inside, the file is a <gx:Track> or a <LineString> in a Placemark. Airport pins (<Point> Placemarks) are ignored, so the map draws the flight and not a straight line between the two airports.

<Placemark><name>ZZZ101</name><gx:Track>
  <when>2026-08-22T05:17:53Z</when><gx:coord>151.17439 -33.94003 -38</gx:coord>
  <when>2026-08-22T05:20:19Z</when><gx:coord>151.20206 -34.01930 1257</gx:coord>
</gx:Track></Placemark>

KMZ is not read: it is a zipped KML, so unzip it and import the .kml inside. Any other KML with a <LineString> or a <gx:Track> works the same way.

GPX

The open standard: phone loggers, Flighty, ForeFlight and most trackers export it. Any GPX with a track works: the <trkpt> points are read in order, whichever way round their lat and lon attributes are written.

<trkseg>
  <trkpt lat="-33.946" lon="151.177"><ele>10</ele></trkpt>
  <trkpt lat="-33.500" lon="151.500"><ele>3600</ele></trkpt>
</trkseg>

A Flightradar24 flight CSV

The per-flight download from a flight's playback page (not the My Flights export above). The header must contain a Position column, and each position cell is a quoted "lat,lon" pair:

Timestamp,UTC,Callsign,Position,Altitude,Speed,Direction
1725000000,2026-08-30T08:00:00Z,ZZ101,"-33.946,151.177",0,0,0
1725000300,2026-08-30T08:05:00Z,ZZ101,"-33.500,151.500",12000,320,30

The sample snippets above are invented for illustration: the callsigns, times and positions belong to no real operator or flight.

What the comparison shows

The track card prints the distance actually flown, the great circle between the two nearest airports to its ends, and the difference between them in your units and as a percentage. Fly it as a Race and the two paths leave together at the same speed, so the longer real one lands later; Journey and Network fly the reference pair the import left in the route box, with the track drawn under it. A track that lands where it took off, or within a few kilometres of it, is a round trip with no great circle to race, so Voyarc picks Trace instead: it flies the flown path and draws it as it goes, with the camera held on the whole picture. The path we draw is a great circle; the distances beside it are measured on the WGS84 ellipsoid, the slightly flattened shape the earth really has.

FlightAware, Flightradar24, FR24, Flighty, ForeFlight and Google Earth are trademarks of their owners. Voyarc is not affiliated with or endorsed by them; their exports are read as files you already hold.

What is in the logbook CSV?

Export CSV sits beside the logbook line under Collections, in the panel's Saved row. The file is one row per leg, with the day in front:

date,route,from,to,bearing_deg,distance_km,count
2026-01-04,SYD-MEL,SYD,MEL,232,706,3
2026-03-15,SYD-KUL,SYD,KUL,298,6579,1

distance_km follows the units you are working in: it is distance_mi or distance_nm instead when you switch.
bearing_deg is the initial course of that leg, the same figure the legs table prints.
count is the day's count folded into the route's own repeat, so the file adds up to the flying it records.
The same routes logged twice on the same date are one entry with the counts added.
It re-imports through Import CSV as routes: it has both a route column and a from/to pair, and the pair is the leg that gets drawn.

What happens to my saved data if I cancel?

Your collections and logbook are kept for 30 days after a subscription ends. For those 30 days you can still open them, download the logbook as a CSV, and delete everything yourself from the panel. You just cannot add to them. After that the record is deleted automatically, and there is nothing left to restore; the details are in the Privacy Policy.

Questions this page does not answer: [email protected].

FAQ