PX4 F450 Frame · 2023-11-14
Public drone flight log, interactive replay and telemetry analysis.
- Type
- Quadrotor
- Airframe
- Holybro S500
- Hardware
- PX4_FMU_V3
- Software
- v1.13.3
- Log format
- px4-ulog
- Location
- Serilingampalle mandal, India
- Flight started
- 2023-10-13T09:33:29Z
- Duration
- 24s
- Home coordinates
- 17.51907815196579, 78.36665497430566
- Onboard video
- Not included
- Published
- 2026-07-31T20:34:26Z
Flight telemetry summary
- Distance Meters
- 4.5 m
- Maximum Altitude AGL
- 0 m
- Maximum Ground Speed
- 0.91 m/s
- Minimum Battery Percent
- 81.1%
- Minimum Battery Voltage
- 10.28 V
- Minimum GPS Satellites
- 15
- Maximum GPS HDOP
- 0.74
- Flight Modes
- ALTCTL
- Maximum Distance From Home Meters
- 4.7 m
- Maximum Distance From Home Time
- 17s
- Average Ground Speed
- 0 m/s
- Maximum Climb Rate MPS
- 0.28 m/s
- Maximum Descent Rate MPS
- -0.33 m/s
- Battery Consumed MAH
- 4.7 mAh
- Battery Consumed Wh
- 0.05 Wh
- Voltage Sag
- 0.79 V
- Flight Mode Seconds
- ALTCTL: 24s
- Maximum GForce
- 5.66 g
- EKF Healthy
- Yes
Weather at the flight
- Source
- open-meteo-archive
- Sampled At Utc
- 2023-10-13T10:00Z
- Latitude
- 17.52
- Longitude
- 78.37
- Temperature C
- 31.5 °C
- Wind Speed MPS
- 2.24 m/s
- Wind Direction Degrees
- 80
- Wind Direction Cardinal
- E
- Weather Code
- 0
- Weather Description
- Clear
AI flight report
This was a very short flight — 24 seconds total, entirely in ALTCTL mode — and by the numbers the aircraft barely moved: track distance was only 4 m, farthest point from home was 5 m (reached at 0:17), and max altitude above home was 0 m. Average moving speed was 0.0 m/s with a top speed of 0.9 m/s, so this reads as a hover/ground-level check rather than a travelling flight. Weather was a non-factor: 31.5°C, clear skies, and a light 2.24 m/s breeze from the east. GPS was solid throughout, holding 15 satellites and a HDOP of 0.74.
Two things stand out. At 0:00, the log flagged a 575 m disagreement between the barometric and fused altitude estimates — a large gap given the aircraft never actually left ground level. Since the vehicle's real altitude stayed near 0 m the whole flight, this looks like a barometer glitch or bad calibration at power-up rather than an actual altitude excursion, but it's worth confirming before trusting altitude-hold on a longer flight. Then at 0:04, the log recorded a hard-landing/impact event at 3.6 G, matching the peak acceleration of 3.58 G — this happened just 4 seconds after the altitude warning, suggesting the aircraft bounced or touched down hard very early in this short flight. Later, around 0:12-0:14, the attitude tilted to its steepest point (11°), the motor spread widened to 571 µs (0:13), and motor 2 hit its peak output of 1708 µs (0:14) — a wide, sustained spread like that usually means the mixer is fighting a constant asymmetry (uneven CG, a weak motor, or prop damage) rather than just normal correction.
Battery use was minimal (5 mAh, 0.1 Wh) but percentage dropped from 89.2% to 81.1% with a 0.79 V sag and a low point of 10.28 V at 0:16 — a bigger sag than the tiny energy draw would suggest, worth keeping an eye on if it repe
Detected flight events
- 0s — Barometric and fused altitude disagree by 575 m
Barometric and fused altitude disagree by 575 m
- 4s — Impact or hard landing: 3.6 G
Impact or hard landing: 3.6 G
- 23s — Vehicle disarmed
Motors disarmed — the flight is complete.