PX4 F450 · 2023-11-14

Flight telemetry summary

Distance Meters

3.9 m

Maximum Altitude AGL

4.5 m

Maximum Ground Speed

0.01 m/s

Minimum Battery Percent

100%

Minimum Battery Voltage

11.43 V

Minimum GPS Satellites

4

Maximum GPS HDOP

4.36

Flight Modes

MANUAL

Maximum Distance From Home Meters

1.9 m

Maximum Distance From Home Time

7s

Average Ground Speed

0 m/s

Maximum Climb Rate MPS

0 m/s

Maximum Descent Rate MPS

0 m/s

Voltage Sag

0.18 V

Flight Mode Seconds

MANUAL: 8s

Maximum GForce

1.01 g

EKF Healthy

Yes

Weather at the flight

Source

open-meteo-archive

Sampled At Utc

1970-01-01T00:00Z

Latitude

17.52

Longitude

78.37

Temperature C

11.8 °C

Wind Speed MPS

1.84 m/s

Wind Direction Degrees

103

Wind Direction Cardinal

ESE

Weather Code

3

Weather Description

Overcast

AI flight report

This was a very brief flight — about 7 seconds total, in MANUAL mode throughout, on a fixed-wing PX4 aircraft (px4-demo-f450). The drone barely moved: track distance was only 4 m, with the farthest point from home just 2 m at 0:07, and recorded max ground speed was 0.0 m/s. Altitude peaked at 4 m above home, flagged by a MAX_ALTITUDE event at 0:03. Weather was mild (11.8°C, overcast, light 1.84 m/s wind from the ESE), so conditions were not a factor here. Given the near-zero speed and distance, this log looks more like a short ground/hover test or a truncated recording than a real cross-country flight.

The most notable anomaly is the altitude disagreement: at 0:01 the barometric and fused (GPS/EKF-blended) altitude estimates diverged by roughly 606-608 m, which triggered an ALTITUDE_DISAGREEMENT warning. That's a huge gap for a flight that only ever climbed 4 m, and it strongly suggests one of the two altitude sources (most likely the baro, possibly due to a bad reference/calibration at power-up) was reporting garbage rather than the aircraft actually changing altitude. This coincided with a genuinely weak GPS picture: only 4 satellites and an HDOP of 4.32-4.36 at 0:00, which triggered both a GPS_DEGRADED and a critical LOW_SATELLITES event. With that few satellites and that poor HDOP, the fused altitude/position estimate itself is on shaky ground, so it's hard to say from this data alone which source (baro or GPS-fused) was at fault — just that they disagreed badly right at the start.

Everything else in the log looks unremarkable: battery stayed at 100% and 11.4-11.8 V, motor output and attitude stayed near neutral (peak lean of only 1° at 0:03), and there's no sign of a control or power problem.

Given the data, the actionable takeaway is about GPS lock quality, not flight technique: don't trust this log's position/altitude data for analysis purposes, and if this was a real flight rather than a bench/ground test, wait for a stronger satellite lock (more than 4 sats, HDOP well under 4) before logging or flying, since the 0:00 GPS_DEGRADED and LOW_SATELLITES events line up exactly with the 606 m baro/fused altitude disagreement. Confirming whether this was an intentional short test or a truncated/aborted log would also settle whether "actionable" advice even applies here.

Detected flight events

1. 0s — GPS quality degraded (HDOP 4.3)

   GPS quality degraded (HDOP 4.3). Position accuracy is temporarily reduced; the flight controller keeps estimating position from other sensors.

2. 0s — Low satellite count (4)

   Low satellite count (4). Position hold may be unreliable until reception recovers.

3. 0s — Barometric and fused altitude disagree by 606 m

   Barometric and fused altitude disagree by 606 m

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

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