Aerial robots from aircraft choice to a usable mission result

Separate three parts of the system

PX4 documents distinct flight modes for manually supported control, programmed missions and commands from an external system. Those modes describe how the aircraft is controlled. They do not, by themselves, establish the quality of a camera record or completion of a delivery. [1]

Scroll sideways for all columns.

Use the mission geometry to narrow the choice

For an illustrative inspection that needs repeated stationary observations, examine aircraft and payload configurations that can maintain the required viewpoint. For an area survey, examine the path between image strips, the turns and the landing arrangement. The useful comparison includes the entire route rather than a maximum endurance figure.

PX4's fixed-wing documentation describes a hold mode that circles a position. That is a different behavior from the position-holding behavior documented for a multicopter. A mode name should therefore be read in the context of the airframe. [1] [2]

A hybrid vertical-takeoff aircraft adds its own transition and recovery requirements. It should be evaluated in the exact configuration proposed for the mission, without combining the best figures from unrelated operating modes.

Reserve time for the parts outside data collection

Imagine a hypothetical mission budget of 24 minutes within an already approved operating plan. Four minutes are allocated to transit, three to launch and recovery, and a further five are kept outside the planned acquisition period. That leaves 12 minutes for useful observation.

The arithmetic illustrates how little of a headline duration may remain for the payload task. It does not prescribe a safe reserve or demonstrate that a particular aircraft can fly for 24 minutes. The operator must determine permitted margins from the aircraft, conditions and approved procedures.

Record any repeat captures and aborted segments. A flight log can establish that the route was attempted while the payload record shows that another visit is needed.

Define the delivered result before departure

For mapping, specify the required area, location quality and accepted image or sensor record. For inspection, identify surfaces and the feature to be resolved. For delivery, identify the package, permitted destination and confirmation of handoff.

Retain the configuration, original records and unresolved gaps. These make a result useful to another person after the aircraft has landed. The guides below develop the flight and sensing questions separately instead of treating every aerial task as the same application.