PX4 S500 Generic · 2023-10-28

Public drone flight log, interactive replay and telemetry analysis.

Type
Quadrotor
Airframe
S500 Generic
Hardware
PX4_FMU_V5
Software
v1.14.0 (a5e429)
Log format
px4-ulog
Location
الجيزة, مصر
Flight started
2023-10-28T16:20:53Z
Duration
54s
Home coordinates
30.0244826710274, 31.211274280773946
Onboard video
Not included
Published
2026-07-31T20:35:27Z

Flight telemetry summary

Distance Meters
0.5 m
Maximum Altitude AGL
0.1 m
Maximum Ground Speed
0.43 m/s
Minimum Battery Percent
0%
Minimum Battery Voltage
-1.1 V
Minimum GPS Satellites
8
Maximum GPS HDOP
1.2
Flight Modes
MANUAL, AUTO_LOITER, MANUAL, AUTO_LOITER, MANUAL
Maximum Distance From Home Meters
0.4 m
Maximum Distance From Home Time
24s
Average Ground Speed
0 m/s
Maximum Climb Rate MPS
0.65 m/s
Maximum Descent Rate MPS
-0.52 m/s
Voltage Sag
0.07 V
Flight Mode Seconds
MANUAL: 9s, AUTO_LOITER: 46s
Maximum GForce
3.57 g
EKF Healthy
Yes

Weather at the flight

Source
open-meteo-archive
Sampled At Utc
2023-10-28T16:00Z
Latitude
30.02
Longitude
31.21
Temperature C
30.3 °C
Wind Speed MPS
2.18 m/s
Wind Direction Degrees
74
Wind Direction Cardinal
ENE
Weather Code
0
Weather Description
Clear

AI flight report

This flight lasted 54 seconds and, according to the logs, never really left the ground: track distance is recorded as 0 m, max altitude 0 m above home, and max ground speed only 0.4 m/s. The telemetry table shows altitude AGL hovering at or just below 0 m throughout (0:00 to 0:45), with battery percentage flat at 0.0% the entire time. Conditions were unremarkable — 30.3°C, light wind at 2.18 m/s from the ENE, clear skies — so weather isn't a factor here. The vehicle cycled through modes several times (MANUAL, AUTO_LOITER, MANUAL, AUTO_LOITER, MANUAL), with mode changes logged at 0:05, 0:11, 0:12, and 0:52, before disarming at 0:53.

The data points strongly to this being a bench test, pre-arm check, or aborted takeoff rather than an actual flight. Several readings are physically implausible for airborne flight: battery voltage is logged as negative (-1.1 V at 0:00, still -0.6 V by 0:45), battery percentage is 0% for the full duration despite a "BATTERY_CRITICAL" event firing at 0:00, and the altitude disagreement event at 0:00 shows a 42 m gap between barometric and fused altitude estimates — all consistent with sensors that hadn't settled or a system not actually flying. A motor imbalance warning also fired at 0:00 (346 µs spread between motor 3 and motor 1), and the derived diagnostics note a widest spread of 688 µs at 0:04 and a peak acceleration of 2.71 G at 0:05 — a spike that would be notable in real flight but here more likely reflects handling, a prop strike, or vibration on the ground rather than an aerodynamic event, given the vehicle never gained altitude or speed.

Given all this, I'd treat any "flight performance" figures from this log (climb rate, descent rate, farthest point) as artifacts of ground testing rather than real airmanship data — they shouldn't be used to judge pilot technique. The two things actually worth checking before the next flight: the battery reporting chain, since -1.1 V and a simultaneous 0% charge reading alongside a critical-battery alert suggests either a disconnected/misconfigured voltage sensor or a genuinely dead pack that shouldn't have been used to attempt arming; and the altitude estimator disagreement at 0:00 (42 m baro-vs-fused gap), which should be resolved before trusting this vehicle's altitude hold in the air. I don't have data here that explains why the vehicle stayed grounded or what triggered the mode-cycling — that would need the raw pilot input log or a maintenance note from this session.

Detected flight events

  1. 0s — Battery below 15%

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

  2. 0s — Sustained motor asymmetry: motor 3 1346 µs vs motor 1 1000 µs (346 µs spread)

    Sustained motor asymmetry: motor 3 1346 µs vs motor 1 1000 µs (346 µs spread)

  3. 0s — Barometric and fused altitude disagree by 42 m

    Barometric and fused altitude disagree by 42 m

  4. 5s — Flight mode changed to AUTO_LOITER

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

  5. 11s — Flight mode changed to MANUAL

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

  6. 12s — Flight mode changed to AUTO_LOITER

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

  7. 52s — Flight mode changed to MANUAL

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

  8. 53s — Vehicle disarmed

    Motors disarmed — the flight is complete.

Open the interactive 3D flight replay