PX4 Generic Quadcopter · 2023-04-11 (0b1a)

Public drone flight log, interactive replay and telemetry analysis.

Type
Quadrotor
Airframe
Generic Quadcopter
Hardware
PX4_FMU_V5
Software
v1.14.0-beta
Log format
px4-ulog
Location
Cottonwood Heights, United States
Flight started
2023-04-11T22:03:16Z
Duration
48s
Home coordinates
40.62034200197022, -111.82853579360247
Onboard video
Not included
Published
2026-07-31T20:41:22Z

Flight telemetry summary

Distance Meters
4.5 m
Maximum Altitude AGL
4.4 m
Maximum Ground Speed
1.07 m/s
Minimum Battery Percent
89.5%
Minimum Battery Voltage
15.47 V
Minimum GPS Satellites
16
Maximum GPS HDOP
1.31
Flight Modes
POSCTL
Maximum Distance From Home Meters
5.2 m
Maximum Distance From Home Time
42s
Average Ground Speed
1.04 m/s
Maximum Climb Rate MPS
1.54 m/s
Maximum Descent Rate MPS
-0.75 m/s
Battery Consumed MAH
59.5 mAh
Battery Consumed Wh
0.96 Wh
Voltage Sag
0.53 V
Flight Mode Seconds
POSCTL: 48s
Maximum GForce
1.53 g
EKF Healthy
Yes

Weather at the flight

Source
open-meteo-archive
Sampled At Utc
2023-04-11T22:00Z
Latitude
40.62
Longitude
-111.83
Temperature C
21.7 °C
Wind Speed MPS
6.84 m/s
Wind Direction Degrees
153
Wind Direction Cardinal
SSE
Weather Code
0
Weather Description
Clear

AI flight report

This was a very short and minor flight — 48 seconds total, with the drone staying within about 4-5 meters of home the whole time. It took off at 0:15, climbed to its maximum altitude of 4 m above home by 0:25, and touched back down by the end, disarming at 0:47. Ground speed stayed low throughout, peaking at just 1.1 m/s at 0:34, and average moving speed was 1.0 m/s. This has the look of a brief hover/test hop rather than a real cross-country flight. Conditions were breezy for such a small flight — 6.84 m/s wind from the SSE and 21.7°C, clear skies — though given the drone barely left the ground, wind doesn't appear to have caused any control problems.

The one real anomaly in this log is a large and sustained disagreement between the barometric and GPS-fused altitude estimates, flagged as a warning at 0:00 and peaking at 1404.6 m at 0:30. That's a huge gap for a flight that only ever climbed 4 m — one of the two altitude sources was clearly reporting badly wrong data, likely a barometer fault (e.g., a bad baro calibration, blocked sensor, or pressure reference issue) rather than a GPS problem, since GPS satellite count stayed healthy at 16-17 sats with HDOP around 1.1 the whole flight. The peak acceleration of 1.41 G at 0:03, right before takeoff, is unremarkable and likely just reflects motor spool-up.

Battery and GPS were both fine — battery only dropped from 98% to 90% (voltage sag of 0.53 V) and satellite count/HDOP stayed stable and good throughout, so neither explains the altitude discrepancy.

Given the size of that barometric-vs-fused gap, the main actionable item here is to check the barometer before trusting this vehicle's altitude readings on a longer flight: recalibrate or inspect the baro sensor (housing, static port, foam cover) and confirm on the next flight that barometric and fused altitude track closely from 0:00 rather than diverging again. Everything else about this flight — speed, battery, GPS lock — was well within normal margins and doesn't point to any other concern.

Detected flight events

  1. 0s — Barometric and fused altitude disagree by 1404 m

    Barometric and fused altitude disagree by 1404 m

  2. 15s — Takeoff (altitude threshold)

    Liftoff at 2 m. The aircraft leaves the ground and starts its climb.

  3. 25s — Maximum altitude: 4 m above home

    Maximum altitude: 4 m above home — the highest point of this flight.

  4. 34s — Maximum ground speed: 1.1 m/s

    Maximum ground speed: 1.1 m/s — the fastest the aircraft moved over the ground.

  5. 47s — Vehicle disarmed

    Motors disarmed — the flight is complete.

Open the interactive 3D flight replay