How to use this
Drop in a flight log — or several at once to compare — and Debrief reads each into one clean flight: the headline numbers and the curves that matter, with liftoff, burnout, apogee and the deployments marked on them. It auto-detects the loggers it knows and falls back to a column mapper for anything else, so any logger that exports a CSV works. Everything runs in your browser — files never leave your device.
- Compare — drop several files at once, or open Compare and tick flights in your logbook, to overlay their curves and line up the numbers side by side. A comparison lives at its own address, so it survives a reload and can be bookmarked or kept in a second tab beside a single flight's report — built from the logbook it starts there, and one built from a drop is one click from it (Give this comparison an address; the link names the flights by their logbook id and carries no flight data). Click any metric in that table to order the flights by it — highest first, then lowest — or move a column with ◀ ▶ into an order no metric gives you (booster then sustainer, flight 1 to 6), or move a reading up and down the table in Choose what's in this report so the comparison leads with what you care about (Choose what's in this comparison). The chart legend and every export follow whichever order you set, and the channel you were last looking at (altitude, velocity, Mach…) is the one the next comparison opens on. Anything in the drop Debrief couldn't read is named, with the reason — even when only one file survives and you get a single report instead. Drop a logger's summary file alongside its log and the device's own figures appear beside Debrief's read as a cross-check.
- Explore — plot any channel the logger recorded, against time or one against another, alongside Debrief's own Mach and dynamic-pressure channels, then save the plot or its data. Open Show the samples to read the exact values behind the curve — the table follows the chart's zoom, and Jump to takes you straight to the row for liftoff, burnout, apogee or a deployment instead of scrolling for it. However you set the plot up is remembered, so the next flight opens the way you left it — and + Save this view keeps several under names you choose (the boost, the deployments, the airframe's health) to switch between on any flight that has those channels.
- Report — a report is written for a purpose, so pick the readings it carries: open Choose what's in this report and turn off what this one doesn't need (a cert package wants apogee, speeds and descent rates; a drag study wants coast efficiency and max Q). The choice applies on screen and to the .txt, .md and .html reports and the bundle — made once, not once per format — and is remembered on this device. The data exports (.csv, .json) always carry everything: a report is a document, a data file is a record. Copy table puts the readings straight on the clipboard — they land in cells in a spreadsheet or a document, and as tab-separated text anywhere else — so the club sheet or the cert package doesn't need a round trip through a saved file. The comparison has the same button — and the same chooser, working off the same choice, so what you care about is answered once rather than once per screen.
- Units — switch feet and meters with one click (top-right), or open per quantity to set each on its own: altitude in feet with speed in mph or km/h, acceleration in g or m/s², temperature in °F or °C. It applies to every number, chart and export, is remembered on this device, and rides in the URL — so a link opens reading the way you sent it.
- Share & keep — copy a link with the whole flight encoded inside it, or let the logbook remember recent flights on this device — both stay on your machine. Once a season's worth has built up, search the logbook by file name, the logger it came off, the note you wrote on it (motor, conditions, cert) or the launch day, and sort by launch day, apogee or top speed. Where a file states when it flew — a GPS's UTC, or a Blue Raven's own clock — that's the date the report and the logbook show, not when you opened it.
- Offline — install it to your home screen; one visit with signal is enough, and after that it works with none, right at the field — the compare page included, along with the methods and validation pages, so “what does this number mean?” is answerable with no bars.
Drop a flight log here
CSV, text, or Excel export from your altimeter — or any logger's CSV or spreadsheet. Drop several at once, or a whole launch day's folder, to compare them — anywhere on the page.
or see what else it reads: · · SYNTHETIC — a flight Debrief made up, not a recording · SYNTHETIC — a flight Debrief made up, not a recording · SYNTHETIC — a flight Debrief made up, not a recording · SYNTHETIC — a flight Debrief made up, not a recording
Your file is read in this browser and never uploaded — parsing and analysis happen entirely on your device.
What you can do here that your altimeter's own software can't
Reads every board, not just the one that made it
Ten logger families are auto-detected from the file itself, and anything else — any CSV or spreadsheet — works through a column mapper that remembers the mapping.
Puts two altimeters side by side, even from different makers
Flew redundant boards? Their readings sit beside each other as independent measurements, with the disagreement shown rather than averaged away. Agreement is confidence; a gap is worth chasing.
Reads a staged launch as a staged launch
Each stage keeps its own apogee, speed and burn, on one shared clock, from the logs you already have. Nothing is combined into a single number — a composite adds order, not readings.
Nothing uploaded, nothing installed, nothing paid for
Your file is read in this browser and never leaves the device. Once opened it works with no signal, so it works at the range.
Recognized loggers
- Altus Metrum (AltOS)
- PerfectFlite (StratoLogger / Pnut)
- Eggtimer
- Featherweight (Raven · Blue Raven · GPS)
- Entacore AIM
- MissileWorks RRC3 (mDACS)
- Rocketry Ltd Mercury (AltimeterCloud)
Auto-detected from the file, including the raw download straight off the card for Altus Metrum (.eeprom) and MissileWorks RRC3 (.rff) — no CSV export needed first. Anything else — any logger that exports a CSV or an Excel spreadsheet — works through a quick column mapper. Ask for a logger that isn't here.
Looking for flights remembered on this device…
Where the numbers come from
Debrief is a measurement instrument, not a simulator: every number is a reading of your own recording, worked out the same way for every logger and labelled wherever it's derived or approximate. See exactly how each one — apogee, velocity, thrust-to-weight, drag and parachute Cd, recovery drift and the rest — is calculated, and where it can be wrong.