Skip to content

Field Test Procedures

nflyernz edited this page Oct 19, 2026 · 1 revision

Field Test Procedures

This page points to the established ArduPlaneTools procedures for collecting deliberate test evidence. Read the complete procedure before testing; the summaries below are navigation aids, not substitutes for flight planning, local operating requirements or pilot judgement.

← Wiki Home

Radio Link failsafe tests

Radio Link uses an aircraft DataFlash BIN as the authoritative record of Plane RC-input failsafe episodes and aircraft response. An EdgeTX CSV is optional supporting transmitter evidence.

Both Radio Link tests require a secured aircraft with the propeller removed, people clear of moving parts, verified logging and normal receiver/transmitter operation. Review the configured short and long failsafe timeouts and actions. Configure the receiver to provide an ArduPilot-recognised RF-loss indication; No Pulses is recommended where supported. Begin fresh aircraft and transmitter sessions for each test.

Transmitter-off/on bench test

This test observes short and long failsafe actions and recovery during complete transmitter shutdown.

  • Establish normal RC control and the intended armed or disarmed state.
  • Switch the transmitter fully off for the required configured timing plus the procedure's safety margin.
  • Switch it back on, confirm RC recovery and check the resulting flight mode.
  • Disarm if required, power down the aircraft and retain that session's BIN.

EdgeTX CSV logging stops when the transmitter is switched off. A recording made after restart is a separate transmitter session and must not be presented as continuous telemetry across the shutdown.

Ground walk to deliberate link loss

This test observes the aircraft's failsafe response as usable RC input is lost and then restored while the transmitter normally remains powered.

  • Keep the propeller-off aircraft stationary and secured on a safe route.
  • Confirm normal control, recording sessions, GPS/date-time where available and relevant RF settings.
  • Walk away until RC control is clearly lost. Remain beyond usable input for the required long-failsafe interval only when safe.
  • Walk back until control returns, then verify control and mode recovery before ending the sessions.

This procedure does not establish physical RF-loss distance unless distance is measured independently. Switching a transmitter off also does not reproduce every possible RF-link failure mode.

Use the Radio Link chapter to analyse the recordings. The complete Radio Link Test Procedure contains the required preparation, timing margin, armed-state qualifications and interpretation limits.

Range-Walk Comparison field procedure

Range-Walk Comparison measures transmitter-side telemetry along a repeatable ground route. It is not a Radio Link failsafe test: it uses five landmark marker holds to compare radio configurations and does not deliberately require an aircraft failsafe.

  • Keep the aircraft stationary and disarmed with the propeller removed.
  • Choose five identifiable physical landmarks; landmark 5 is the safe turnaround.
  • Record Walk 1 using the original radio configuration. Stop at each landmark, hold full elevator-down for approximately three seconds, then return the stick to neutral.
  • Preserve the CSV, landmark names, radio configuration and RF settings. Walk 1 establishes the route and fixed baseline.
  • For each later walk, repeat the same landmarks, outward order, turnaround and settings where practical, and document the radio arrangement that changed.
  • Never manufacture a missing marker or automatically reassign the remaining candidates.

Five landmarks define four outward moving sections. Missing or zero-filled telemetry is unavailable evidence, not a zero RF measurement. The comparison does not declare an antenna winner or establish an exact range limit.

See Range-Walk Comparison for the GUI workflow and the full Range-Walk Comparison Test Procedure before recording a walk.

Stall slow-flight test procedure

The Stall procedure supports deliberate FBWA slow-flight evidence. A probable attitude departure in the resulting report does not by itself prove an aerodynamic stall or establish a universal stall speed.

Before flight:

  • Establish and verify a tested MANUAL switch and a deliberate recovery plan.
  • Choose sufficient starting altitude and a conservative minimum recovery-altitude limit for the aircraft, site, weather and test plan.
  • Stop testing and begin the planned recovery if the aircraft approaches that limit or control becomes uncertain.
  • Do not continue holding nose-up demand into an uncontrolled departure.
  • After an attempted departure, restore stable airspeed and attitude and reassess before any further attempt. A mode switch alone does not prove recovery.

Review the aircraft, controls, centre of gravity, weather, test area, instrumentation and logging before beginning. Retain the corresponding BIN and relevant test notes after the flight.

Read the Stall chapter for report interpretation and the complete Stall / slow-flight test procedure before conducting the test.

Related information

Clone this wiki locally