Skip to content

Landing

nflyernz edited this page Oct 19, 2026 · 2 revisions

Landing

Purpose: Review landing attempts detected inside the flight windows of one ArduPlane DataFlash BIN. Landing Analysis separates approach, preflare, flare, optional rangefinder evidence, and landing or rollout termination.

← Wiki Home

What you need

  • One ArduPlane DataFlash .bin or .BIN log.
  • Logged flight and landing-controller evidence for the approaches you want to examine.
  • The APT desktop GUI. See the README installation instructions if needed.

The GUI analyses every detected flight in the selected BIN. It does not require a separate file for each landing.

Run Landing Analysis

  1. Click Choose BIN… beside Source BIN:.
  2. Select the aircraft BIN.
  3. Open Landing from Overview or select the Landing tab.
  4. Click Analyse.
  5. Review each flight and landing attempt in the report panel.
  6. Click Docs for the in-app description and glossary.

Read the report

Flights, landing windows and attempts

APT first scopes evidence to detected armed-flight windows. Within each flight it finds bounded landing-controller windows, then extracts individual landing attempts. A flight can contain no landing attempt, one attempt or several attempts.

No landing attempts detected means the log did not contain the required supported evidence inside that flight window. It does not automatically mean that no physical landing occurred or that a landing failed.

Approach

For each attempt, the report identifies its logged time window and duration. The APPROACH section can include approach altitude and calculated glide-slope angle. These values describe samples retained within the detected evidence window. Terrain, wind, sensor quality and configuration affect their interpretation.

Preflare and flare

The PREFLARE section can report the event time, height, airspeed, GPS groundspeed and sink rate associated with the logged preflare transition.

The FLARE section can report the flare-timing event, height, sink rate, airspeed, GPS groundspeed and distance to the landing target. A logged flare transition is controller evidence; it is not proof of physical touchdown.

Optional rangefinder evidence

When supported rangefinder data exists, a separate section reports the first non-zero observation and distance, the first observation inside the configured usable range, and the point from which usable observations became continuous.

The section is omitted when suitable evidence is absent. A missing rangefinder section is not a zero-height measurement.

Landing and rollout completion

The final section identifies how the attempt ended. Current report labels include:

  • GPS stop — the detector observed its low-groundspeed endpoint.
  • Landing aborted — the controller evidence indicates an aborted attempt.
  • Flight ended before landing stop detected — the flight window ended first.

When a GPS stop is available, the report can show flare-to-stop time and distance from the target. GPS stop is rollout evidence based on groundspeed; it is not necessarily the touchdown time and does not prove wheel contact.

Landing attempt with approach, preflare, flare, rangefinder and termination evidence

One detected attempt shows the bounded approach, preflare, flare and rangefinder evidence. Its end reason is Flight ended before landing stop detected, so APT does not invent rollout completion.

Limitations

Landing Analysis reports logged evidence, not a landing-quality score. Missing preflare, flare, rangefinder or stop evidence remains unavailable and is not automatically classified as a failed landing.

The analysis cannot certify touchdown quality, runway suitability, wheel contact or landing safety. Sampling rate, sensor accuracy, wind, terrain, configuration and detector boundaries can all affect the reported values.

Related information

Clone this wiki locally