Star Citizen Ironclad Assault Review: Is It Worth Owning?

The Drake Ironclad Assault is easier to justify when treated as a mobile support platform rather than simply a more expensive Ironclad.

Its Alpha 4.10.0 vehicle record lists 1,440 SCU of cargo, dimensions of 117 × 50 × 25 meters, 130 m/s SCM, 940 m/s NAV, 278,000 ship HP, 144,000 ship-level shield HP, a 7–8 crew field, three manned turret positions, five remote turret positions, and ten Size 5 missiles. It also carries the detachable Command Module used by the Ironclad family.

Those specifications explain what the ship contains, but not why someone would choose it over the standard Ironclad. The Assault gives up 760 SCU of cargo-grid capacity in exchange for a configuration built more heavily around vehicle deployment, combat support, and Ship Hangar Services.

CIG confirmed that the ship launched in Alpha 4.8 with an initial implementation of Ship Hangar Services that allowed ground vehicles and spacecraft inside the ship to use repair and refueling services. That makes the Assault particularly relevant to organizations that actually deploy vehicles, snubs, or other small craft away from conventional service locations.

For a cargo owner who rarely uses those facilities, the trade is much harder to justify.

This review focuses on that ownership question rather than repeating the full specifications already covered in the Star Citizen Ironclad Assault Guide.

The Ironclad Assault Works Best as a Mobile Support Base

The Assault's strongest use case begins after it arrives.

A conventional transport delivers cargo or vehicles and then waits for the next trip. The Ironclad Assault has a stronger reason to remain at the operating area because its support functions can continue contributing after deployment.

CIG's DefenseCon 2956 Q&A states that the Assault launched with the initial implementation of Ship Hangar Services. At that time, repair and refueling were available ship-wide to compatible vehicles and spacecraft inside the vessel. CIG also described a future plan to restrict those services to the rear third of the cargo bay.

That launch-era implementation gives the ship a genuine forward-operating-base role. A crew can transport vehicles, deploy them, recover them after use, and return them to the ship for servicing instead of treating the Assault as a one-way delivery platform.

The important version limitation is that the Q&A describes the Alpha 4.8 implementation. It does not independently prove that every service boundary remains identical in Alpha 4.10.1, so ship-wide servicing should not be presented as a permanently verified current rule.

Why repair and refueling matter more than another turret

The Assault has considerably more weapon infrastructure than a basic transport, but its support capability changes the mission more fundamentally.

A damaged vehicle that can return to the ship for repairs may remain useful during a longer operation. A small spacecraft that can return for fuel can continue operating around the parent ship without immediately ending the session.

That makes the Assault relevant to organization events, remote industrial activity, convoy support, or coordinated ground operations where the crew wants to remain deployed for an extended period.

The ship does not eliminate logistics. It relocates more of those logistics onto one large platform.

The Fabricator Is Still a Future-Value Problem

The Ironclad Assault includes a fabricator, but it should not be a major reason to buy the ship today.

CIG stated in the DefenseCon 2956 Q&A that the fabricator was not enabled at launch because fabrication directly to and from vehicle cargo grids was not yet available. The intended system is planned to use available blueprints through that cargo-grid workflow in a future patch.

That distinction matters because the fabricator appears central to the ship's long-term support identity. A buyer can easily imagine the Assault as a mobile workshop capable of combining transport, repair, refueling, and manufacturing, but only part of that package was documented as implemented at launch.

The safest ownership case therefore ignores fabrication entirely. If the Assault already makes sense for your group because of its vehicle capacity, weapons, repair and refueling services, and internal space, future fabrication can be treated as an additional benefit if and when it becomes available.

Without newer official implementation evidence, it should not be described as an independently confirmed Alpha 4.10.1 capability.

1,440 SCU Is Plenty — Until Cargo Becomes the Main Job

The Assault's 1,440 SCU remains a very large cargo capacity. Its Alpha 4.10.0 data lists two 720-SCU cargo grids, giving the ship substantial room for supplies and freight even though the variant prioritizes vehicle support.

That capacity makes the Assault more flexible than a narrowly specialized dropship. A crew can carry vehicles while retaining room for equipment, commodities, recovered cargo, or mission supplies.

The problem appears when commercial hauling becomes the primary activity.

The standard Ironclad carries 2,200 SCU in the same Alpha 4.10.0 cargo-grid data, giving it 760 SCU more capacity. CIG separately publishes 2,204 SCU for the standard Ironclad. The reason for the four-SCU discrepancy between those two standard-Ironclad figures has not been established, so both should remain clearly identified by source rather than forcibly reconciled.

