Reports have surfaced that a military aircraft used in the highly controversial Sept. 2, 2025, strike on an alleged drug boat, as well as a follow-on strike as two survivors were clinging to its wreckage, was imitating a civilian aircraft (see here and here). Reportedly, the aircraft had no military markings and carried weapons internally, but its transponder was “squawking” its military status. The aircraft apparently swooped in low over the boat, which turned back toward Venezuela, before attacking it and killing nine on board. Two shipwrecked crewmembers and the remains of the boat were then destroyed in a second strike (see analysis of the attacks here and here).
Most discussion of disguising the aircraft’s military character has focused on whether doing so violates the law of armed conflict (LOAC) prohibition on perfidious attack, which involves feigning protected status under LOAC to kill the enemy. This article explains that using an aircraft not marked as military in character is lawful during peacetime and that, had there been an ongoing armed conflict (there was not), the attack would not have been perfidious under LOAC. However, if conducted as reported and if an armed conflict had been underway, the operation might have violated a separate LOAC obligation requiring that only military aircraft exercise belligerent rights, such as conducting attacks.
It is important to clarify at the outset that both the first and second strikes on the boat were clearly unlawful on other grounds (see here, here, and here). Moreover, it is difficult to see any operational merit in using an aircraft that appeared to be civilian to conduct the attack, although in the face of the administration’s lack of transparency, the wisdom of doing so is difficult to assess. That said, it is telling that subsequent attacks, which were likewise unlawful, appear to have been carried out by appropriately marked military platforms.
Which Body of Law Governs?
The administration claims that the drug boat strikes took place in the context of a non-international armed conflict to which LOAC rules apply. That claim is simply wrong (see the Just Security collection of articles on the attacks). The U.S. sinkings of alleged drug boats, at least until the U.S. attack on Venezuela (and still in cases lacking a sufficient nexus to that conflict), were governed instead by international law rules applicable in peacetime. This is because neither of the two requirements for the existence of a non-international armed conflict, an armed conflict between a State and an “organized armed group,” was satisfied at the time of the attack (or any time since). As explained previously in greater depth, 1) the drug cartels and gangs concerned do not qualify as “organized armed groups under LOAC, and 2) the violence between the United States and the drug cartels and gangs had not reached the requisite degree of intensity on Sept. 2 (DoD Law of War Manual, § 17.1.1; Tadić, para. 70).
As a consequence, LOAC rules such as the prohibitions on attacking civilians and civilian objects, the qualification of shipwrecked individuals as protected persons who are hors de combat, and the prohibition on perfidy do not apply. Instead, the strike was an “internationally wrongful act” by the United States in violation of the right to life of those aboard the boat and an act of murder by some of those involved under the domestic criminal law of States that enjoy prescriptive (lawmaking) jurisdiction over the incident, such as the State of nationality of the participants in the strike and of those who were killed (see our discussion here).
As to the aircraft that conducted the Sept. 2 strike appearing to be of civilian character, the Chicago Convention on International Civil Aviation provides that “Every aircraft engaged in international air navigation shall bear its appropriate nationality and registration marks” (art. 20). However, the Convention explicitly excludes “State aircraft,” a category that includes “[a]ircraft used in military… services” from its reach (art. 3; with limited exceptions that are not relevant here). While there is a strong peacetime practice among States of identifying military aircraft using national rondels or insignia, tail markings, serial numbers, and unit or service identifiers, there is no international law obligation dictating how State aircraft must be marked. The use of an aircraft that appeared to have civilian (civil) status to mount the attack made it no more unlawful than it already was.
Did the Attack Violate the Perfidious Attack Rule? (had there been an armed conflict)
As noted, there was no armed conflict, and therefore, no violation of the prohibition on perfidious attack. However, even if an armed conflict had been underway, the use of an aircraft that appeared to be civilian would not, in the attendant circumstances, have qualified as a perfidious attack.
There is universal agreement that under customary law, it is prohibited to kill or wound the enemy by resorting to perfidy (§ 5.22.2; see also ICRC Customary IHL study, rule 65). The DoD Law of War Manual defines perfidy as “acts that invite the confidence of enemy persons to lead them to believe that they are entitled to, or are obliged to accord, protection under the law of war, with intent to betray that confidence” (§ 5.22.1). A long-standing prohibition (see, e.g., 1863 Lieber Code, art. 16; 1899 Hague II and 1907 Hague IV Regulations, art. 23(b)), in treaty law, it is found in Article 37(1) of the 1977 Additional Protocol I for Parties to the instrument (the United States is not a Party). That provision extends the prohibition to perfidious capture.
The applicability of the rule in non-international armed conflict is not entirely settled, an important point in light of the (flawed) U.S. claim that the attack occurred in that context. The DoD Law of War Manual discusses perfidious attack only in the context of an international armed conflict (conflict between States), although it does not expressly exclude application in a non-international armed conflict. However, the prevailing, and better, view is that it is likewise barred in such conflicts, with the ICRC setting out strong support for that position in its Customary International Humanitarian Law study’s catalogue of practice. This is also the conclusion of a study by the International Institute of Humanitarian Law (NIAC Manual, § 2.3.6). And the Rome Statute of the International Criminal Court includes perfidy as a war crime in both international and non-international armed conflict (arts. 8(2)(b)(xi) and 8(2)(e)(ix), respectively).
There is no question that civilian status is among the protected statuses that may not be feigned to attack the enemy. Indeed, “feigning civilian status and then attacking” is one of the five examples of perfidious attack in the DoD Law of War Manual (§ 5.22.3). And there is equally no question that the rule extends to aircraft. The international group of experts who prepared the HPCR Manual on the International Law Applicable to Air and Missile Warfare (Harvard AMW Manual) concluded that “[i]t is perfidious for a military aircraft to feign the status of a civilian aircraft,” giving as examples “painting civilian markings on a military aircraft” (commentary to rule 114(b); The Harvard AMW Manual confirmed that leveraging perfidy to “kill or injure an adversary” is unlawful in the aerial environment (rule 111). The Canadian Law of Armed Conflict at the Operational and Tactical Levels manual likewise provides that “using false markings on military aircraft such as the markings of civil aircraft” is among the “examples of perfidy in air warfare if a hostile act is committed” (§ 706(3)(a)).
The aircraft at issue in the Sept. 2 U.S. strike did appear to be a civilian aircraft. And, while it was apparently squawking its military status, those aboard the boat that it was engaging would have been unable to acquire that signal. However, that does not end the analysis. There are two reasons the Sept. 2 attack would not constitute perfidy had it occurred during an armed conflict (as a reminder, it did not).
First, a perfidious attack requires a specific intent. As noted in the DoD Law of War Manual, “The key element in perfidy is the false claim to protections under the law of war in order to secure a military advantage over the opponent” (§ 5.22.1, emphasis added). That military advantage can, for instance, be catching the enemy unaware or preventing the enemy from realizing the need to flee.
Operationally, it is difficult to imagine how such military advantages could have played a role in the U.S. decision to use the aircraft. As has been demonstrated in the 35 drug boat strikes to date (and surely would have been apparent at the time of the first strike at issue here), U.S. forces can attack them with impunity, without risk, and with great tactical success. While it is true that the Sept. 2 strike was the earliest, it is hard to imagine why a very robust force would be concerned that a boat in transit that already had been located by U.S. forces might be able to get away if it spotted a military aircraft in the area, and that therefore they had to employ one appearing to be civilian to lull the crew into complacency. And in terms of vulnerability to attack from those aboard the boat lest they be alerted, it is unlikely that the boats posed much of a threat to intercepting aircraft or vessels had they been identifiable as military platforms – that is, reporting to date has not indicated the boats were armed with weapons that could have posed such a threat. Therefore, it is highly unlikely that the U.S. armed forces conceived a plan to sneak up on the drug boats to execute the strike successfully. This being so, the operation would not amount to perfidy had there been an armed conflict.
A second possible reason is that perfidious attack is limited to circumstances in which the specific intent is to feign protected status in order to kill or wound persons. The prohibition arguably does not extend to actions targeting objects; in other words, killing or wounding must be the intention, not the consequence. As noted in Bothe et al.’s New Rules for Victims of Armed Conflict commentary on Article 37, “sabotage or the destruction of property as such through the use of perfidious deception is not prohibited (page 234; see also Dinstein, page 305).
By this interpretation, even if the U.S. forces intended to feign civilian status to trick the boat crew, if the boat allegedly laden with drugs was the target, not the crew, the requisite intent may not have been present. True, those aboard the boats were almost certainly going to be incidentally killed or wounded. However, if the mission was solely to stop the shipment of drugs, not to deprive the cartels or gangs of those who transport them, that would be relevant to application of the perfidy rule.
Despite the lack of access to all the facts, the intent requirements described above would seem to preclude characterization of the use of the seemingly civilian aircraft to mount the Sept. 2 attack as perfidy (again, assuming the prohibition on perfidy applies during non-international armed conflict and according to the erroneous U.S. view that such a NIAC was ongoing).
Was the Use of the Aircraft to Conduct the Attack Lawful?
It is well-settled in international law that “only military aircraft are entitled to engage in attacks in armed conflict” (DoD Law of War Manual, § 14.3.3.1; see also UK LOAC Manual, ¶ 12.34). This long-standing rule is based on the authoritative, albeit non-binding, 1923 Hague Rules of Air Warfare (art. 13).
The Harvard AMW Manual experts agreed with the rule in principle, but concluded that it did not bar the use of civilian aircraft during non-international armed conflict, which the administration (wrongly) claims to have been engaged in on Sept. 2 (Harvard AMW Manual, rule 17(a) commentary). To support its position, it pointed to the use of law-enforcement aircraft during such conflicts.
No such caveat appears in the DoD Manual, even though it post-dated the AMW project. Similarly, the UK Law of Armed Conflict Manual fails to distinguish the application of the rule in international and non-international armed conflict. And the German Law of Armed Conflict Manual appears to accept the rule in all armed conflict, noting, “Only military aircraft are entitled to conduct air operations. This also applies to all enforcement actions that do not in themselves entail the use of weapons such as intercepting, diverting or forcing to land other aircraft for the purpose of inspection” (¶ 1115).
If the Harvard AMW experts are right, there would be no violation of the limitation. But if the rule applies to all armed conflicts, the question becomes whether the aircraft is of military character.
The Harvard AMW Manual experts defined a military aircraft as “any aircraft (i) operated by the armed forces of a State; (ii) bearing the military markings of that State; (iii) commanded by a member of the armed forces; and (iv) controlled, manned or preprogrammed by a crew subject to regular armed forces discipline” (rule 1(x), rule 13(j)). The requirement of being marked is based on the Hague Rules of Air Warfare (art. 3).
The UK’s LOAC manual is in agreement with the marking requirement (¶ 12.10), as is the Canadian Law of Armed Conflict Manual (§ 704) and the German manual(¶¶ 349, 1103). By these standards, the aircraft’s failure to be marked as military precludes its qualification as a military aircraft, and therefore it was unlawful for it to exercise the belligerent right of conducting attacks (again, assuming the limitation applies in a non-international armed conflict, and that such a conflict was in fact occurring, which it was not).
Interestingly, the DoD Law of War Manual takes a broader approach: “Military aircraft may be understood as aircraft that are designated as such by a State that operates them. The United States has not ratified a treaty that requires certain qualifications before an aircraft may be designated as military aircraft.” It cautions that while “[m]ilitary aircraft are customarily marked to signify both their nationality and military character … circumstances may exist where such markings are superfluous” (§ 14.3.3). In explanation of when such marking may be superfluous, a footnote cites as an example situations in which “no other aircraft except those belonging to a single state are flown” (citing the 1976 Air Force Pamphlet 110-31).
Yet, it merits note that the Air Force Pamphlet cited by the DoD’s Law of War Manual also states that “while engaging in combat operations, military aircraft, as entities of combat in aerial warfare, are also required to be marked with appropriate signs of their nationality and military character” (§ 7.4, emphasis added). In other words, it appears that despite the mention of situations in which marking is superfluous in the DoD Law of War Manual, the U.S. position tracks those of other States vis-à-vis the circumstances at hand. At least with respect to belligerent rights, such as the right of attack, the aircraft concerned must be appropriately marked as military.
Conclusions
From the analysis above, a number of conclusions can be drawn about the Sept. 2 use of an aircraft to conduct the attack on the alleged drug boat.
- As there was no armed conflict, the law of armed conflict, including the prohibition of perfidious attack, was inapplicable. Instead, the U.S. attack violated the right to life of those aboard the boat and may have constituted murder by some of those involved.
- As the incident did not occur during an armed conflict, there was no requirement to mark the aircraft as a military aircraft.
- Had the law of armed conflict applied because the situation qualified as an armed conflict (it did not), the rule prohibiting perfidious attack would not have applied since U.S. forces likely did not intend to deceive the adversary to secure a military advantage.
- Even if U.S. forces did want to deceive those aboard the boat to achieve a military advantage, the prohibition on perfidious attack arguably only applies to situations in which the goal is to kill or wound, not to damage or destroy objects like drugs and boats transporting them (which may have been the case in this strike).
- Only military aircraft may conduct attacks during an international armed conflict. Whether this rule applies to non-international armed conflict is less settled.
- To qualify as a military aircraft during an armed conflict, the prevailing view is that aircraft must be marked as such, at least while engaged in combat operations.
- If the limitation of attacks to military aircraft applies during a non-international armed conflict, and such a conflict had been underway (it was not), the use of an unmarked aircraft to conduct the Sept. 2 attack would have been a LOAC violation.
The confused and confusing discussion that resulted when the use of a military aircraft to conduct the Sept. 2 attack came to light underscores the importance of first identifying the applicable body of law before rendering legal analysis. It also drives home the unintended knock-on consequences of asserting unsupportable legal claims, as this administration has repeatedly done. Indeed, but for its legally incorrect claim that a non-international armed conflict was underway at the time, the use of an aircraft that was not marked as military would have raised no additional legal issues at all beyond the unlawfulness of the strike itself.
FEATURED IMAGE: CARIBBEAN SEA – SEPTEMBER 22: In this handout provided by the U.S. Navy, An AH-1Z Cobra, assigned to Marine Medium Tiltrotor Squadron (VMM) 263 (Reinforced), fires an air-to-ground missile (AGM) 114N during a live-fire exercise on September 22, 2025 in the Caribbean sea. (Photo by Andrew Eggert/U.S. Navy via Getty Images)
Great Job Michael Schmitt & the Team @ Just Security Source link for sharing this story.
