Skip to content

TAKEOFF

nflyernz edited this page Oct 19, 2026 · 2 revisions

TAKEOFF

Purpose: Review ArduPlane TAKEOFF-mode launch evidence and measured aircraft response from one DataFlash BIN. The report associates firmware launch states with logged airspeed, attitude, altitude, throttle-command and optional rangefinder evidence without treating commands as proof of physical motion.

← Wiki Home

What you need

  • One ArduPlane DataFlash .bin or .BIN log.
  • A recording that includes a TAKEOFF-mode execution if you want a takeoff report.
  • The APT desktop GUI. See the README installation instructions if needed.

A TAKEOFF-mode execution is an interval owned by ArduPlane Mode 13. Runtime AUTO NAV_TAKEOFF activity is tracked separately and is not presented as a Mode-13 execution.

Run TAKEOFF Analysis

  1. Click Choose BIN… beside Source BIN: at the top of the APT window.
  2. Select the required aircraft BIN.
  3. Open TAKEOFF from Overview or select the TAKEOFF tab.
  4. Click Analyse.
  5. Read the report in the panel below the controls.
  6. Click Docs for the shorter in-app description and glossary.

TAKEOFF execution summary with completed and mode-exit-censored results

The summary keeps triggered, already-airborne and omitted non-trigger executions distinct. Completed and mode-exit-censored takeoffs are not combined.

Read the report

Execution summary

The opening summary distinguishes:

  • TAKEOFF-mode executions detected — all owned Mode-13 intervals.
  • Triggered takeoffs analysed — executions containing the firmware's logged Triggered AUTO launch-acceptance event.
  • Already-airborne TAKEOFF entries reported — explicit firmware evidence that TAKEOFF began while already flying or climbing toward takeoff altitude.
  • Non-trigger executions omitted — ordinary entries without a launch trigger or explicit already-airborne evidence.

If the log contains several triggered takeoffs, a comparison table shows their completion state, timing to configured minimum airspeed, altitude response, peak current, maximum roll and endpoint evidence where available.

Launch trigger and throttle suppression

The firmware launch trigger is the report's time origin (0.000 s). It is a logged firmware decision, not proof of hand release, wheel movement or liftoff.

Throttle suppression is the firmware state that withholds the takeoff throttle command until configured release conditions are met. Throttle unsuppressed means that state changed. Reported throttle percentages and PWM are commanded-output evidence; they do not prove motor rotation, thrust or actuator position.

The timing section can show throttle unsuppression, target/course finalization, TAKEOFF control completion and mode exit relative to the trigger. Missing transitions remain unavailable.

TAKEOFF control stages and completion

Takeoff phase evidence reports the observed or configured acceleration gate, trigger, throttle release and first suitable AIRSPEED_MIN observation. It also reports the TAKEOFF control state.

A TAKEOFF is marked Completed only when APT observes the logged control-stage transition from TAKEOFF to NORMAL. A mode change is not promoted to completion. If the aircraft leaves TAKEOFF mode first, the execution is reported as Mode exit before completion and its observation interval is censored at that boundary.

This distinction lets you compare the evidence recorded before the exit without claiming that the automatic TAKEOFF stage completed.

Performance evidence

Depending on the available messages and configuration, a triggered execution can include:

  • Airspeed source, airspeed, GPS groundspeed, pitch and roll at the trigger.
  • Time from trigger or throttle release to the first owned usable sample meeting AIRSPEED_MIN.
  • Altitude change at AIRSPEED_MIN.
  • Airspeed range, largest pitch-tracking error and maximum absolute roll during the bounded control interval.
  • Minimum and endpoint altitude changes.
  • Throttle command at unsuppression, peak throttle, throttle-ramp timing, throttle at AIRSPEED_MIN and peak battery current.
  • A bounded rangefinder height response for a supported immediate-takeoff-pitch profile.
  • Trigger-time TAKEOFF configuration and the selected pitch-control path.

Detailed TAKEOFF phase and performance evidence for a censored execution

This execution ended by mode exit. APT retains its bounded phase, airspeed, rangefinder, control and commanded-throttle evidence without labelling the TAKEOFF control stage complete.

Firmware evidence versus measured behaviour

APT deliberately keeps different evidence types separate:

  • Firmware messages and stage changes describe what ArduPlane reported or commanded.
  • CTUN, GPS, POS, RFNS and battery samples describe logged estimates or measurements inside bounded intervals.
  • Configuration values describe the parameters applicable to the event where supported.

None of these alone proves physical release, rotation, liftoff, motor response or thrust. Sampling gaps can also place a logged observation after the underlying firmware transition.

Limitations

A missing measurement is shown as unavailable or omitted; it is not inferred. Synthetic airspeed estimates are identified separately from airspeed-sensor evidence. Censored executions support only the evidence observed before mode exit.

TAKEOFF Analysis does not grade launch quality, certify safe configuration or recommend parameter changes. Interpret the report with the aircraft, launch method, sensor quality, event boundaries and flight conditions in mind.

Related information

Clone this wiki locally