Somewhere out there is a complete list of every flight you've ever taken. The problem is that nobody kept it in one place — not you, not the airlines, not any app. It's scattered across frequent flyer accounts, ten years of email, old calendars, a Flightradar24 profile you half-remember making, and credit card statements from banks you no longer use.
The good news: almost all of it is recoverable, and the recovering is weirdly satisfying. This guide walks through every source we know of, roughly in order of effort-to-payoff, and by the end you'll have a list that's as close to complete as anyone can get without subpoena power. People who do this regularly turn up flights they'd completely forgotten — a redeye from 2013, a puddle-jumper on a family trip, that one diversion that turned a two-leg day into three.
A note on method before we start: work source by source and dump everything into one running list (a spreadsheet with date, flight number, origin, destination is plenty — flight number and date alone are usually enough to reconstruct the rest). Don't try to dedupe as you go; overlap between sources is actually useful, because agreement between your email and your frequent flyer statement is how you confirm the details. Dedupe once at the end.
And a note on why we wrote this: Row1 turns your real flights into a game: import your flight history from Flighty, Flightradar24, or your calendar, earn XP, collect 304 badges, and share an animated 3D-globe Wrapped video of your year in the sky. Every source below feeds that import. But the guide stands on its own — your flight history is worth having, whatever you do with it.
Four columns: date, flight number, origin, destination. Everything else — aircraft type, distance, seat — can be reconstructed later from those four, and Row1 does that reconstruction automatically on import.
Two rules. First, don't dedupe as you go; you'll use the overlap to confirm details at the end. Second, don't stop to research individual flights mid-sweep — capture, move on, reconcile later.
Time budget: one to three hours for most people. If you've been flying weekly since the nineties, give it an afternoon and a beverage.
Every loyalty program keeps an activity ledger, and every mileage-earning flight appears in it with a date and usually a flight number. This is the closest thing to an official record you have access to.
Log in, find the activity or statement history, and page back as far as the site will let you. Screenshot or export as you go — some sites paginate badly and you don't want to do this twice.
History depth varies wildly by program: some show everything back to your enrollment date, others only a few years. Flights you credited to a partner program live in that program's ledger — if you flew one airline but banked the miles elsewhere, check the program that got the miles. Award tickets sometimes appear as redemptions without flight details, so cross-check those against email. And flights taken before you joined the program are invisible here entirely — that's what the other sources are for.
When programs merge, the surviving program usually inherits the ledger. If you flew an airline that no longer exists, log into the successor's program (or the program it merged into) and look for imported activity. It's there more often than you'd expect.
If you've had the same email address for a while, your inbox is the closest thing to a complete record that exists. Airlines have been sending confirmation emails since before online check-in existed.
Work through these in Gmail (adapt for other providers), and save each hit to the list:
TripIt's email import will parse years of confirmation emails into structured trips in one pass. Even if you never intend to use TripIt again, it's a fast extraction tool: connect the inbox, let it chew, export the result.
The college address, the account at the old job, the ISP address from the 2000s. Even read-only access to an old inbox is a goldmine — one search of a dormant account can fill in half a decade.
Booking emails also feed Row1 directly: forward them to your import address and they become logged flights.
If you ever logged flights on myFlightradar24, you're sitting on the single cleanest import file there is: your history exports as a CSV with dates, flight numbers, and routes already structured.
Log in on the web, go to your account settings, and look for the export option. The CSV contains everything Row1 needs — import it and badges are awarded retroactively for your whole history at once, which is a genuinely great thirty seconds.
Anyone who has synced bookings, used a work calendar, or accepted a TripIt or Concur calendar feed has flights sitting in old events they've forgotten about.
Search Google Calendar and Apple Calendar — across all past years, not the default view — for flight numbers, airport codes, and words like "depart," "flight," and "boarding." Check secondary calendars too: the work calendar, the shared family one, and any subscribed feeds; travel events love to hide in calendars you stopped looking at.
Work travel deserves a special mention: if you've changed jobs, the corporate booking tool's confirmations are gone with the old email address, but the calendar entries they created often synced to your personal calendar and survived.
This is also the laziest source to use with Row1 — it reads flights straight out of your calendar, so this layer often needs no manual transcription at all.
Statements won't give you flight numbers, but they prove a purchase happened, which makes them the backstop for everything the other sources missed.
Search downloadable statements for airline merchant names, ticket-number-like descriptors (airlines often encode ticket numbers in the transaction line), and foreign-transaction fees, which flag international trips even when the airline charge itself is ambiguous. How far back you can go depends on your issuer's online archive — check yours, and know that older statements can often be requested.
Turning a charge into a flight is a matching game: take the charge date, then look for the trip in email, calendar, or your own memory. A charge you can't match to anything is usually a canceled trip — or a flight you'll be delighted to remember.
For the pre-digital years: physical boarding passes, old passport stamps, and your photo library.
Search your photos for "airport," "airplane," and "boarding pass" — modern photo search is shockingly good at this — and use the location and timestamp metadata to pin down travel dates when nothing else survives. A gate photo with GPS coordinates is a flight record, just an informal one.
Realistic framing: this layer is for the last five percent. It's also the fun part.
If you used App in the Air and exported your data before the 2024 shutdown, keep that file safe. If you didn't, everything above reconstructs the same data — the app was only ever aggregating your email, your inputs, and your bookings, and those sources still exist. We wrote more about the shutdown and what replaced the game layer in our App in the Air comparison.
Now the dedupe pass: sort the master list by date, merge rows where two sources describe the same flight, and resolve conflicts in favor of the frequent flyer ledger — it's the operational record. What "done" looks like: a dated list of every flight you can evidence, which you will never have to rebuild again.
A spreadsheet is a fine trophy, but it doesn't do anything. Import the list into Row1 — Flighty export, Flightradar24 CSV, calendar scan, or forwarded booking emails — and years of badges unlock at once, your lifetime map draws itself, and the app renders your whole flying life as an animated Wrapped globe. Free on the App Store: row1.app.
Realistically, as far back as your oldest surviving email account or frequent flyer ledger — for most people that's 10-20 years. Before that, it's passport stamps, photos, and memory.
The activity ledger in your own frequent flyer account is usually the practical limit. Formal personal-data requests exist in some jurisdictions and sometimes surface more, but responses vary widely by airline.
A myFlightradar24 CSV export, if you have one — it's structured and complete. Otherwise, your frequent flyer accounts.
Frequent flyer ledgers (some go back decades), passport stamps, physical boarding passes, and photo-library metadata. That's also the order to try them in.
Calendar, forwarded booking emails, Flighty exports, and Flightradar24 CSVs import automatically, and badges are awarded retroactively. The shoebox layer is manual entry — but by then it's a short list.