For a group that spends most sessions moving freight, giving up roughly a third of the standard Ironclad's cargo-grid capacity is difficult to ignore.

The Ironclad vs Ironclad Assault comparison covers that trade in greater detail. From an ownership perspective, however, the principle is simple:

The Assault needs to justify its lost cargo capacity through activities other than hauling.

If your group regularly deploys and services vehicles or small craft, it can. If it does not, the standard ship is usually easier to justify.

Using the Assault as a Vehicle Carrier

The Ironclad Assault is most distinctive when part of the cargo is not really cargo at all.

Vehicles consume physical space, require maneuvering room, and need a sensible deployment sequence. An operational vehicle bay therefore needs more than a large SCU number.

The Assault provides enough internal scale to organize a genuine vehicle operation rather than merely squeezing one vehicle into spare cargo space. A ground-combat group can carry vehicles and supplies to the same destination, while an industrial group can transport working vehicles or smaller craft alongside equipment and recovered material.

A mixed organization can also use the ship as a temporary staging point instead of returning every asset to a station between activities.

Vehicle capacity still depends on physical fit

SCU does not tell you which combinations will work well.

A theoretically possible layout may leave too little room to maneuver during deployment or recovery. A vehicle may physically fit while blocking another asset behind it, while small spacecraft introduce additional concerns around landing and takeoff clearance.

CIG specifically discussed the Assault carrying multiple Pitbull snubs, supporting the concept of using the ship with smaller craft. That should not be generalized into a guarantee that every fighter or spacecraft that fits geometrically is operationally suitable.

For actual fleet planning, deployment order and recovery workflow matter more than filling every available meter of the hold.

Community Feedback: The Mobile-FOB Use Case Is Real, but Experiences Differ

Community reports provide useful evidence that some owners are using the Assault as a mobile base rather than treating that role as purely theoretical.

In an August 27, 2026 discussion about the Ironclad family in Alpha 4.10, one player described using the Assault “as a mobile FOB with the RRR.” That wording is the player's own description of the experience. It should not be read as confirmation that RSI's DefenseCon Q&A officially documented a complete current-version repair, rearm, and refuel package.

The official Q&A cited in this article directly supports repair and refueling in the initial Ship Hangar Services implementation. The player's broader “RRR” phrasing belongs to the community report.

The same discussion included positive impressions of the mobile-base role while noting other issues such as targeting-pip problems.

A July 29 comparison between the standard Ironclad and Assault showed a similar ownership split. Some players valued the Assault for supporting vehicles and carrying operational supplies, while another preferred the standard Ironclad because its additional cargo space better suited an industrial Prospector workflow.

These comments illustrate why the two variants appeal to different owners more clearly than their MSRP or weapon counts alone.

Reliability evidence is mixed

Community evidence also shows why the Assault should not be assigned a simple reliability label.

An August 30, 2026 player report described serious losses during commodity hauling with an Ironclad Assault, including ships and cargo disappearing or being destroyed unexpectedly. Other participants reported fewer problems, and some discussion attributed part of the experience to broader backend or synchronization issues rather than the Assault itself.

That does not establish an Ironclad Assault-specific failure rate. It also does not support declaring the ship either reliable or broken.

The useful conclusion is narrower: individual experiences during the 4.10 period varied significantly, and problems involving a ship capable of carrying 1,440 SCU can have expensive consequences when they occur.

Prospective owners should therefore treat these Reddit posts as individual player reports, not as substitutes for official mechanics documentation or controlled Alpha 4.10.1 testing.

Crew Is the Real Cost of the Assault

The Alpha 4.10.0 vehicle record lists a 7–8 crew field, while separately enumerating eight crew stations and seven beds. These are different fields and should not be combined into a new official crew requirement.

The larger ownership issue is that the Assault can require two groups of people at once: players operating the ship and players operating the assets being deployed from it.

A transport crew may need a pilot, gunners, engineering attention, and someone coordinating deployment. A ground operation may simultaneously require vehicle crews, infantry, or pilots for the smaller craft being carried.

That means a meaningful Ironclad Assault operation can consume far more human participation than simply filling the ship's onboard stations.

A practical crew example

For planning purposes, five to eight shipboard players can illustrate how duties might be divided during a substantial deployment.

That is an editorial planning example only. It is not CIG's official recommendation, not a tested optimum, and not evidence that the Assault becomes inefficient below five players.

A simpler flight can obviously use fewer people. The limitation is that reducing crew does not remove responsibilities; it concentrates them.

