Which factor makes automation complacency a specific hazard for remote pilots?

Automation complacency is the erosion of active monitoring that follows from a system working reliably. Return-to-home is the clearest case for a remote pilot: it works nearly every time, so the pilot comes to treat it as a guaranteed recovery rather than as an automated routine with preconditions. Those preconditions matter. Return-to-home depends on a valid satellite position and a correctly recorded home point, and it flies a programmed path — usually a climb to a set altitude and a direct track home — that knows nothing about the tree, the crane or the building that has appeared along the way. When it engages in a situation it was not designed for, the pilot who has stopped monitoring loses seconds recognising that the automation is not going to fix this, and those seconds are often the entire margin. The countermeasure is to keep hands on the controls, know how to override instantly, and treat every automated recovery as something to supervise rather than to trust.

Reliable automation erodes active monitoring, so a pilot who trusts return-to-home is slow to recognise when it is behaving wrongly and delays taking manual control.

Automation complacency describes reduced monitoring arising from reliable automated systems. Return-to-home depends on valid satellite position and a correct home point, and flies a programmed path without obstacle awareness.

It Works Until It Does Not. The seconds spent realising that are the margin you were counting on.

Return-to-home has no obstacle awareness along its programmed path. Verify the home point and the return altitude before every flight.

• •Treating return-to-home as a guaranteed recovery
• •Not verifying the home point and return altitude before flight
• •Watching the automation rather than being ready to override it