NBC News reported on Sunday evening, 27 September, that eight US Marines were injured on 14 September when an Iranian cruise missile struck the ship they were operating on in the Strait of Hormuz, according to three US officials. The Marines were not seriously injured. They sustained smoke inhalation and possibly traumatic brain injuries, with concussion symptoms including headaches, the officials told NBC’s Courtney Kube. All eight — seven enlisted and one officer — returned to duty soon afterwards. The officials said the Marines were operating as part of a battalion landing team and were not on a US Navy ship. The Trump administration had not publicly disclosed the incident. That NBC account, dated 9:07 p.m. EDT on 27 September and carried through on Monday by The Washington Post and The Maritime Executive, is the primary for this note. It is not a new 28 September attack, not a named-hull UKMTO product, and not a rewrite of the 23 September Cape Dao fatality or of Sunday’s JMIC severe advisory.
The Washington Post, on Monday afternoon, said eight Marines were injured this month when the nonmilitary vessel on which they were embarked was attacked by Iran. Officials speaking to the Post on condition of anonymity because they were not authorized to discuss the incident characterized the wounds as minor, including smoke inhalation and head injuries, and did not identify the vessel beyond saying it was not operated by the US military. Pentagon spokespeople did not fill that gap in the Monday reporting. Military.com, writing through NBC on Monday morning, described the hull as a non-commissioned commercial vessel in the strait when the cruise missile struck, and said the Pentagon did not announce the injuries but entered them in the Defense Casualty Analysis System. The Maritime Executive noted that a Fox News correspondent had earlier this month reported a “US-contracted” vessel hit by an Iranian munition near Hormuz, injuring US personnel, and treated NBC’s 14 September dating and Marine count as further detail on that unnamed file. Officials declined to give the name, type, flag or exact mission. Private maritime-security sources have previously pointed to a Western-operated vessel hit in the same region on the same day; that identification is not an official naming and is not used here.
Do not recast the Sunday–Monday disclosure as confirmation that every US-facilitated Hormuz transit now carries an embarked Marine team, as a change to UKMTO warning practice, or as a reason to treat a merchant AIS track as a naval unit. The operational fact for commercial operators is narrower and more uncomfortable: US officials now say that on 14 September an Iranian anti-ship cruise missile hit a ship that was not a Navy hull, that Marines from a battalion landing team were on board, and that eight of them took smoke and head injuries that were logged internally but not briefed at the time.
An unnamed nonmilitary hull in a severe-rated strait
The date matters because it sits inside a week this blog already covered from other products. 14–16 September was the El Gaia / Musandam fire and missing Indian seafarer window, the period of reported projectile activity off the Omani coast, and the days around which Fox and EOS Risk Group described a US-contracted vessel hit near Hormuz with US personnel aboard and smoke-inhalation casualties treated in an unidentified Gulf country. NBC now puts a cruise-missile strike on 14 September and names the injured as eight Marines. Whether that is the same hull as the mid-month Fox account is not something Reuters, UKMTO or the Pentagon has put on the record. Operators should keep the files adjacent and unnamed until a company, a flag or a maritime agency identifies a ship. Inventing a name from social-media reconstruction does not help a Master.
What NBC and the Post do establish is the category of ship. It was not a US Navy warship. The Post’s formulation is “nonmilitary” and “not operated by the US military.” Military.com’s secondary wording is “non-commissioned commercial.” Battalion landing teams are Marine infantry embarked for amphibious and maritime-security tasks; they are not a substitute for a published notice to mariners that a particular merchant or contracted hull is carrying armed US personnel. The 2023 USNI reporting that Marines had trained to provide armed security aboard foreign commercial ships transiting Hormuz is background for the mission set, not evidence that this unnamed 14 September ship was on that programme. The War Zone asked US Central Command whether US personnel are embarking on commercial ships in the strait; CENTCOM declined to comment. That refusal is itself an operator input: you may not be told, on AIS or on VHF, that the ship five miles on the bow has US Marines on board.
The casualty picture is deliberately modest in the official telling and still incomplete. NBC said the eight were not seriously injured and returned to duty soon after. Smoke inhalation plus concussion symptoms is still a weapon-effects file on a ship that, if it was commercial or contracted, also had a Master, a crew and, possibly, a cargo. None of those civilian outcomes has been published. UKMTO did not issue a 14 September warning that matches this disclosure by name. JMIC’s later period products listed other unnamed tanker and cargo casualties; they did not, in the material on this blog, identify a Marine-embarked nonmilitary hull. The Pentagon’s internal count, as relayed by NBC and Military.com, puts more than 800 US service members injured in the Iran conflict this year, with Military.com citing 18 publicly acknowledged deaths and a Washington Post claim of a higher fatality total that the Pentagon refuted. Those theatre-wide figures are context for why a single eight-person smoke-and-head-injury event could be absorbed into a database without a press briefing. They are not a substitute for a maritime incident report.
The Maritime Executive added that US forces have been trying to keep commercial traffic moving through the southern Strait of Hormuz and that the methods “do not appear to involve direct US Navy convoy escorts.” CENTCOM has previously spoken about coordinated protection and about a blockade of Iranian ports; it has not published a passenger-or-security-team manifest for contracted hulls. Admiral Brad Cooper’s 19 September claim of more than a billion barrels moved with coordinated protection, and the anonymous US official’s 23 September figure of about 60 ships and 22 million barrels, remain the volume claims already on this blog. They do not tell a Master whether the next US-associated transit has armed personnel on the bridge wing. Iran, for its part, has continued to treat unauthorized Hormuz traffic as a target set. Sunday’s JMIC note still described IRGC presence along key lanes. A cruise missile against a nonmilitary hull with Marines embarked is consistent with that pressure even if Tehran has not claimed this specific ship.
What this does to commercial voyage orders
For owners, charterers and company security officers the disclosure is a crew-knowledge and insurance problem as much as a kinetic one. If a commercial or contracted ship takes US military personnel on board for a Hormuz transit, that fact belongs in the voyage orders, the war-risk proposal, the ISPS record and the Master’s briefing to the crew. It changes who is on the muster list, who has weapons, who talks to approaching military units, and how a Master answers a VHF challenge. It can also change how an attacker classifies the ship. A hull that looks commercial on AIS and carries a Marine battalion-landing-team detachment is not a warship under a naval ensign, but it is also not an ordinary merchantman for targeting and for the law-of-naval-warfare arguments that follow a hit. Crews have a right to know that distinction before the strait, not after a cruise missile and a delayed press story.
If the ship was US-contracted rather than a liner or tramp on a commercial fixture, the operator still owes the same clarity to the seafarers who were already on articles. Smoke inhalation and head injuries on 14 September, logged in a Defense Department casualty system and withheld from public incident channels until 27 September, mean that other ships in the TSS that day had no UKMTO-style warning tied to this hull. Collision avoidance and reporting did not get a named casualty. War-risk underwriters pricing 14 September transits did not get an official Marine-embarked tag. That information lag is now part of the Hormuz picture: kinetic events involving US personnel on nonmilitary ships may be carried in military casualty databases first and in maritime safety broadcasts late, or not at all.
None of this authorises a merchant ship to refuse a lawful charter solely on the rumour of embarked Marines, and none of it makes every US-facilitated tanker a combatant. It does require a question on the fixture and on the security plan: will any foreign military or government security team be on board; who commands them; what is the weapons policy; what is the reporting line if the ship is challenged or hit; and is that arrangement disclosed to the flag, the P&I club and the war-risk writer. A company that cannot answer those questions should not pretend the 14 September file is only a Washington political story. It is a shipboard command-and-control story in a strait that JMIC still rates severe.
What Operators Should Note
- This is a 14 September hit disclosed on 27–28 September, not a new Monday attack. NBC, citing three US officials, dates an Iranian cruise missile to 14 September, with eight Marines injured by smoke inhalation and possible concussion, all returned to duty. The Post says the hull was nonmilitary and not US-military operated. Do not move the casualty onto this week’s position list.
- Do not name the ship. Officials refused name, type, flag and mission. Treat Fox’s earlier “US-contracted” report and private identifications of a Western-operated hull as the same unnamed cluster unless UKMTO, a flag or a company says otherwise. A reconstructed name is not a primary.
- Ask, in writing, whether any military or government security team will be embarked. A battalion landing team on a non-Navy ship changes the muster, the weapons policy and how an approaching unit will classify you. Put the answer in voyage orders, the ISPS record and the war-risk proposal before Musandam, not in a day-message after a hit.
- Do not assume a maritime warning will precede a military casualty. The injuries were entered in the Defense Casualty Analysis System and were not briefed at the time. UKMTO did not publish a matching named product. Other ships in the strait on 14 September had no public tag that a nonmilitary hull with Marines aboard had been struck.
- Keep this file apart from Cape Dao, from unnamed tanker Warnings 140-26 and 141-26, and from JMIC’s 72-hour quiet. Sunday’s severe rating and the 23 September Antigua-flag Capesize fatality are separate products. An undeclared Marine-embarked hit does not downgrade them and does not replace them.
- CENTCOM methods still do not read as a published convoy. The Maritime Executive’s read is that southern-strait facilitation does not appear to be direct US Navy escort. Cooper’s barrel counts and the 23 September 60-ship claim remain volume statements. They are not a passenger list. A Master who is told the transit is “coordinated” should still ask who is on board and who speaks on VHF.
- Crew welfare and club notice come before political narrative. Smoke and head injuries on a ship that also had a civilian crew have not been described for those seafarers. If your hull took a similar fixture, check the people, the medical log and the notification to flag and P&I, regardless of whether Washington has issued a statement.
Regulas Shipping will keep lining NBC’s 27 September disclosure of eight Marines injured on a 14 September nonmilitary Hormuz transit against the still-unnamed hull and the still-severe strait so operators can treat embarked military teams as a voyage-order and crew-information problem, not as a reason to assume every facilitated tanker is a warship or that the public incident channel is complete.
