PX4 Generic Quadcopter · 2023-04-04
Public drone flight log, interactive replay and telemetry analysis.
- Type
- Quadrotor
- Airframe
- Generic Quadcopter
- Hardware
- PX4_FMU_V6C
- Software
- v1.14.0 (58000f)
- Log format
- px4-ulog
- Flight started
- 2023-04-04T08:14:32Z
- Duration
- 4m 32s
- Home coordinates
- 0.000006018555431808181, -0.0000012800464546103285
- Onboard video
- Not included
- Published
- 2026-07-31T20:42:50Z
Flight telemetry summary
- Distance Meters
- 450.4 m
- Maximum Altitude AGL
- 12.3 m
- Maximum Ground Speed
- 11.16 m/s
- Minimum Battery Percent
- 35.9%
- Minimum Battery Voltage
- 13.65 V
- Minimum GPS Satellites
- 23
- Maximum GPS HDOP
- 0.62
- Flight Modes
- POSCTL, MODE_19, AUTO_LAND
- Maximum Distance From Home Meters
- 96.7 m
- Maximum Distance From Home Time
- 2m 34s
- Average Ground Speed
- 2.18 m/s
- Maximum Climb Rate MPS
- 2.36 m/s
- Maximum Descent Rate MPS
- -2.65 m/s
- Battery Consumed MAH
- 827.1 mAh
- Battery Consumed Wh
- 12.75 Wh
- Voltage Sag
- 2.32 V
- Flight Mode Seconds
- POSCTL: 1m 12s, MODE_19: 2m 58s, AUTO_LAND: 22s
- Maximum GForce
- 4.12 g
- EKF Healthy
- Yes
Weather at the flight
- Source
- open-meteo-archive
- Sampled At Utc
- 2023-04-04T08:00Z
- Latitude
- 0
- Longitude
- -0
- Temperature C
- 25.9 °C
- Wind Speed MPS
- 4.14 m/s
- Wind Direction Degrees
- 82
- Wind Direction Cardinal
- E
- Weather Code
- 51
- Weather Description
- Drizzle light
AI flight report
The flight lasted 4:32 and covered 450 m of track, staying close to home the whole time — the farthest point reached was just 97 m out, at 2:34. Altitude topped out at 12 m above home, logged at 4:12, and the vehicle spent most of its climb time cruising around 8 m AGL rather than gaining height quickly. Conditions were mild but damp: 25.9°C with a light easterly breeze (4.14 m/s) and light drizzle, which is worth keeping in mind given the altitude and battery behavior described below. The flight moved through POSCTL, then MODE_19 (the bulk of the flight, 2:58), and finished with a 22-second AUTO_LAND.
The most active period of the flight is clustered right around 1:13–1:19, just after the switch into MODE_19 at 1:12. In that short window the log shows the widest motor spread of the flight (479 µs at 1:13), the top ground speed (11.2 m/s at 1:18), the highest G-load (2.17 G, also 1:18), and the steepest attitude (28° from level, 1:19). Taken together this looks like one aggressive maneuver or transition rather than a sustained problem — the spread and G-load don't stay elevated in the surrounding 15-second samples, which show speed dropping back to under 1 m/s by 1:30. There were also two altitude-disagreement warnings, one at the very start (12 m gap) and one at 3:19 (8 m), and the single largest baro-vs-fused gap of the flight (14.9 m) landed at 1:17, right inside that same busy window. Since barometer and fused-position estimates are independent, a gap that large is worth flagging even though it didn't appear to affect the flight path.
The other point of interest is landing. Battery percentage had already fallen to 38% by 4:00, and at 4:10 — the same moment battery voltage hit its flight-low of 13.65 V — motor 3 hit its peak output for the flight, 1883 µs, close enough to the 2000 µs ceiling that little control authority would have been left if more thrust were needed. This coincides with the mode changes to ALTCTL and then AUTO_LAND, both logged at 4:10, and a fast descent shortly after (2.7 m/s at 4:14, altitude dropping from 8.2 m at 4:15 to 0.8 m by 4:30). Nothing in the data shows a loss of control, but the timing of low voltage, high motor demand, and the descent all landing in the same 10-second stretch is a pattern worth a closer look.
Two things this flight's data actually supports checking: first, the battery margin at landing — voltage sag of 2.32 V combined with a near-ceiling motor command at 4:10 suggests the pack was working hard right when AUTO_LAND needed authority, so confirming remaining capacity before triggering landing on future flights would add margin. Second, the barometer/fused-altitude disagreement (up to 14.9 m at 1:17, plus the two logged warnings) is large enough that it's worth checking baro calibration or looking for vibration/prop-wash effects around that maneuver window, since AUTO_LAND tim
Detected flight events
- 0s — Barometric and fused altitude disagree by 12 m
Barometric and fused altitude disagree by 12 m
- 5s — Takeoff (altitude threshold)
Liftoff at 2 m. The aircraft leaves the ground and starts its climb.
- 1m 12s — Flight mode changed to MODE_19
Flight mode changed to MODE_19. The pilot or autopilot switched control behavior here.
- 1m 18s — Maximum ground speed: 11.2 m/s
Maximum ground speed: 11.2 m/s — the fastest the aircraft moved over the ground.
- 3m 19s — Barometric and fused altitude disagree by 8 m
Barometric and fused altitude disagree by 8 m
- 4m 10s — Flight mode changed to ALTCTL
Flight mode changed to ALTCTL. The pilot or autopilot switched control behavior here.
- 4m 10s — Flight mode changed to AUTO_LAND
Flight mode changed to AUTO_LAND. The pilot or autopilot switched control behavior here.
- 4m 12s — Maximum altitude: 12 m above home
Maximum altitude: 12 m above home — the highest point of this flight.
- 4m 31s — Vehicle disarmed
Motors disarmed — the flight is complete.