Flight Report
ExperimentalGet a Post-Flight Summary Without Leaving the Field
After a flight, you want to know what happened. How high did it go? How fast? Did the chutes deploy where you expected? AltosUI generates a formatted flight report directly on your phone — no laptop needed, no file transfers, no waiting until you get home. Long-press a tracker and get the story of that flight.
An At-a-Glance Field Summary
Flight Report is a field summary, not a replacement for desktop analysis. Think of post-flight analysis as three progressively richer tiers:
- In the field — iOS Flight Report. Headline numbers, phase timeline, motor, aero, apogee, recovery, stability, GPS drift, signal quality, and an inline altitude chart — right after touchdown, on the phone already in your hand. This is what the feature is for.
- Anywhere later — AltosUI desktop opening the same
.telemfile. Zoomable multi-channel plots, map with GPS track overlay, richer statistical tables, CSV export for spreadsheets, KML export for Google Earth — from the same ground-station capture the iOS report analyzes. No cable, no rocket recovery required: the.telemfile is exposed through the iOS Files app, so you can AirDrop or email it straight to a laptop. - After recovery — AltosUI desktop opening the
.eepromfile. The.eepromis the onboard flight-computer log pulled off the altimeter over USB, and it's categorically richer than radio telemetry: lossless, full 32-bit precision, 100 Hz throughout the flight, with raw sensor channels — MS5607 baro, high-G accelerometer, full IMU accel / gyro / mag — that don't fit in a 32-byte radio packet. This is the source for a true thrust curve, transonic diagnostics, and record-quality analysis.
The biggest single difference shows up during descent. Radio telemetry runs at 10 Hz through boost and coast, then drops to 1 Hz at drogue deploy. The onboard log keeps writing at 100 Hz until touchdown — roughly 100× more samples through the descent phase, and the natural source for drogue descent rate, main-opening shock, and any post-apogee diagnostic work. The report itself points all of this out, right at the top, so nobody has to guess which tool to reach for next.
The goal of the on-device report is simple: know the numbers while you're still in the field — whether you've just walked back from recovery or you're watching the next flight with friends. Every report is fully self-contained HTML, including the altitude chart — no network required, it works anywhere your phone does.
Two Tiers of Detail on the Phone
Within the iOS report itself there are two levels of depth. Every report delivers at least a summary tier pulled from live tracker metadata: flight identity, peak performance, GPS drift.
When the .telem file captured by your TeleBT ground station is on the device — automatic for live flights, inherent for replayed or imported files — the report adds a deep analysis pass over the full packet stream: phase timing, motor, aero, apogee, stability, recovery, signal quality, and rule-based advisories.
What You'll See
The report is a single scrollable document. Sections appear in this order:
Advisory Banner — Always at the top: labels the report as estimation from radio telemetry and invites user feedback via an email link.
Signal Loss Warning — Only for flights where telemetry was truncated before landing. Tells you the capture was incomplete and that values are from signal loss, not touchdown.
Flight Information — Date, callsign, rocket serial number, device type, flight number, final flight state, and ground station serial.
Flight Performance — Max height, max speed (with Mach), and max acceleration (with G).
GPS & Drift — Pad location, landing location (or "Last Known Position" for truncated captures), drift distance and bearing.
High-Altitude Warning — For flights above ~30 km, a banner flags the barometric sensor ceiling and notes that altitude data is Kalman-estimated.
Altitude Profile Chart — Inline SVG chart of height vs. time with phase-transition markers. For high-altitude flights: solid trace below the baro ceiling, dashed trace above. For truncated captures: a "Signal Lost" marker at the right edge. The chart auto-scales to show only the active flight, not post-landing flat-line.
Flight Timeline — Time, height, and speed at each phase transition (boost, fast, coast, drogue, main, landed).
Motor Performance — Burn time, peak and average acceleration, burnout speed, and burnout altitude.
Aerodynamic Deceleration — Entry and exit speeds, speed lost to drag, and peak drag deceleration.
Apogee — Apogee altitude, time to apogee, coast duration, and drogue deploy gap.
Stability — Off-rod tilt and max boost tilt. IMU-equipped devices only (TeleMega, EasyMega).
Recovery System — Drogue and main deployment altitudes, descent rates, and landing speed.
Signal Quality — Total, valid, and invalid packet counts with per-type breakdown.
Observations & Recommendations — Rule-based advisories covering descent rate, landing speed, deploy altitude, G-loading, Mach, tilt, and signal quality, with a cross-check disclaimer.
When values aren't available, the report says why (e.g., "no GPS lock before launch", "no speed data in telemetry") rather than showing unexplained dashes.
How to Use It
Three ways to get a report:
- Long-press a tracker on the Map or Recover tab → Flight Report
- From the Files app → tap a
.telemfile → Quick Look preview → Share → Open with AltosUI - From the Files app → long-press a
.telemfile → Open with… → AltosUI
Works with any .telem file — live flights, iCloud Drive, AirDrop. No import step, no setup.
Export
The Share button exports a paginated PDF — proper letter-size pages with margins and tables that don't split across page breaks. The on-screen view stays a continuous scrollable document.
The feedback email link in the banner opens Mail with the PDF attached, pre-addressed to the development team, with a prompt for your feedback.
Desktop Consistency
The iOS analyzer was audited against AltosUI desktop's algorithms to ensure .telem estimates don't surprise users when they compare against .eeprom analysis. Max speed and max acceleration are restricted to the boost phase (matching the desktop convention), descent-rate formulas handle elevation differences, and GPS positions require 4+ satellites. You should see numbers in the same ballpark — not identical (different data sources), but consistent conclusions.
When It Works Best
Right after a flight — walking back from recovery, or between flights with friends. The data is fresh, everyone wants to know the numbers, and you can share the report immediately. No more scribbling max altitude on a notepad or trying to remember the numbers later.
It's also useful for flight logging. Export a PDF for each flight and you'll build an archive over the season — motor performance trends, chute descent rates, drift patterns for your regular launch site. For record attempts or authoritative motor analysis, feed the .eeprom file from the recovered altimeter to AltosUI on desktop — that's the canonical source, and the iOS report is explicitly not a substitute for it.
What You Need
- A flight received by AltosUI — the summary tier works from live tracker metadata alone
- The associated
.telemfile on the device for the deep-analysis sections (saved automatically during live flights; inherent for replayed or imported files)
Compatibility:
- TeleMega v1–v7 — full report including IMU stability
- TeleMetrum v1–v4 — full report; no stability (no IMU)
- TeleMini v2–v3 — baro-only flight detail (no accelerometer-derived motor stats, no GPS drift)
- TeleGPS v1–v4 — GPS-focused summary; no Kalman-filter phase analysis
- EasyMega v1–v3 — deep analysis including stability when telemetry is captured
What's Coming Next
- Flight-to-flight comparison — multiple flights of the same rocket, with trend detection
- iOS vs. AltosDroid side-by-side comparison
- Temperature and atmospheric pressure profile plots
- Spin rate from gyro data
This feature is experimental and being actively refined based on field testing. We'd value your input on what flight data matters most to you at the launch site.