Matilda 1: A Stern Landing Vessel as a Test Case in USMC–Australian Army Co-Invention
In an earlier article I have argued that the U.S. Marine Corps and the Australian Army are engaged in a process of co-invention: two allied land and expeditionary forces, confronting the same Indo-Pacific strategic problem, arriving independently at compatible answers, and then testing those answers against each other through shared exercises and shared terrain.
Marine Rotational Force–Darwin has been the most visible venue for that process.
But co-invention is not only conceptual. It also happens at the level of a single platform, procured through an unusual leasing arrangement, that forces both institutions to confront a shared capability gap in real time. The stern landing vessel Matilda 1, chartered by the U.S. Marine Corps and homeported in the Northern Territory in partnership with the Australian Army, is exactly that kind of platform. It is small, unglamorous by the standards of major shipbuilding programs, and easy to overlook next to the F-35 or the Amphibious Combat Vehicle.
But it deserves close attention precisely because it shows co-invention operating at the level where doctrine meets deck plates: a single Australian-designed hull, leased rather than purchased, crewed jointly, and used to generate the operational data that will shape a much larger U.S. Navy shipbuilding decision still years from being finalized.
The Capability Gap Driving the Charter
The Marine Corps’ Force Design transformation rests on the idea of the Stand-In Force: small, distributed units operating forward, inside an adversary’s weapons engagement zone, generating sensing and targeting value for the wider joint force rather than massing for a single decisive engagement. That concept only works if those small forward units can actually be moved, supplied, and repositioned across a maritime theater defined by thousands of scattered islands, few developed ports, and shallow, tidal, often poorly charted coastal water. Large amphibious ships and fixed port infrastructure cannot reach most of that terrain. The Marine Corps has needed, for some time, a way to land people and equipment directly onto irregular beaches without depending on a pier or a well-deck, and to do so cheaply enough and often enough that it becomes routine mobility rather than a special operation.
That gap sits between two existing solutions that each solve only part of the problem. Large-deck amphibious ships and the future Light Amphibious Warship program address long-range lift and survivability but cannot access most nearshore terrain. Small landing craft can beach but lack range, seakeeping, and cargo capacity.
The stern landing vessel is a third category: a commercial design lineage, refined over roughly three decades of Australian coastal cargo service, that combines a conventional ship-like bow for open-ocean transit with a reinforced stern ramp and hull geometry purpose-built for repeatedly backing onto a beach, holding position while cargo moves off, and reversing back to sea. It is, in effect, a cargo ship that can also behave like a landing craft on demand.
From an Improvised Prototype to a Purpose-Built Hull
Before Matilda 1 entered service, the Marine Corps had already tested the underlying operational concept using an improvised stand-in: a converted commercial offshore support vessel, the HOS Resolution, fitted after the fact with an oversized stern ramp, a reinforced deck, and landing legs to approximate what a purpose-built stern landing vessel might offer. That vessel was put through a series of evaluations, including Project Convergence Capstone 4, where Marines tested ramp gradients, beach interaction, vehicle compatibility, and shore-to-shore movement against the service’s actual vehicle fleet.
The exercise proved the concept was viable, but it also demonstrated the limits of adapting a hull never designed for the mission. Matilda 1 represents the next step: a vessel designed from first principles for beaching rather than retrofitted for it, built by the Queensland naval architecture firm SeaTransport and constructed by Karimun Anugrah Sejati in Batam, Indonesia, drawing on a design lineage that has operated in Australian commercial service for decades delivering vehicles, livestock, containers, and bulk cargo to remote coastal communities.
At 73 meters (240 feet), Matilda 1 is substantial for a vessel intended to sit on a beach. It can carry roughly 550 tonnes of cargo across 4,000 nautical miles of open ocean in high sea states, arriving with a ship-like bow before presenting a 12.7-meter-wide stern ramp once it reaches shallow water. Its cargo deck, described by SeaTransport as nearly twice the area of a standard tennis court, can accommodate bulk supplies, military vehicles, and double-stacked shipping containers. The tri-hull configuration is the design detail that matters operationally: it protects the propulsion and steering gear during beaching and prevents the hull-suction effect that afflicts conventional flat-bottomed landing craft when they try to withdraw from soft sand or mud.
SeaTransport has noted that the Marine Corps’ charter marks the first time any military force anywhere has adopted a true stern landing vessel design for operational service, despite more than twenty broadly similar commercial vessels already operating worldwide — a reminder that this is a case of the U.S. military importing a mature civilian design concept rather than commissioning something wholly novel.
Proving the Concept at Darwin
Matilda 1’s move from commercial concept to military platform was tested methodically rather than declared by press release. The vessel first completed contractor sea trials and end-user acceptance trials before transiting to Darwin. A week before its first beach landing, it underwent dry-out berthing trials in the mangrove mudflats of Hudson Creek, an estuary near Darwin, settling onto soft sediment through a tidal cycle and successfully refloating, a scenario chosen deliberately because soft, tidal seabeds are exactly what defeats conventional landing craft.
On 8 July 2026, Matilda 1 conducted its first live beach landing at Dundee Beach, southwest of Darwin, backing onto the shoreline, lowering its stern ramp onto the sand, holding position through a simulated unloading sequence, and reversing back into deeper water in under a minute. U.S. Marine Corps personnel were aboard for the landing, with members of the Australian Defence Force observing — a small but telling detail, since it means the first operational validation of the vessel was itself a joint activity rather than a unilateral U.S. test witnessed afterward by an ally.
The three-year charter that followed is intentionally structured as an experimentation program rather than a simple logistics contract. It is managed by MariGuard LLC on behalf of the Marine Corps Warfighting Laboratory, and its explicit purpose is to allow direct, comparative measurement of cargo throughput, fuel consumption, crew requirements, loading time, maintenance burden, beach availability, and mission completion rates against the improvised HOS Resolution approach that preceded it.
That framing matters: Matilda 1 is not being procured as a program of record. It is an instrumented experiment, designed to generate the kind of operational data that a requirements document alone cannot produce, in the same way that Steel Knight functioned as an operational proof of concept for the Marine Corps’ broader impact force transformation rather than a simple training exercise.
Institutional Co-Invention, Not Just Technology Transfer
What makes Matilda 1 a genuine case of co-invention, rather than simply an American purchase of Australian technology, is where the vessel lives and who it is built to serve. Matilda 1’s permanent homeport is in the Northern Territory of Australia, positioned specifically to support units such as Marine Rotational Force–Darwin and the Australian Army’s 1st Division. Aaron Hatfield, Maritime Program Manager in the Science and Technology Division at the Marine Corps Warfighting Laboratory, described the arrangement plainly: the vessel gives Stand-In Forces a way to move personnel and equipment across contested littorals without relying on fixed ports or large amphibious shipping, and operating it alongside the Australian Army is a near-term, allied solution to a real capability gap.
That is co-invention language almost verbatim, a capability gap identified by one institution’s force-design process being closed, in the near term, through operational partnership with the other institution’s forces rather than through either side acting alone.
The practical mechanics reinforce this. U.S. Marines and Australian soldiers embarked on Matilda 1 together for the first time in July 2026, meaning the vessel’s operating concept is being developed with mixed crews from the outset rather than handed to the Australian Army as a finished U.S. product or leased to the Marine Corps as a finished Australian one.
The experimentation phase is explicitly focused on logistics-centric maneuver and sustainment and on refining tactics, techniques, and procedures for the littoral water space, the same sustainment problem that Building the Impact Force identifies as the binding constraint on the entire impact force concept, and the same problem that the Australian Army’s own littoral pivot treats as a precondition for any persistent forward presence in the archipelago.
Matilda 1 does not resolve that sustainment gap by itself. But it is a direct, physical attempt to close a piece of it, using an Australian hull, Australian crews, an Australian home port, and a Marine Corps requirement, in a single instrumented package.
A Deliberately Chosen Name
The vessel’s name is not incidental, and it is worth taking seriously as evidence of how both institutions understand what they are doing. MATILDA 1 honors the relationship between the U.S. 1st Marine Division and the Australian Army forged during the Second World War: after the Battle of Guadalcanal, the 1st Marine Division adopted the Australian folk song “Waltzing Matilda” as an unofficial anthem, a gesture that has remained part of Marine Corps institutional memory for more than eighty years.
Naming a jointly operated experimental logistics vessel after that legacy is a small act of institutional signaling, a way of telling both services’ personnel, and each other, that the current partnership is understood as a continuation of a shared history rather than a novel transactional arrangement. Colonel Kenny Jones, Science and Technology Division Director at the Marine Corps Warfighting Laboratory, framed the charter as risk reduction for future requirements rather than as a finished capability: the lessons generated will directly benefit both the Marine Corps and the Navy, and experimenting with the vessel in real-world littoral environments today is intended to actively reduce risk and shape the operational requirements for tomorrow’s integrated naval fleet.
Bridging to a Program of Record
That last point is the mechanism by which a single leased commercial-derived hull becomes strategically significant rather than a minor logistics footnote. Matilda 1 is explicitly positioned as the second platform in a sequence of experimentation while the U.S. Navy matures its Medium Landing Ship program, the successor to the now-cancelled Light Amphibious Warship effort.
In other words, the charter is not simply solving today’s Stand-In Force mobility problem in northern Australia. It is a deliberate, allied mechanism for reducing acquisition risk on a major future U.S. Navy shipbuilding decision, using an operational Australian design as the empirical stand-in for requirements that would otherwise be generated through paper studies and modeling alone. This is co-invention functioning across time horizons simultaneously: an immediate, tactical answer to a Marine Corps logistics gap in the near term, and a live data-generation exercise shaping a Navy program of record that will not deliver ships for years.
Governance Implications
The Matilda 1 case illustrates, in miniature, an argument I have made about the broader Australian Army–Marine Corps relationship: decisions that appear to be purely national or purely programmatic are, in practice, no longer separable once co-invention has become operational rather than conceptual. A charter negotiated by the Marine Corps Warfighting Laboratory, homeported on Australian soil, crewed jointly, and designed to inform a U.S. Navy shipbuilding program is not a matter that sits neatly inside either country’s normal acquisition governance.
The data Matilda 1 generates about beach availability, fuel consumption, and maintenance burden in the Timor Sea and the approaches to northern Australia will shape assumptions the Australian Army makes about what sustainment support it can expect from a rotating U.S. force in a contingency, just as Australian infrastructure and crewing arrangements shape what the Marine Corps can assume about the vessel’s availability and reliability. Treating the charter as a self-contained U.S. logistics experiment, rather than as a shared allied laboratory with implications on both sides of the relationship, would understate what is actually happening at Dundee Beach and Hudson Creek.
Conclusion
Matilda 1 will not, by itself, resolve the sustainment gap that both the Marine Corps and the Australian Army have separately identified as the central constraint on their respective force-design transformations. It is one leased hull, on a three-year charter, undergoing an explicitly experimental program.
But it is a useful and concrete illustration of what co-invention looks like when it moves from doctrine and exercise design down to a single platform. An Australian commercial design lineage, refined over decades for a purpose no one originally intended for military use, has been adopted by the Marine Corps to solve a Stand-In Force mobility problem; homeported in partnership with the Australian Army; crewed jointly from its first embarkation; and instrumented to shape a future U.S. Navy shipbuilding program, all under a name chosen deliberately to invoke a wartime partnership eight decades old.
That is co-invention operating exactly as the broader Marine Corps–Australian Army relationship suggests it should: not one ally borrowing the other’s finished answer, but two allied forces discovering, testing, and refining a shared answer together, on the same beach, in real time.
Bibliography
Australian Defence Magazine. “SeaTransport Matilda Completes Beach Landing Trials.” Australian Defence Magazine, July 2026. https://www.australiandefence.com.au/news/news/seatransport-matilda-completes-beach-landing-trials.
Australian Naval Institute. “SeaTransport in Successful Beach Landing.” Australian Naval Institute, July 2026. https://navalinstitute.com.au/seatransport-in-successful-beach-landing/.
Baird Maritime. “Vessel Review | Matilda 1 – New Stern Landing Vessel Boasts Long-Distance Navigation Capability.” Baird Maritime, March 18, 2026.
Carroll, Emily. “MCWL Charters New Stern Landing Vessel to Spearhead Marine Corps Littoral Modernization.” Marine Corps Warfighting Laboratory, Futures Directorate. U.S. Pacific Command News Articles, July 17, 2026.
Defence.info / Second Line of Defense. “The U.S. Marine Corps and the Australia–Indonesia Amphibious Turn: Quiet Co-Invention in the Littorals.” Second Line of Defense, May 15, 2026.
Defence Blog. “Australian-Made Ship Could Reshape How Marines Resupply Troops.” Defence Blog, July 2026.
https://defence-blog.com/australian-made-ship-could-reshape-how-marines-resupply-troops/.
Global Defense Corp. “Australian-Made Landing Craft Could Reshape How U.S. Marines Resupply Troops.” Global Defense Corp, July 15, 2026.
Army Recognition. “Australia’s Matilda 1 Stern Landing Vessel Completes Beach Trials for US Marine Corps Logistics.” Army Recognition, July 2026.
https://www.armyrecognition.com/news/navy-news/2026/matilda-1-stern-landing-vessel-usmc-trials.
From Hosting to Co-Invention: The USMC and the Australian Army in Evolution