EU High Representative Kaja Kallas said on Monday, 28 September, as she arrived in Brussels for the Foreign Affairs Council at defence-ministers’ level, that Operation Aspides still needs more naval assets and that the need is “greater than ever.” Speaking to reporters before the meeting, she said she had urged member states to contribute more ships to the Red Sea mission and had received no new firm commitments. Kuwait’s news agency, carried by Kuwait Times, quoted her noting numerous requests for vessel escorts. Iran International, timestamped 07:34 GMT+1, reported her as saying more ships were needed for Aspides “to become operational.” That doorstep is the primary for this note. It is not a rewrite of her 21 September United Nations line that the mission needed more than ten warships, of Italy’s 18 September national-escort file, of Friday’s Maersk 67 / CMA CGM 60 Suez counts, or of the Yanbu war-risk premium already on this blog.
The meeting is the date Kallas pointed member states toward after Italian Defence Minister Guido Crosetto’s 18 September letter and her own 19 September letter to the EU-27. Monday’s public result, as of the arrival statements, is that the escort queue is still longer than the force. Diplomats have told Reuters that about six warships are operating with the mission. Kallas said last week that when Aspides was stood up the indication was at least ten ships and that “the situation, I think, is even more grave right now.” Monday did not close that gap with named new hulls. Do not brief it as a Bab el-Mandeb clearance, a restored Suez container pattern, a listed-area change, or a European substitute for US cover in the Red Sea.
The cover the mission can actually give is the constraint
EUNAVFOR Aspides was launched in February 2024 as a defensive maritime-security operation after Houthi attacks on merchant shipping. Its area of activity covers major routes around the Bab el-Mandeb Strait and international waters in the Red Sea, Gulf of Aden, Arabian Sea, Gulf of Oman and the Gulf. The Council extended the mandate in February 2026 until 28 February 2027 after a strategic review and allocated nearly €15 million in common costs from 1 March 2026 through the end of that mandate. In March the Council also expanded the task list to include collecting and sharing information on suspicious activity related to critical submarine infrastructure, training Djiboutian maritime forces and cooperating with the Yemeni Coast Guard. Those extra tasks sit on the same hulls. They do not create extra escorts.
Crosetto wrote to Kallas on 18 September calling for “decisive and extremely urgent” contributions from other member states, according to Italian reporting of the letter. He said Aspides did not have enough assets to meet merchant requests for protection and warned that Italy could use naval assets already deployed under Aspides to escort Italian merchant ships through Bab el-Mandeb on a national basis, saying Rome “could not wait for EU bureaucracy.” A Rome diplomatic source told Euractiv that a meaningful impact would require a dimension closer to double the current size. Kallas’s 19 September letter, seen by Euractiv, said Houthi control of Mocha port, Perim Island (Mayyun) and the Hanish Islands had given the group greater leverage over Bab el-Mandeb, and that one conclusion was already known: “We need more and well-equipped naval and air assets,” including more close-protection capacity. She asked capitals to propose possible actions ahead of the 28 September Foreign Affairs and Defence Council, including reinforcement of Aspides and Atalanta.
Il Sole 24 Ore, writing on 26 September ahead of the meeting, said Greece is leading the operation, that Italy currently has one frigate in the region to which two minesweepers could be added, and that many partners are aware of the passage’s importance but short of resources. A diplomat told the paper that, apart from resources, some governments have reassessed involvement after recent Houthi attacks. Belgium was reported as willing to make a ship available; France and the Netherlands were described as possible. Paris currently has two vessels in the region, typically stationed toward the Strait of Hormuz rather than as a standing Bab el-Mandeb escort. Those are pre-meeting reports of willingness, not Monday pledges. Kallas’s arrival line is the one that can be used operationally: no new firm commitments, numerous escort requests, need greater than ever, and a mission she described as still short of what it takes to be operational.
Operators should treat escort as rationed, not as a corridor
Houthi forces still hold Mocha, Mayyun and the Hanish Islands and the Yemeni Red Sea coast. Abdul-Malik al-Houthi’s “safe except Saudi” targeting rule remains the published political line, not a traffic-management product. Independent commodity counts through Bab el-Mandeb have stayed well below the Houthi “more than 40 a day” claim already examined on this blog. Dry bulk, certain products and a limited tanker set without Saudi affiliations are what still move; box lines that have returned some hulls to Suez are doing so on their own commercial calculus, not because Aspides can now cover a restored 80-a-week container canal. Maersk’s September count of 67 ships and CMA CGM’s 60, reported at the Suez Canal Authority meeting in Ismailia, sit beside that cover gap. They are not evidence that European close protection is available on demand.
The operational implication is a booking problem, not a press-conference problem. A Master who files for an Aspides escort is competing for a force Kallas says is below the original ten-ship assessment and has not been topped up on the day ministers met. If the request is not accepted, the alternatives are the same as last week: delay, group with other traffic if the operation offers that product, proceed unescorted under the company’s BMP and flag guidance, or divert via the Cape. Italy’s national-escort option, if used, is a national product for Italian merchant ships. It is not a general-traffic lane. French hulls reported in the wider region are not automatically a Red Sea close-protection screen. US aerial support that exists in Hormuz is not an on-request Red Sea cover, a point already recorded in the Yanbu war-risk file. Quoted war-risk for Saudi-linked tankers calling Yanbu has been running around 3 percent of hull value, with Jizan and ports south of Yanbu reported up to 7 percent. That market does not move because a High Representative asks for more frigates.
The extra March tasks on submarine-cable information, Djibouti training and Yemeni Coast Guard cooperation matter for the mission’s workload. They do not change what a commercial operator can count on at Bab el-Mandeb tonight. A force that cannot meet “numerous” escort requests while also watching cables and running partner training will ration close protection. Companies that have written Aspides into voyage instructions as if it were a standing convoy should rewrite those instructions against the Monday doorstep: the operation is still asking for hulls, not announcing them.
What Operators Should Note
- Treat Monday as a no-new-hulls readout, not as a pending yes. Kallas said on arrival that she had urged contributions and had received no new firm commitments. Do not hold a Suez or Bab el-Mandeb booking on the assumption that Belgium, France, the Netherlands or Italy’s extra minesweepers were pledged in the room. Pre-meeting “reportedly willing” lines are not sailing orders.
- File escort requests early and write a no-escort plan on the same form. Kuwait Times, via KUNA, recorded “numerous requests for vessel escorts.” A late request against about six operating warships is likely to be declined. The fallback — delay, unescorted transit under BMP and flag guidance, or Cape diversion — should be in the Master’s pack before the QST is sent.
- Do not read a Suez box-ship return as Aspides cover. Maersk 67 and CMA CGM 60 in September are commercial counts already on this blog. They do not mean close protection is available for a follow-on tanker, a Saudi-affiliated hull, or a first-time returnee. War-risk, charter warranty and BMP remain the binding stack.
- Keep Italian national escort, Aspides and US Hormuz cover in separate columns. Crosetto’s 18 September letter contemplated using Italian Aspides hulls to escort Italian merchant ships if the EU did not reinforce. That is a national product. It is not a general Bab el-Mandeb lane. US coordinated protection in Hormuz is a different theatre and is not automatic on private request in the Red Sea.
- Leave Mocha, Mayyun and Hanish on the threat board. Kallas’s 19 September letter treated Houthi control of those positions as greater leverage over the strait. Al-Houthi’s “safe except Saudi” line is a targeting statement, not a clearance. Saudi-linked tankers, Yanbu callers and hulls with a Saudi commercial connection remain in a different war-risk bucket from unassociated Red Sea transits.
- Do not brief the March submarine-infrastructure task as cable protection for your ship. Information-sharing on suspicious activity near critical submarine infrastructure is an Aspides task expansion. It is not a guarantee that a merchant ship loitering, drifting or conducting underwater work will be screened, and it is not a substitute for coastal-state consent and notice regimes in an exclusive economic zone.
- Keep this file separate from Hormuz diplomacy and from JMIC. Monday’s Hormuz notes on this blog — JMIC still at severe, Iran’s conditions unchanged after the seven-day plan was rejected — are a different strait and a different force. Aspides does not become “operational” because oil is moving in the Gulf, and Hormuz does not reopen because EU ministers met in Brussels.
Regulas Shipping will keep lining Kallas’s 28 September arrival statements against the six-hull operating count and the unmet escort queue so operators can treat Aspides as a rationed defensive product through February 2027, not as a corridor or a substitute for voyage-specific war-risk and routing decisions.