The same player may need to leave a turret to manage a vehicle, pause another task to help with deployment, or leave the cockpit to deal with a ship system. The Assault becomes more useful when enough people are present to perform several jobs at the same time.

Can You Solo the Ironclad Assault?

You can fly it solo, but solo ownership leaves much of the reason for choosing the Assault unused.

A single pilot can move the ship and use its cargo space, but one person cannot simultaneously fly the transport, staff the manned weapon positions, manage several deployed vehicles, respond to engineering problems, and operate a ground force.

That gives the Assault a weaker solo ownership case than the standard Ironclad. The standard ship at least allows a solo player to pursue its primary activity—moving freight—even if loading 2,200 SCU alone is cumbersome.

The Assault's main differentiators are more dependent on simultaneous activities. A solo owner can still transport a vehicle or use the vessel as a mobile base, but the more ambitious the operation becomes, the more strongly the design assumes other players are involved.

Future NPC crew or automation should not be counted as established current ownership value.

Weapons Make the Assault Safer to Deploy, Not a Front-Line Warship

The Assault's Alpha 4.10.0 vehicle record lists three manned turret positions, five remote turret positions, and ten Size 5 missiles.

That is significant firepower for a transport, but the important question is what those weapons are intended to support.

The Assault's underside coverage is particularly relevant when approaching or leaving a landing area, allowing crewed weapon stations to support vehicle or personnel deployment.

That does not make the ship a replacement for dedicated combat vessels. Its weapons are attached to a very large transport hull, and many of them depend on additional players occupying the relevant stations.

Ballistic-heavy defenses create logistics of their own

The current loadout includes large ballistic weapons, including Size 5 AD5B Gatlings on manned positions.

Prolonged combat therefore consumes ammunition, which creates another support requirement during extended operations.

That fits the Assault's broader identity: it does not eliminate logistics. It concentrates logistics, transport, combat support, and vehicle deployment into one platform.

Owners looking for a simple heavily armed cargo ship may find that complexity unnecessary.

Durability Is Harder to Judge Than the Marketing Suggests

The Alpha 4.10.0 snapshot reports 278,000 ship HP and 144,000 ship-level shield HP for the Assault.

CIG also positions the variant as having greater armor emphasis than the standard Ironclad.

Those facts should not be reduced to a simple claim that the Assault always survives more damage. Individual defensive fields describe different systems, and actual survivability depends on hit location, component damage, shields, armor behavior, crew response, and the type of attack.

The Assault's useful defensive advantage is therefore operational rather than a universal numerical verdict.

It has enough protection and weapon coverage to support deployment in conditions where a lightly defended transport would face greater risk, but a ship carrying multiple vehicles, equipment, and crew still represents a concentrated asset.

Losing the transport can compromise the entire operation at once.

The Command Module Is Useful, but It Does Not Change the Assault's Core Role

The Assault uses the detachable Drake Command Module shared with the standard Ironclad.

The Alpha 4.10.0 module record identifies it as an independent Size 2 transport with its own flight capability.

It is useful for personnel movement and emergency separation, but it is not an auxiliary cargo ship. The same record lists 0 SCU of cargo capacity, so it cannot detach with part of the Assault's 1,440-SCU shipment and complete a separate freight delivery.

For an Assault crew, its more interesting value is operational flexibility. The heavy parent ship can remain in one location while personnel use the module for another task.

That may be useful during longer deployments, but it does not fundamentally change the Assault's dependence on crew or its main vehicle-support role.

Value at the $650 Reference MSRP

The Alpha 4.10.0 vehicle record lists a $650 reference MSRP for the Ironclad Assault.

That should not be read as confirmation that RSI currently offers the ship as a $650 standalone pledge. It is also separate from Warbond pricing, CCU pricing, secondary-market pricing, and current pledge-store availability.

At that reference value, the useful question is not whether the Assault includes more systems than the standard Ironclad. It does.

The useful question is whether those systems matter to the owner.

Repair and refueling services are valuable when a group repeatedly operates vehicles or smaller craft. Additional weapon stations are valuable when players actually occupy them. A 1,440-SCU hold is valuable when the organization has enough equipment and supplies to use it.

For a cargo-first player who rarely runs vehicle operations, the same reference value buys a ship that gives up 760 SCU compared with the standard Ironclad while adding capabilities that may sit unused.

The change in role matters more than the $50 difference in reference MSRP.

Ironclad Assault vs Standard Ironclad in Daily Ownership

The most useful distinction is not simply combat versus cargo. It is support logistics versus freight logistics.

The standard Ironclad uses its scale to move more cargo. The Assault uses more of that scale to support a broader operation.

