Every eVTOL startup I talk to has the same problem: flight test data scattered across spreadsheets, CSVs, and custom scripts that break every other week. No standard format. No validation. No easy way to query what happened during Test 47.
I hit this wall myself. So I built aero-telemetry, a lightweight, open-source telemetry ingestion API for aerospace prototyping.
What It Does
Ingest sensor data via HTTP: battery state, GPS, IMU, motor RPM
Validate everything: voltage ranges, motor counts, coordinate bounds
