PX4 Generic Quadcopter · 2023-04-11 (2087)

Flight telemetry summary

Distance Meters

33.7 m

Maximum Altitude AGL

7.4 m

Maximum Ground Speed

2.75 m/s

Minimum Battery Percent

48%

Minimum Battery Voltage

21.52 V

Minimum GPS Satellites

29

Maximum GPS HDOP

0.77

Flight Modes

POSCTL

Maximum Distance From Home Meters

4.6 m

Maximum Distance From Home Time

2m 43s

Average Ground Speed

1.43 m/s

Maximum Climb Rate MPS

0.65 m/s

Maximum Descent Rate MPS

-1.14 m/s

Battery Consumed MAH

607.7 mAh

Battery Consumed Wh

13.63 Wh

Voltage Sag

1.59 V

Flight Mode Seconds

POSCTL: 3m 21s

Maximum GForce

1.89 g

EKF Healthy

Yes

Weather at the flight

Source

open-meteo-archive

Sampled At Utc

2023-04-11T21:00Z

Latitude

40.62

Longitude

-111.83

Temperature C

21.3 °C

Wind Speed MPS

7.2 m/s

Wind Direction Degrees

155

Wind Direction Cardinal

SSE

Weather Code

0

Weather Description

Clear

AI flight report

This was a very short, tight flight: 3:21 total, covering just 34 m of ground track and staying within 5 m of home (farthest point at 2:43), flown entirely in POSCTL. Despite being logged as a fixed-wing aircraft, the profile looks like a hover/hop test — it climbed to a peak of 7 m above home by 1:17, then came back down near ground level (0.5-0.9 m) for the remainder of the flight, pottering around at low speed (mostly under 1.7 m/s) until disarming at 3:20. Winds at the time were a brisk 7.2 m/s from the SSE, which is worth noting given how little ground the aircraft actually covered.

The most notable anomaly is the altitude disagreement flagged at 0:00: barometric and fused altitude estimates disagreed by 1395 m, and the derived diagnostics show this gap actually grew slightly to 1398.3 m at 3:09. That's a sustained, not momentary, disagreement between two independent altitude sources, and it persisted for essentially the whole flight. This kind of gap generally points to a baro or GPS-altitude reference/calibration issue rather than a one-off glitch, though the log alone doesn't tell us which sensor is at fault. Aside from that, the flight was mechanically unremarkable — motor 3 peaked at 1737 µs (1:02), well short of saturation, and the widest motor spread (284 µs at 2:57) coincided with the point of lowest satellite count (29) and highest HDOP (0.77), suggesting the mixer was working slightly harder to hold position as GPS quality dipped, not a sign of a damaged prop or CG problem.

Battery-wise, the aircraft used 608 mAh over the flight and sagged from 23.1 V down to 21.5 V (0.26 V/cell), ending at 49.3% with voltage still a reasonable 21.6 V — nothing concerning there for a flight this short.

Given the size of the persistent altitude gap, I'd recommend checking the barometer/GPS-altitude calibration before trusting altitude-hold behavior on this airframe for a real flight — a 1395+ m disagreement sitting quietly in the background from the very first sample is the kind of thing that could bite during a longer or higher flight even though it caused no visible problem here. I'd also suggest re-running this test with less wind or in a more sheltered spot: 7.2 m/s of wind against a vehicle that only ever moved a few meters and topped out at 2.8 m/s ground speed leaves very little margin, and the small increase in motor spread as GPS satellites dropped to 29 at 2:57 hints the controller was already starting to work for its position hold.

Detected flight events

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

   Barometric and fused altitude disagree by 1395 m

2. 45s — Takeoff (altitude threshold)

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

3. 1m 17s — Maximum altitude: 7 m above home

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

4. 2m 42s — Maximum ground speed: 2.7 m/s

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

5. 3m 20s — Vehicle disarmed

   Motors disarmed — the flight is complete.