Ask which task is autonomous
Calling an aircraft autonomous does not fully describe the relationship between the machine and its operators. Navigation, managing a flight and decisions about the use of force are different functions. A headline that merges them into one label can give a much broader impression than the source supports.
A better article names the function under discussion. If a release reports a flight without continuous manual control, that supports a statement about that flight. It does not automatically establish how every other function works. Readers should not have to infer authority from the absence of a person inside the aircraft.
A concrete example from Ghost Bat
At a September 2025 briefing, Australian officials described an E-7 Wedgetail operator controlling two MQ-28 Ghost Bat aircraft during demonstrations. That is useful evidence of a particular human-machine arrangement in a test. It is more informative than a generic claim that the aircraft can operate on its own.
The appropriate follow-up is about the boundary of the demonstration: which tasks were assigned, what information the operator received, and which responsibilities remained with people. Where those details are not public, we leave them open. We do not generalize a demonstration into a complete description of future employment.
Oversight needs an understandable interface
The US Department of Defense's January 2023 autonomy directive offers one public policy example. It calls for appropriate human judgment over force, realistic testing and interfaces that communicate system status and the division of tasks. It is a US policy document, not a worldwide definition or evidence that a specific Australian aircraft satisfies its requirements.
Our editorial conclusion is that meaningful oversight must be explained in practical terms. Saying a human is involved is a starting point, not a complete account. Can that person understand what the system is doing? What responsibilities have actually been assigned? A useful story makes those questions visible while resisting both extremes: treating all autonomy as unrestricted machine decision-making, or treating an operator's presence as sufficient proof that every risk has been resolved.
A conceptual explainer using a dated Australian demonstration and the 2023 US directive as separate examples. It does not describe secret system functions, assess compliance, or claim that all countries use the same rules.
Read the evidence.
- 01Press Conference, WoomeraAustralian Department of Defence · 5 Sept 2025
- 02DoD Directive 3000.09: Autonomy in Weapon SystemsUS Department of Defense · 25 Jan 2023