PX4 Holybro S500 · 2023-06-17

Flight telemetry summary

Distance Meters

0 m

Maximum Altitude AGL

0.8 m

Maximum Ground Speed

0.03 m/s

Minimum Battery Percent

0%

Minimum Battery Voltage

0 V

Minimum GPS Satellites

17

Maximum GPS HDOP

0.66

Flight Modes

AUTO_LAND

Maximum Distance From Home Meters

0.4 m

Maximum Distance From Home Time

19s

Average Ground Speed

0 m/s

Maximum Climb Rate MPS

0.05 m/s

Maximum Descent Rate MPS

-0.01 m/s

Voltage Sag

0.06 V

Flight Mode Seconds

AUTO_LAND: 21s

Maximum GForce

1.02 g

EKF Healthy

Yes

Weather at the flight

Source

open-meteo-archive

Sampled At Utc

2023-05-02T16:00Z

Latitude

54.71

Longitude

37.53

Temperature C

11.3 °C

Wind Speed MPS

3.14 m/s

Wind Direction Degrees

233

Wind Direction Cardinal

SW

Weather Code

1

Weather Description

Mainly clear

AI flight report

This was an extremely short flight — 21 seconds total, from arming to disarm, and the vehicle barely left the ground. Track distance was 0 m, max altitude reached just 1 m above home, and max ground speed was 0.0 m/s throughout. The two telemetry samples available (0:00 and 0:15) confirm this: altitude went from 0.0 m to 0.7 m AGL with vertical speed near zero, and the log shows the aircraft was already in AUTO_LAND mode at arming, staying there for the entire 21-second duration. Weather was mild (11.3°C, light 3.14 m/s wind from the southwest, mostly clear skies), so conditions were not a factor here.

The data points to a problem on the ground or at the very start of the flight rather than anything that happened in the air. At 0:00, the battery was already flagged critical (below 15%), with a logged voltage of 0.00 V — this is likely a sensor/telemetry dropout rather than a literal zero-volt battery, since the aircraft still armed and briefly lifted off, but it's worth checking your logs directly since the report can't distinguish "battery genuinely dead" from "voltage sensor not reporting" from this summary alone. At the same instant (0:00), there's a 91 m disagreement between the barometric and fused altitude estimates — a large enough gap that one of those two sources was clearly wrong, and this is flagged as the single biggest anomaly in the flight. Given that the vehicle went straight into AUTO_LAND at the very start, it's plausible (though not certain from this data) that the critical battery reading and/or the altitude disagreement triggered an automatic land response before any real flight could begin.

For next steps, I'd recommend checking the raw battery voltage log around 0:00 to confirm whether the 0.00 V reading is a genuine power issue or a sensor fault — if it's real, this aircraft should not have been armed in the first place. I'd also recommend reviewing the barometer and GPS/fused altitude sources independently around 0:00, since a 91 m disagreement is large enough to cause bad automatic decisions (like the immediate AUTO_LAND) if it's not resolved before flight. Given how little useful flight data exists here, the more useful diagnostic step is probably pulling the raw (non-downsampled) log for the first few seconds rather than drawing conclusions from this summary alone.

Detected flight events

1. 0s — Battery below 15%

   Battery below 15%. Battery at 0%. The aircraft should land as soon as possible.

2. 0s — Barometric and fused altitude disagree by 91 m

   Barometric and fused altitude disagree by 91 m

3. 0s — Vehicle armed

   Motors armed — the flight controller accepted the arming request and the flight officially begins here.

4. 0s — Flight mode changed to AUTO_LAND

   Flight mode changed to AUTO_LAND. The pilot or autopilot switched control behavior here.

5. 20s — Vehicle disarmed

   Motors disarmed — the flight is complete.