Private beta · flight-log analysis for DJI operators
Your DJI logs,
turned into answers.
Upload your original DJI TXT flight records. Flymetry builds searchable flight records, links aircraft, pilots and batteries by serial number, and shows the available cell-level telemetry — every value traceable back to the original file.
Available fields vary by log, aircraft, app version and whether encrypted sections could be decrypted.
Built in Sweden. Designed with data control in mind. How
Illustrative example · synthetic data
Logs stop being files. They become records.
Pilots drag in their original DJI TXT logs. Each file is decoded where the format and available keys allow, fingerprinted with SHA-256 and kept byte-exact — duplicates are caught, gaps stay visible, and every number traces back to its source record.
- Input
- Original DJI TXT logs
- Fingerprint
- SHA-256 per file
- Duplicates
- Caught per organisation
- Export
- CSV + byte-exact original
Import · 3 files
uploading
uploading
uploading
Originals kept byte-exact · duplicates caught within the organisation
Altitude · log reference
Duration
—
Max alt
—
Aircraft
—
Battery
—
Illustrative example · synthetic data · click any stage
Aircraft, pilots and batteries — connected by serial number.
An exact UAV serial links each log to its registered system. Unknown aircraft surface as suggestions for an administrator to review, and a battery seen on several systems keeps one shared observed history.
- Matching
- Exact UAV serial
- Unknown aircraft
- Suggested for review
- Cycle counters
- Read, never summed
- Roles
- Admin and pilot
BAT ··· 0217 — seen on two systems · one shared observed history
Illustrative example · synthetic data · serials truncated
See what the pack recorded — down to the cell, where the log has it.
Cell balance, temperature, charge, current and BMS-reported capacity — when the log contains them — in context. Watch a flight replay, pick another battery, or scrub the timeline yourself.
Observed batteries
- Systems
- System A · System B
- First seen
- 2026-03-02
- Last seen
- 2026-10-21
- History scope
- Imported logs only
Cell 1
3.832 V
Cell 2
3.822 V
Cell 3
3.839 V
Cell 4
3.793 V
Pack temp
25.6 °C
Time
7.3 min
Δ cells
46 mV
Charge
53 %
Current
7.5 A
Temp
26 °C
Illustrative example · synthetic data · gaps are shown, never interpolated
Missing
is never zero
Gaps are not filled with invented data.
≥ 3 days
for a capacity trend
With at least three comparable pairs.
≥ 120 s
for a benchmark
With 85% coverage and real cell records.
No score
no fit-to-fly verdict
No health score or remaining-life prediction.
Want to see this with your own fleet's logs?
Join the private betaYour logs. Your call on every key request.
Logs are decoded on the server. DJI key retrieval is blocked by default and can only be allowed per organisation — never silently.
Full data-control policy+
| Control | Behaviour | Condition |
|---|---|---|
| Default policy | DJI key requests blocked in the backend | Encrypted telemetry without local keys stays locked |
| Per organisation | Automatic key retrieval can be allowed | Only at import or explicit retry |
| Strict server mode | Overrides the organisation's choice | Server block cannot be lifted by an org setting |
| Key cache | AES-256-GCM, bound to org and file hash | Master key lives in the same server environment |
| Originals | Stored byte-exact with SHA-256 | A fingerprint, not a signature |
| Network | Not fully isolated | Optional Mapbox map tiles make external requests |
When retrieval is enabled, a restricted key request is sent — not the TXT file or explicit coordinate fields. DJI still receives the server IP and request time. Strict-local mode is not full network isolation. Security details
What exists today, and what's planned.
Developed against real DJI logs, but support is not universal. Logs reviewed so far include Mini 2, Avata, Matrice 30 and Mavic 3 Enterprise / M3T; available fields vary by aircraft, app version and decryption. Place names and the overview map are Sweden-oriented.
● Current MVP
- Organisations, admin and pilot roles
- Manual TXT upload with per-file results
- Duplicate check by SHA-256 within an organisation
- System register and serial-number matching
- Flight track, playback, curves and record table
- Battery profiles and conditional comparison
- CSV export and byte-exact original download
- Local backup with a tested local restore
○ Planned — not yet implemented
- Invitations, password reset, account lockout
- Flymetry Sync for Android — in development
- Offsite backups, monitoring and a production restore drill
- Continuous verification across DJI models and log versions
- Automatic multi-battery identity
- Maintenance history and technical logbooks
- Operational management for flight teams
- International localisation
Does Flymetry support every DJI aircraft?+
No. Flymetry is developed and tested against DJI TXT flight records from a growing set of aircraft, but support is not universal. Available fields vary by aircraft, app version and log format, and encrypted sections can only be read when the required keys are available.
Can it run without contacting DJI?+
By default the server blocks DJI key requests. Encrypted telemetry then stays locked unless the keys are already available locally, and a new encrypted log may need its own key material. This is not full network isolation: optional map tiles (Mapbox) make external requests.
Are battery health scores or replacement decisions included?+
No. Flymetry presents available measurements, BMS reports and calculated observations. It does not certify health, predict remaining life or decide whether a battery is fit to fly. Observed load-step response is not verified internal resistance.
Is there a mobile or controller app?+
Flymetry Sync for Android is in development, intended for supported Android workflows including DJI Enterprise controllers. Compatibility with physical controllers has not been verified. Today, flight records are uploaded manually.
Is Flymetry affiliated with DJI?+
No. Flymetry is independent and is not affiliated with, endorsed by or partnered with DJI.
Is the online product available now?+
The current product is a working MVP. A small private online beta is being prepared; public self-service is not offered. Request early access below and we'll reach out if a place opens.
Running DJI operations with a team? Get in early.
We're preparing a small private pilot for 5–10 people. Leave your details and tell us roughly how many aircraft you operate — we review every request personally.
- 01 Your request is saved in a restricted database — one per email address.
- 02 The on-screen confirmation is your receipt; no confirmation email is sent. We email you if a place opens.
- 03 No newsletter, no resale of your details.