PX4 Generic Quadcopter · 2025-12-19

Flight telemetry summary

Distance Meters

0 m

Maximum Altitude AGL

0 m

Maximum Ground Speed

0.16 m/s

Minimum Battery Percent

93.4%

Minimum Battery Voltage

24.76 V

Minimum GPS Satellites

14

Maximum GPS HDOP

1.01

Flight Modes

ALTCTL

Maximum Distance From Home Meters

1.3 m

Maximum Distance From Home Time

22s

Average Ground Speed

0 m/s

Maximum Climb Rate MPS

-0.02 m/s

Maximum Descent Rate MPS

-0.1 m/s

Battery Consumed MAH

3.9 mAh

Battery Consumed Wh

0.1 Wh

Voltage Sag

0.18 V

Flight Mode Seconds

ALTCTL: 21s

Maximum GForce

1.28 g

EKF Healthy

Yes

Weather at the flight

Source

open-meteo-archive

Sampled At Utc

2025-12-19T23:00Z

Latitude

32.49

Longitude

-84.98

Temperature C

10.2 °C

Wind Speed MPS

2.59 m/s

Wind Direction Degrees

310

Wind Direction Cardinal

NW

Weather Code

0

Weather Description

Clear

AI flight report

This was a very brief flight — 22 seconds total, and the vehicle never really went anywhere. Track distance was 0 m, top ground speed was just 0.2 m/s, and the farthest it got from home was 1 m at 0:22. Altitude stayed at 0 m above home for the whole log, with the two samples showing a slight dip to -1.9 m AGL by 0:15 and a max descent rate of -0.1 m/s. In short, this looks like a ground test or an arm-and-disarm check rather than an actual flight — the aircraft was armed at 0:00, spent its 21 seconds in ALTCTL mode, and disarmed at 0:21. Conditions were cold and calm-ish (10.2°C, wind 2.59 m/s from the NW), which wouldn't have been a factor at this scale.

Despite the lack of movement, the telemetry flagged some real concerns right at 0:00. Motor 2 was commanded to 1984-2000 µs — essentially pinned at maximum output — while motor 1 sat around 1161 µs, a 729-1000 µs spread depending on the exact sample. That's a large, sustained asymmetry, not a brief correction, and it's the kind of pattern you'd expect from a weak motor, a damaged prop, or a CG problem the mixer is fighting to compensate for. At the same time, barometric and fused altitude disagreed by 36-39 m, which is a big enough gap that one of the two altitude sources was clearly wrong at that moment — worth checking before trusting altitude data from this log. GPS was fine throughout (14-15 satellites, HDOP 0.90-1.01), so the disagreement isn't a satellite issue.

Battery draw was negligible (4 mAh, 0.1 Wh) with only 0.18 V of sag, consistent with a flight this short — nothing notable there.

Given the motor imbalance and saturation both showed up in the very first second, the actionable step is to check motor 2 and its prop on the ground before the next flight — if it's already near max output while stationary, there's little margin left once real maneuvering starts. It's also worth confirming why barometric and fused altitude diverged by over 36 m during a flight where the vehicle never left the ground — that's either a baro calibration issue or an EKF fusion glitch, and either one should be resolved before relying on altitude data from a longer flight.

Detected flight events

1. 0s — Sustained motor asymmetry: motor 2 1890 µs vs motor 1 1161 µs (729 µs spread)

   Sustained motor asymmetry: motor 2 1890 µs vs motor 1 1161 µs (729 µs spread)

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

   Barometric and fused altitude disagree by 36 m

3. 0s — Motor 2 at 1984 µs — near maximum output, little authority left

   Motor 2 at 1984 µs — near maximum output, little authority left

4. 0s — Vehicle armed

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

5. 0s — Flight mode changed to ALTCTL

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

6. 21s — Vehicle disarmed

   Motors disarmed — the flight is complete.