Repository navigation
Stall
Purpose: Review deliberate FBWA slow-flight attempts and evidence of probable demand-opposed attitude departures in one ArduPlane DataFlash BIN. The analysis characterises logged behaviour; it does not declare a certified stall speed or prove an aerodynamic stall.
- One ArduPlane DataFlash
.binor.BINlog from deliberate FBWA slow-flight testing. - Suitable logged pilot-input, attitude, controller and flight evidence; airspeed evidence is included only when supported.
- A safely planned and conducted test. Read the Stall / slow-flight test procedure before collecting evidence.
- The APT desktop GUI. See the README installation instructions if needed.
The in-app Test Procedure includes the required preparation and recovery guidance. Testing is intended for FBWA, with a tested MANUAL switch, a deliberate recovery plan, sufficient starting altitude and a conservative minimum recovery-altitude limit chosen for the aircraft and conditions.
Stop the test and initiate the planned recovery if control becomes uncertain or the aircraft approaches that limit. Do not continue holding nose-up demand into an uncontrolled departure. Switching modes alone does not prove recovery; stable controlled flight must be confirmed.
- Click Choose BIN… beside Source BIN:.
- Select the relevant aircraft BIN.
- Open Stall from Overview or select the Stall tab.
- Click Test Procedure when you need the safety and flight-test guidance.
- Click Analyse.
- Review each detected flight independently in the report panel.
- Click Docs for the shorter description and glossary.
The flight summaries count no-demonstrated-departure, ambiguous and rejected outcomes independently. These flights contain no probable departure and therefore no comparable probable-departure cohort.
APT retains four outcomes:
- Probable demand-opposed attitude departure — logged pitch stopped following continuing nose-up FBWA demand in the required evidence sequence.
- No demonstrated departure — a usable attempt did not show that signature. This does not establish a safe airspeed.
- Ambiguous — a real manoeuvre lacked complete or consistent decisive evidence.
- Rejected candidate — the movement did not contain enough support to be treated as an analysable attempt.
Counts are reported for each detected flight. Flights are never pooled into one cohort.
For a supported attempt, the report can relate:
- Flight mode, commanded throttle class, bank context and flap command.
- Pilot nose-up input, FBWA target pitch and measured pitch response.
- Pitch peak, first opposed fall, fall magnitude and growth in target-versus-actual error.
- Logged elevator command and PWM output endpoint.
- BARO altitude at the departure reference where available.
Commanded elevator and PWM are controller/output evidence, not physical control-surface feedback.
Airspeed observations are identified as raw ARSP samples and can include pre-fall pitch-peak airspeed, first opposed-fall airspeed, minimum usable airspeed, recovery-control-start airspeed and a later recovery milestone.
The report includes saved and effective airspeed-ratio provenance where supported and warns when the evidence is unusable or incompatible. The lowest value can occur in another phase and must not automatically be called the stall speed.
When at least two same-flight probable departures have compatible calibration and clean, idle-commanded, approximately level context, APT can show a descriptive cohort mean, median and range. Incompatible or insufficient evidence produces no mean.
For probable departures, the report can identify observed pilot-demand reduction, target reduction or commanded-power increase, followed by supported pitch, airspeed, altitude and sink-arrest observations.
These are recovery-control milestones. They do not assert that recovery was complete, that the aircraft was safe to continue testing, or that a mode switch guaranteed recovery.
The probable departure retains pilot demand, FBWA target, measured pitch, raw-airspeed provenance and bounded recovery observations. Nearby no-demonstrated-departure attempts remain separately classified.
A Probable demand-opposed attitude departure is an evidence classification. It does not by itself prove aerodynamic stall, flow separation, angle-of-attack stall, exact stall onset or spin entry.
APT does not select or recommend AIRSPEED_STALL, AIRSPEED_MIN, approach speed or landing speed. No-demonstrated-departure attempts do not establish that an airspeed is safe.
The result depends on the logged FBWA demand, controller output, attitude response, sensor quality, calibration provenance and detector sequence. Missing or inconsistent evidence remains unavailable or ambiguous rather than being inferred.
Use the report to review recorded behaviour alongside the flight-test plan and pilot observations. It does not replace safe flight-test practice, physical inspection or operational judgement.
- Back to the Wiki Home
- TAKEOFF — compare how APT separates firmware commands from measured response in another flight phase.
- Events — inspect chronological mode changes and firmware messages.
- APT project README
- Stall in-app Help source
- Stall glossary
- Stall / slow-flight test procedure
Getting started
Battery & packs
Flight analysis
Radio & diagnostics
Reference