An industrial group that wants maximum room for cargo, equipment, pods, and collected material may prefer the standard ship. Community comments from July 2026 reflect exactly this kind of preference, with some players choosing the regular Ironclad because its additional space better supported their industrial workflow.

A group using ground vehicles or small craft as active mission assets has a stronger reason to choose the Assault.

That ownership split is more meaningful than comparing which variant has the higher MSRP or larger number of weapon stations.

For the freight-focused side of the family, the Star Citizen Ironclad Guide covers the standard ship's cargo workflow, crew burden, Command Module, and ownership considerations.

Who Should Consider Owning the Ironclad Assault?

The Assault has its strongest ownership case for an organized group that repeatedly deploys assets rather than merely transports them.

It makes sense when vehicles and small craft leave the ship, perform meaningful work, return, and benefit from having a support platform nearby. It also suits players who enjoy running a large vessel as the center of a group operation, where piloting, defense, engineering, logistics, vehicle deployment, and ground activity can give different players useful responsibilities.

The ship becomes much harder to justify when that group gameplay does not exist.

A cargo-focused owner gives up freight capacity, a solo owner leaves many systems understaffed, and a player buying mainly for future fabrication is depending on functionality CIG explicitly described as unavailable at launch.

The Assault should therefore make sense based on its currently documented transport and support role before future features enter the calculation.

Final Verdict

The Ironclad Assault is most convincing as a mobile support platform for organizations that genuinely use vehicles and small craft away from normal infrastructure.

Its 1,440-SCU hold is large enough to keep cargo relevant, but cargo alone is not why the variant exists. The ownership case comes from combining transport with deployment, defensive support, and the initial repair and refueling functionality CIG introduced when the ship became flyable.

That combination can turn the Assault into the center of a longer operation instead of a transport that leaves as soon as unloading is complete.

The same design also creates its main weakness: owners need missions that actually use those systems and enough players to operate them. Current community feedback shows both positive and negative individual experiences during the 4.10 period, but those reports do not establish a uniform Alpha 4.10.1 reliability conclusion.

For an organized vehicle-focused group, the Assault has a distinct role that the standard Ironclad does not replicate. For a solo pilot or freight-first owner, the standard Ironclad is usually easier to justify.

FAQ

Is the Ironclad Assault worth owning?

It has a strong ownership case for groups that regularly transport and support vehicles or small spacecraft. Cargo-first and solo owners may benefit more from the standard Ironclad.

How much cargo does the Ironclad Assault carry?

The Alpha 4.10.0 vehicle-data snapshot lists 1,440 SCU, arranged as two 720-SCU cargo grids.

Can the Ironclad Assault repair and refuel vehicles?

CIG confirmed an initial Ship Hangar Services implementation at Alpha 4.8 that allowed ground vehicles and spacecraft inside the ship to use repair and refueling services. CIG also described a future restriction to the rear third of the cargo bay. The Alpha 4.8 service boundary should not be treated as an independently verified permanent Alpha 4.10.1 rule.

Does the Ironclad Assault support rearming?

A community user described operating the Assault “as a mobile FOB with the RRR.” That is a player report. The RSI DefenseCon Q&A directly cited in this article confirms repair and refueling in the initial Ship Hangar Services implementation; it should not be stretched into an official confirmation of a complete current-version RRR package.

Does the Ironclad Assault fabricator work?

CIG stated that blueprint fabrication was not enabled at launch. Without newer official implementation evidence, it should remain treated as planned functionality rather than an independently confirmed Alpha 4.10.1 feature.

Can you solo the Ironclad Assault?

You can fly it alone, but many of its distinguishing features depend on simultaneous ship operation, vehicle deployment, defense, and support activities. A solo player leaves much of that capability unused.

How many players does the Ironclad Assault need?

Its Alpha 4.10.0 data lists a 7–8 crew field, with eight crew stations and seven beds recorded separately. The five-to-eight-player example in this review is editorial planning only, not an official recommendation or tested optimum.

Is the Ironclad Assault better than the standard Ironclad?

Not universally. The Assault is more relevant to vehicle deployment and support, while the standard Ironclad offers more cargo capacity: 2,200 SCU in Alpha 4.10.0 cargo-grid data, compared with 1,440 SCU for the Assault. CIG separately publishes 2,204 SCU for the standard Ironclad.

How much does the Ironclad Assault cost?

The Alpha 4.10.0 vehicle record lists a $650 reference MSRP. This does not confirm a current $650 standalone offer and should not be confused with Warbond, CCU, secondary-market, or current pledge-store pricing.