The Pentagon's Seven-Year Amnesia

How Institutional Forgetting Becomes Strategic Failure

April 30, 2026 | Commentary | Defense & Strategy

On August 18, 2019, the U.S. Navy successfully fired a Tomahawk cruise missile from a ground-based launcher. The missile flew more than 500 kilometers and struck its target accurately. The Pentagon had just demonstrated a working solution to a problem it would still face in 2026.

Seven years later, facing that exact problem—Iranian ballistic missile launchers relocated beyond existing system range—the Pentagon is now requesting deployment of Dark Eagle, an immature hypersonic system with fewer than eight missiles per battery, uncertain operational effectiveness, and a unit cost of $15 million per round.

The Tomahawk system that worked in 2019 could have been deployed by 2021. The Pentagon knew this. It chose a different path anyway.

The institutional memory of that successful 2019 test has simply evaporated. The people who made the decision to deprioritize Tomahawk ground-launch have moved on. The people requesting Dark Eagle deployment in 2026 either weren't in the room in 2019, or inherited a bureaucratic momentum that had already committed elsewhere.

The Pathology: Nearsightedness as Institutional Design

This is not a story of technical failure or unforeseen complications. It is a story of how institutions systematically forget their own solutions and prioritize near-term institutional advantage over long-term strategic resilience.

The Pentagon's nearsightedness is not accidental. It is baked into the structure of how the organization makes decisions:

The Five-Year Defense Plan (FYDP) cycle creates budget myopia. What matters is what can be demonstrated and funded in this budget year and the next. A 2019 decision to scale up ground-launched Tomahawk would show results by 2021–2022, but wouldn't generate headlines in 2024 or 2025. A new hypersonic program generates announcement effects, congressional testimonies, and contract awards spread across multiple years. The incentive structure points toward "new" rather than "mature."

Career incentives reward innovation, not execution. A general gets credit for initiating Dark Eagle. Nobody gets promoted for successfully completing ground-launched Tomahawk deployment. Institutional prestige accrues to the person who proposes something revolutionary, not the person who executes something adequate. The people who made the 2019 decision to pursue hypersonics instead of scaling Tomahawk faced no consequences when their choice led to a 2026 crisis. They had already moved to different positions.

Service parochialism overwhelms joint optimization. Tomahawk belongs to the Navy. The Army wanted something it could call its own. Institutional tribalism matters more than strategic consolidation. So the Pentagon developed Dark Eagle (Army), pursued Mid-Range Capability (joint, but with Army emphasis), and extended PrSM variants (joint), rather than simply scaling the Navy system that already worked. Three development programs instead of one deployment effort.

Technology demonstrations become justifications for continued development, not proof of completed capability. When the August 2019 Tomahawk test succeeded, the Pentagon's response was not "ground-launched Tomahawk is validated; proceed with deployment." The response was "data collected will inform future development." The test became a data point in an extended exploration rather than an endpoint proving the concept. The institution had an escape route: "we learned something; let's keep developing."

The Institutional Memory Problem

The deeper issue is that bureaucratic memory in the Pentagon works on a 3–5 year horizon, not a 10–20 year horizon.

A military officer serves in a position for 2–4 years, then rotates. A senior civilian official serves 4–8 years if they're fortunate. The people who made the 2019 decision to prioritize hypersonics over proven systems are no longer in those positions. Their successors inherited the consequences of those choices without having made them.

This creates a pathological pattern: each cohort of leaders makes decisions that optimize for their tenure. Those decisions accumulate consequences that hit subsequent cohorts. By the time the consequences manifest—as a 2026 crisis requiring emergency deployment of an immature system—the original decision-makers are gone. Accountability dissolves.

Meanwhile, the institutional record of what was tested, what worked, and what was deliberately rejected gets archived in databases nobody reads. The 2019 Tomahawk test wasn't a secret. It was announced publicly. But institutional memory is so short that by 2026, the officials responsible for CENTCOM's capability planning either don't know about it or inherited a bureaucratic trajectory that made it irrelevant.

The core problem: In the Pentagon, institutional memory is measured in budget cycles, not in decades. The vision horizon extends only as far as the next congressional hearing and the current officer rotation timeline. This creates systematic incentive to prefer ambitious long-term programs (which generate career advancement and budget lines for multiple years) over proven short-term solutions (which solve the problem immediately and thus disappear from the budget).

The Accountability Void

Consider what would happen if the Pentagon were accountable for paths not taken. If the 2019 decision-makers were evaluated in 2026 on whether their choice to deprioritize Tomahawk ground-launch was sound, the conversation would be very different.

They would have to explain why, in the face of a successful demonstration of a proven system, they chose to pursue multiple less mature alternatives. They would have to justify the opportunity cost: the resources committed to Dark Eagle development that could have been committed to Tomahawk deployment. They would have to account for the fact that the 2026 crisis could have been prevented with 2019 discipline.

But they won't be evaluated on that basis. The 2019 decision-makers are no longer in those positions. The officials requesting Dark Eagle deployment in 2026 can justify it as a response to an operational requirement. The earlier decision to reject Tomahawk is simply not part of their decision space.

This accountability void is not unique to the Tomahawk case. It is endemic to how the Pentagon operates.

Why This Matters Beyond Missiles

The Tomahawk case is not an isolated failure. It is symptomatic of how the Pentagon systematically underinvests in mature capability consolidation and overinvests in experimental alternatives.

The same pattern appears in cruise missile production (new hypersonic programs outbid conventional system sustainment), air defense (new concepts proposed while existing systems remain incomplete), strategic transport (pursuit of revolutionary new platforms while current fleet ages), and virtually every other major capability domain.

The institutional bias is always toward the new, the advanced, the revolutionary. The mature, the proven, the adequate are chronically underfunded relative to their operational utility.

This would be acceptable if experimental programs reliably succeeded on schedule and budget. They do not. Dark Eagle itself is a cautionary example: three successful tests as of 2026, after years of failures, with DOT&E (Director, Operational Test & Evaluation) assessment that "there is not enough data available to assess operational effectiveness." The system is being deployed not because it has demonstrated superiority, but because earlier decisions to deprioritize alternatives left the Pentagon without options when a crisis emerged.

The Solution Requires Structural Change

No amount of rhetoric about "strategic thinking" or "long-term vision" will solve this problem. The issue is not that Pentagon leaders are shortsighted; it is that the institutional structure systematically rewards nearsightedness.

Fixing this would require:

Accountability for opportunity cost. Decision-makers at the flag and senior executive level should be required to justify not just what they chose to do, but why they chose not to do proven alternatives. When a new development program is initiated, the opportunity cost of not scaling an existing system should be formally documented and revisited at intervals.

Institutional memory that extends beyond rotation cycles. The Pentagon should maintain formal cost-benefit analyses comparing new development programs to the alternative of scaling proven systems. These analyses should be mandatory when capabilities are requested, and should be explicitly retrieved from archives to inform current decisions.

Separate budgeting for proven vs. experimental capability. The current system lumps everything together, which means experimental programs compete for resources against proven systems. A separate budget line for "demonstrated capability scaling" versus "exploratory development" would force explicit choices about trade-offs.

Multi-year officer assignments for acquisition leadership. The current 2–4 year rotation cycle is too short to see the consequences of acquisition decisions. Officers in key acquisition positions should serve 6–8 year terms minimum, making them personally accountable for whether their development decisions actually resulted in deployed capability.

The Larger Truth

The Pentagon's request to deploy Dark Eagle in 2026 is not a statement about Dark Eagle's readiness. It is a statement about the Pentagon's institutional failure to maintain strategic memory and disciplined long-term planning.

The institution tested a working solution in 2019. It then allowed that knowledge to evaporate through the normal churn of personnel rotation, bureaucratic momentum, and institutional preference for ambitious development over mature deployment. Seven years later, facing the exact problem that the 2019 solution was designed to address, the Pentagon found itself without options.

This pattern will repeat. In 2030 or 2035, the Pentagon will find itself requesting emergency deployment of some immature system when an earlier decision to scale a proven capability would have prevented the crisis. And the officials making that request will have no institutional memory of the path they chose not to take.

Institutional memory is short and vision is nearsighted. Until the Pentagon's structure changes to create accountability for paths not taken and incentives for capability consolidation over perpetual development, this pattern will continue.

The cost will be measured not in budget dollars but in operational risk, in capability gaps that open exactly when they are least acceptable, and in the persistent feeling that the Pentagon has the resources to solve its problems but somehow always chooses not to.

Dark Eagle at the Threshold: CENTCOM's Untested Hypersonic Gamble Against Iran

US Central Command requests hypersonic weapons for strikes on Iran: Reports - Daily Excelsior

Cost, Readiness, and the Pentagon's Seven-Year Planning Failure on Conventional Intermediate-Range Strikes

April 30, 2026 | Defense & Aerospace Analysis

BLUF (Bottom Line Up Front)

U.S. Central Command has formally requested approval to deploy the Army's Long-Range Hypersonic Weapon (LRHW), nicknamed Dark Eagle, to the Middle East to strike Iranian ballistic missile launchers reportedly repositioned beyond the range of existing Precision Strike Missile (PrSM) systems. If approved, it would mark the first operational combat deployment of an American hypersonic weapon. However, the request exposes a deeper institutional failure: the Pentagon failed to develop operational conventional intermediate-range systems despite having seven years (2019-2026) after the INF Treaty's termination and explicit Congressional authorization dating to 2015. The Intermediate-Range Nuclear Forces Treaty, which terminated August 2, 2019, had banned both nuclear and conventional ground-launched intermediate-range systems—but research and development were always permitted. The Pentagon did not systematically pursue that legal pathway. Now, facing an operational gap created by Iranian launcher relocation, CENTCOM is requesting deployment of an immature hypersonic system as a stopgap solution. Dark Eagle has not been declared combat-ready, Pentagon testing authority forecasts insufficient operational effectiveness data until early 2027, available inventory is fewer than eight missiles per battery, unit costs exceed $15 million, and recent test data indicate persistent reliability challenges. The deployment reflects both genuine tactical necessity and deep institutional failure in strategic planning.

The Operational Context: An Avoidable Gap

The immediate justification for CENTCOM's Dark Eagle request is straightforward. During Operation Epic Fury—the 38-day air and missile campaign beginning February 28, 2026—U.S. and Israeli forces employed the Precision Strike Missile extensively against Iranian targets. The PrSM, a Lockheed Martin ballistic missile integrated onto the HIMARS rocket artillery platform, carries a range of approximately 500 kilometers (310 miles) and was deployed in its first combat use during those operations.

In response to the opening strikes, Iranian forces relocated their ballistic missile launchers to positions deeper within the country, reportedly beyond PrSM reach. This tactical adjustment created what CENTCOM characterizes as an operational gap: existing conventional strike systems cannot reach dispersed or hardened launcher positions now positioned inland at extended range.

The Dark Eagle, with a reported range of 1,725 miles (2,775 kilometers)—with classified assessments suggesting potential ranges exceeding 3,500 kilometers—would restore the ability to hold those targets at risk. For CENTCOM, the operational logic is clear and tactically valid.

Yet this operational gap was predictable and largely avoidable. The explanation lies in the history of arms control, treaty law, Pentagon institutional decision-making, and Congressional action dating back more than a decade.

The Treaty Context: Why PrSM Is Capped at 500 Kilometers

The Precision Strike Missile's 500-kilometer range ceiling is not an engineering constraint or a cost optimization. It is a direct artifact of the Intermediate-Range Nuclear Forces (INF) Treaty, signed in 1987 by President Ronald Reagan and Soviet General Secretary Mikhail Gorbachev.

The INF Treaty required both superpowers to eliminate and forswear all ground-launched ballistic and cruise missiles with ranges of 500-5,500 kilometers. Critically, the treaty applied equally to systems armed with nuclear warheads and systems armed with conventional warheads. A special clarification adopted during ratification in 1988 made explicit that the treaty covered all missiles falling under its definition "irrespective of whether they were equipped with nuclear, conventional, or 'exotic' warheads."

When the Pentagon began developing what would become the PrSM in the mid-2010s—during the Obama and early Trump administrations—the INF Treaty remained in force and would remain so until August 2, 2019. Consequently, early development contracts specified a range of "499 kilometers"—deliberately just shy of the prohibited threshold. The missile's motor, fuel load, airframe design, and aerodynamics were optimized around this constraint. PrSM Increment 1, now operational and deployed to the Middle East, remains locked at this INF-compliant ceiling.

Extended-range variants—PrSM Increment 2 (also known as the Land-Based Anti-Ship Missile, or LBASM), designed for ranges approaching 1,000 kilometers—are in development but will not be operational until 2027 at the earliest, according to recent Army statements. Secretary of the Army Pete Hegseth only recently (May 2025) directed acceleration of Increment 2 fielding to 2027, moving it up from the previously planned 2028 target. This acceleration came after the Iran war had already expended 45 percent of PrSM Increment 1 stockpiles.

This timeline creates the critical gap: a system designed under treaty constraints became insufficient once the treaty ended, but its successor system remains years from operational deployment.

The Legal and Institutional Failure: A Seven-Year Planning Missed Opportunity

Here is where the Pentagon's institutional failure becomes clear. The INF Treaty prohibited three specific activities: possession, production, and flight-testing of intermediate-range ground-launched systems. However, the treaty explicitly did not prohibit research and development.

Throughout the treaty period (1988-2019), the United States was legally free to conduct theoretical research, computer modeling, conceptual design, and materials science related to intermediate-range missile systems. The threshold of violation came only at production (manufacturing hardware) or testing (launching operational prototypes). The Pentagon could have used this R&D exemption to prepare detailed designs and concept maturity for conventional intermediate-range systems that could transition to production upon treaty withdrawal.

Instead, the Pentagon largely did not. Congressional pressure eventually forced the issue. When the U.S. formally alleged Russian INF violations in 2014, and as those allegations accumulated through 2015-2018, Congress began authorizing explicit Pentagon action. The FY2015 and FY2016 National Defense Authorization Acts called on the Pentagon to study and plan for development of possible military options in response to Russian non-compliance. Most significantly, the FY2018 National Defense Authorization Act (P.L. 115-91, Section 1243) specifically authorized the Defense Department to commence "treaty-compliant research and development" on conventional, ground-launched, intermediate-range missile systems and mandated that the Pentagon begin a "program of record" to develop new systems.

This Congressional authorization in 2018—a full 14 months before the treaty terminated—gave the Pentagon explicit legal and budgetary authority to initiate serious development work on conventional intermediate-range systems designed for operational deployment after August 2019.

The Pentagon initiated some R&D funding and conceptual work, but evidently without the strategic priority or institutional commitment required to deliver operational systems by 2025-2026.

Why? Several institutional factors converged:

• Service parochialism: No single military service had dominant institutional interest in ground-launched intermediate-range conventional systems. The Army had immediate fires requirements addressed by ATACMS and later PrSM. The Air Force and Navy possessed existing air-launched and sea-launched systems reaching intermediate ranges without treaty constraints. There was no powerful advocate within the Pentagon hierarchy for advancing this capability category.
• Peacetime planning atrophy: The 1991-2014 period, following the Soviet collapse, was marked by multiple out-of-area conflicts (Iraq, Afghanistan, Balkans) but not peer-competitor strategic competition. Strategic planning for potential China and Russia contingencies was subordinated to immediate Middle East operational demands. By the time peer-competitor threats were recognized (circa 2015-2017) as central to Pentagon strategic thinking, institutional momentum for ground-launched system development had never been established.
• The hypersonic priority: Once the Trump administration (2017 onward) began identifying hypersonic weapons as a strategic priority—a response to Russian and Chinese hypersonic deployments and a symbol of technological leadership—institutional resources, budget allocations, and prestige flowed to Dark Eagle and related programs. This created a perverse incentive: advancing an immature hypersonic system forward provided visibility and budget justification, while completing conventional system development that had been de-prioritized for a decade received less institutional attention.
• Organizational distance from strategic planning: Operating commands and service requirements branches typically work within the operational environment they inherit. They do not track arms control treaty implications or exploit R&D exemptions. If senior strategic planning staffs (Office of Secretary of Defense Policy, Joint Chiefs, regional commands) had recognized and articulated the requirement for operational conventional intermediate-range systems before 2019, service investment would have followed. Instead, treaty language—even where legally avoidable—became an excuse for organizational inaction.

The Deeper Problem: Seven Years to Develop Alternative Systems Was Available

Consider what the Pentagon should have accomplished on a realistic timeline:

2018-2019 (Treaty withdrawal period): Congress had already authorized R&D. The Pentagon could have initiated aggressive development of conventional ballistic and cruise missile systems designed for the post-treaty environment. Naval Strike Missile variants, extended-range Tomahawk concepts, and conventional ballistic missile designs could all have been prioritized.

2019-2023 (Post-treaty acceleration): With treaty constraints removed, prototype testing could have accelerated. Existing booster technology (the Lockheed Martin two-stage design shared between PrSM and Dark Eagle) could have been integrated with conventional guidance systems. The baseline for PrSM Increment 2 design was already mature; aggressive production scheduling could have moved first operational units to the field by 2023-2024.

2023-2026 (Current operational window): Extended-range conventional systems could be operational in theater by the time Iranian launchers relocated. Instead, Army leadership only recently (May 2025) directed acceleration of Increment 2 fielding from 2028 to 2027—after the operational gap had already emerged and after PrSM Increment 1 stocks had been largely expended.

This is not a timeline constrained by physics, technology, or law. It is a timeline constrained by institutional priorities and budget cycles that valued hypersonic demonstration over conventional system completion.

The Development Trajectory: Dark Eagle's Troubled History

The Dark Eagle program has accumulated approximately $12 billion in development funding since 2018, making it one of the Pentagon's most resource-intensive advanced conventional weapon initiatives. Yet the program's testing history reveals a troubled development arc marked by delays, failures, and incomplete evaluation.

Between October 2021 and September 2023, multiple planned flight tests either failed outright or were scrubbed during pre-flight checks. An October 2021 booster test was classified as a "no test" after the Common Hypersonic Glide Body failed to deploy; a June 2022 full-system test also resulted in failure. March and September 2023 launch attempts at Cape Canaveral were halted during pre-flight checks, attributed to mechanical engineering issues with the Lockheed Martin-produced transporter-erector-launcher (TEL).

These setbacks forced the Army to abandon its original fielding target of fiscal year 2023. A successful end-to-end flight test in June 2024, conducted from the Pacific Missile Range Facility in Hawaii and terminating in the Marshall Islands, marked the program's major breakthrough. A second successful test occurred in December 2024 at Cape Canaveral Space Force Station—the first to employ actual battery operations equipment and a TEL in an operational configuration. A third test succeeded on March 26, 2026, also from Cape Canaveral.

Three successful end-to-end tests constitute meaningful progress. Yet the Pentagon's own testing authority has delivered a sobering assessment. The Director of Operational Test and Evaluation (DOT&E) concluded in its 2024 report: "There is not enough data available to assess the operational effectiveness, lethality, suitability, and survivability of the LRHW system." DOT&E projects that sufficient data for comprehensive evaluation will not accumulate until early 2027—nine months or more from the current request date.

This assessment is critical. DOT&E's caution reflects an acknowledged gap in weaponeering data—specifically, uncertainty about the probability of a Dark Eagle missile actually destroying its intended target. As DOT&E noted, this "uncertainty in weaponeering tools could result in excessive employment requirements or failure to meet warfighter objectives." Translated into operational terms: commanders might need to fire multiple $15 million missiles at a single target to achieve the desired probability of destruction, or risk mission failure with inadequate targeting data.

Key Technical Characteristics of Dark Eagle (LRHW)

• Range: 1,725 miles (2,775 km) unclassified; potential 3,500+ km classified
• Velocity: Mach 5+ (hypersonic glide body phase)
• Configuration: Two-stage booster + Common Hypersonic Glide Body (C-HGB)
• Prime Contractors: Lockheed Martin (booster, assembly, launcher), Northrop Grumman (missile component), Dynetics/Leidos (glide body)
• Battery Composition: 8 missiles, 4 transporter-erector-launchers, Battery Operations Center, support vehicle
• Per-Missile Cost: ~$15 million
• Battery System Cost: ~$2.7 billion
• Current Available Inventory: Fewer than 8 missiles
• Status: Initial Operational Capability (claimed); not formally declared combat-ready
• First Designated Operational Unit: Bravo Battery, 1st Battalion, 17th Field Artillery Regiment, 3rd Multi-Domain Task Force, Joint Base Lewis-McChord

Munitions Stockpile Depletion: The Second Driver of the Request

Beyond the tactical gap created by Iranian launcher relocation, a second driver of the Dark Eagle request is the rapid depletion of PrSM stockpiles during Operation Epic Fury. The Center for Strategic and International Studies (CSIS) estimates that in the first seven weeks of operations, the U.S. expended at least 45 percent of its Precision Strike Missile inventory. A U.S. Army Fires Center official stated in mid-April that "our entire inventory" of PrSMs had been shot at the beginning of the Iran war, though Army leadership later clarified that some inventory remained but resupply was active.

This ambiguity itself is revealing. Whether depleted entirely or merely substantially, PrSM stocks are clearly constrained. The missile is in early production; prior to fiscal year 2024, the Army had procured only 130 PrSMs, a fraction of eventual force needs. Lockheed Martin has announced a framework agreement to quadruple production capacity, but rebuilding depleted inventories is a multi-year enterprise.

In this context, an underdeveloped system representing "scaled hypersonics" designated as a critical technology area by the Pentagon's Chief Technology Officer becomes attractive to advocacy within CENTCOM and industry—not necessarily as the optimal solution, but as the solution that appears available when existing systems are scarce.

Cost and Production Constraints

Each Dark Eagle missile carries an estimated unit cost of approximately $15 million—higher in real terms than a Trident II D5 submarine-launched ballistic missile ($31 million historical cost), but in the same ballistic missile cost category. These figures exclude integration, launcher, command and control, and sustainment costs; the full battery system cost totals approximately $2.7 billion.

For a system being deployed in an active theater with fewer than eight missiles available, the cost-exchange ratio becomes problematic. If a single Iranian target requires two or three Dark Eagle shots to achieve destruction (realistic given acknowledged lethality uncertainties), the system rapidly becomes a one-mission-per-target proposition. For comparison, the PrSM costs significantly less per round ($3.5 million versus $15 million); even with higher ammunition consumption rates, maintaining magazine depth across multiple targets becomes more feasible with conventional systems.

Production constraints reinforce this limitation. The program is hampered by manufacturing complexity, quality control issues affecting the launcher system (historically the program's most persistent problem), and demand for limited test range facilities. A June 2025 Government Accountability Office assessment noted that estimated cost for the first prototype battery rose $150 million in a single year (January 2024 to January 2025), driven by increased missile costs and investigations into earlier failures and the need for re-testing.

Fielding activities for the first operational battery began in December 2025 and are expected to complete in early 2026. The 3rd Multi-Domain Task Force at Joint Base Lewis-McChord has been designated to receive and operate the first operational battery. However, "fielding completion" does not equate to full operational deployment or declarative combat readiness—it means the unit has received hardware and personnel have begun integration and safety validation training.

Strategic Signaling and Great-Power Competition

Beyond the specific operational gap, Dark Eagle deployment carries strategic signal value that the Pentagon is unlikely to minimize in internal debates. Russia deployed hypersonic systems (Kinzhal air-launched, Avangard ICBMs) years ago. China has tested multiple hypersonic platforms and declared deployment of the DF-ZF boost-glide weapon. The U.S., despite early technological leadership in hypersonic aerothermodynamics and propulsion, has lagged in fielding—a gap that has generated Congressional concern and public statements by senior leaders about American competitiveness in advanced weapons categories.

Deploying Dark Eagle—even in limited numbers, even under conditions of incomplete operational testing—would represent the first American hypersonic system in an active theater. For the Pentagon's narrative about technological edge and strategic competitors' capabilities, this has symbolic weight. For Congressional audiences concerned about hypersonic "lag," it signals American movement. For industry seeking production rate increases and budgetary justification for scaling, it provides the case study of first operational use.

These are not trivial considerations in the defense policy ecosystem. They do not, however, address the central technical question: Is Dark Eagle ready for combat employment?

Operational Risk Assessment

Several overlapping risks attend a decision to deploy Dark Eagle:

Technical Readiness: The system has achieved three successful end-to-end tests. This is meaningful but represents a small data population. Hypersonic flight imposes extreme thermal and structural stresses; long-term reliability of shielded electronics, thermal protection, and guidance systems remains incompletely characterized. The program's 2021-2023 history of launcher failures and booster issues suggests production and integration quality remains a concern.

Weaponeering Uncertainty: DOT&E's explicit acknowledgment that lethality and effectiveness cannot be fully assessed until 2027 means that employment plans will rest on incomplete data. If commanded to strike hardened or dispersed targets, Dark Eagle operators will lack validated probability-of-kill estimates—a gap that may force either conservative targeting assumptions or unjustified risk of mission failure.

Limited Inventory and Magazine Depth: Fewer than eight missiles per battery means one battery represents a single-engagement capability against multiple target sets. If Iran possesses decoy or dummy launchers, some proportion of Dark Eagle inventory would be consumed in attempts to locate and destroy actual launch platforms. Resupply from production is months to years away.

Escalation and Ceasefire Dynamics: A ceasefire, however fragile, has been in place between the U.S. and Iran since April 9, 2026. Deployment of a new, more capable strike system—particularly one characterized as experimental—sends a dual signal: reinforced deterrence, but also visible preparation for resumed offensive operations. In the context of failed diplomatic negotiations (April 12 talks in Islamabad collapsed without agreement), deployment could be perceived as preparation for resumed strikes rather than stabilization. Whether that perception is accurate or not, it shapes Iranian decision-making and may reduce incentives for further negotiation.

The Alternative Path Not Taken: Accelerated PrSM Increment 2

An alternative decision path existed and arguably should have been pursued: aggressive acceleration of PrSM Increment 2 development and production ahead of Dark Eagle deployment. The Navy's Conventional Prompt Strike system, sharing the same Common Hypersonic Glide Body as Dark Eagle, completed a successful test in December 2024. PrSM Increment 2 with extended range (targeting 1,000 km) has been in development since 2020.

If the Pentagon had prioritized this acceleration beginning in 2018-2019 when Congressional authorization first became available—or at minimum, by 2019 when the INF Treaty terminated—extended-range conventional ballistic missiles could be operational by 2024-2025. Such a system would:

• Provide intermediate-range coverage without the testing uncertainties of hypersonic systems
• Use proven booster technology (Lockheed Martin two-stage design shared with Dark Eagle)
• Integrate seamlessly with existing HIMARS and MLRS launchers
• Build on the operational experience of PrSM Increment 1, now combat-proven in Iran
• Cost significantly less per round than Dark Eagle ($3.5 million vs. $15 million)
• Preserve larger magazine depth for distributed, mobile strike operations

The fact that PrSM Increment 2 acceleration only happened recently (May 2025, after the Iran war had largely expended Increment 1 stocks) demonstrates that institutional prioritization was misaligned. The Pentagon was pursuing hypersonic exotica while allowing the conventional next-generation system to lag.

The Case for Caution

Defenders of the Dark Eagle deployment request point to a genuine operational gap: existing systems cannot reach relocated Iranian targets. This is factually correct. They note that allies (Russia, China) have fielded hypersonic systems; American technological leadership is legitimately at stake. They observe that the program has now achieved three successful tests and has reached initial operational capability by Pentagon standards.

Yet each of these arguments has a counterargument that merits serious consideration:

The operational gap could have been addressed through alternative means—longer-range derivatives of existing systems, which should have been in development since 2018. Extended-range cruise missiles and conventional ballistic missiles could have provided extended-range strike capability without the developmental immaturity of Dark Eagle. These alternatives would employ systems with greater data on operational effectiveness and higher inventory levels.

The great-power competition argument is sound, but fielding an incomplete system in combat conditions is a high-stakes way to close a perception gap. If Dark Eagle operations result in unexpectedly high failure rates, incomplete target destruction, or collateral damage due to weapons handling or targeting errors, the strategic credibility message could reverse. American hypersonic capability would be perceived as immature rather than innovative.

Three successful end-to-end tests, while important, do not resolve DOT&E's assessment that effectiveness cannot be validated until 2027. The contrast between claims of "initial operational capability" and the testing authority's explicit statement that sufficient data is not yet available creates a credibility tension within the Pentagon bureaucracy itself.

More fundamentally, the precedent of deploying an underdeveloped system to combat may establish an unwanted institutional pattern. If Dark Eagle goes to the Middle East before full operational testing concludes, and if that deployment is perceived as driven by organizational momentum (hypersonic priority) and inadequate planning (failure to develop conventional alternatives), future pressure to field other incomplete systems under time pressure will be harder to resist.

Conclusion: A Preventable Crisis

As of April 30, 2026, no final decision has been announced. The Trump administration will ultimately decide whether to approve CENTCOM's request. The U.S. Strategic Command, which maintains employment authority over long-range conventional strike systems, will have a formal voice in the deliberation. The Pentagon's testing and evaluation staff will likely submit formal reservations.

What seems unlikely, barring sharp reversal in diplomatic status or Iranian escalation that changes the tactical calculus, is outright rejection. The operational gap is real, the political appetite for hypersonic fielding is genuine, and a formal CENTCOM request carries bureaucratic momentum.

Yet the deeper issue is this: the current operational gap was largely preventable. The Pentagon had legal opportunity (R&D exemption under the INF Treaty), Congressional authorization (FY2018 NDAA and subsequent acts), budgetary authority, and seven years between treaty withdrawal and the current request to develop operational extended-range conventional systems. It failed to prioritize this development, instead allowing institutional momentum to carry hypersonic programs forward while conventional system development lagged.

Dark Eagle deployment may be the tactical response to an immediate problem. But it is also a symptom of an institutional failure in strategic planning—one that cost the Pentagon flexibility, options, and the opportunity to address the Iranian launcher relocation with mature, cost-effective conventional systems rather than immature, expensive hypersonic experimental weapons.

The choice now facing the Pentagon is not whether to close the operational gap (some response is necessary). The choice is whether to do so with systems that should have been ready by now, or whether to accept the institutional consequences of under-resourced planning and deploy an underdeveloped system to compensate for institutional misjudgment.

---

Verified Sources & Formal Citations

[1]

U.S. Central Command Requests Deployment of 'Dark Eagle' Hypersonic Missiles to Middle East

Published: April 30, 2026

Defense News

https://www.thedefensenews.com/news-details/US-Central-Command-Requests-Deployment-of-Dark-Eagle-Hypersonic-Missiles-to-Middle-East/

Summary: Official announcement of CENTCOM's formal request for Dark Eagle deployment to target Iranian ballistic missile launchers beyond PrSM range. Includes operational context and system specifications.

[2]

US Seeks to Deploy Hypersonic Missile For the First Time Against Iran

Published: April 29, 2026

Bloomberg News

https://www.bloomberg.com/news/articles/2026-04-29/us-seeks-to-deploy-hypersonic-for-the-first-time-against-iran

Summary: Original reporting on CENTCOM's Request for Forces submission. Notes that Dark Eagle has not been declared fully operational and is running far behind schedule compared to Russian and Chinese hypersonic deployments.

[3]

The US wants to use a new missile on Iran. It might not even work.

Published: April 30, 2026

Responsible Statecraft (Center for Strategic and International Studies)

https://responsiblestatecraft.org/us-hypersonic-missile/

Summary: Critical analysis of deployment timing and readiness status. Emphasizes DOT&E assessment that insufficient data exists for combat effectiveness evaluation until early 2027. Includes Kelly Grieco (Stimson Center) expert commentary on budget-driven acquisition incentives.

[4]

Dark Eagle Takes Flight: Guide to America's Landmark Hypersonic Weapon

Published: August 26, 2025

The Defense Post

https://thedefensepost.com/2025/08/26/dark-eagle-hypersonic-weapon-guide/

Summary: Comprehensive technical and programmatic history of Dark Eagle development. Details 2021-2023 testing failures, December 2024 breakthrough test, cost overruns, and DOT&E verdict on insufficient effectiveness data. Essential source on development trajectory.

[5]

Dark Eagle's Road to Operational Readiness: A Testing History

Published: April 2026 (updated)

K4i Defense Technology

https://k4i.com/2026/04/08/dark-eagles-road-to-operational-readiness-a-testing-history/

Summary: Detailed chronology of Dark Eagle testing from October 2021 through March 26, 2026 successful test. Categorizes test events and explains distinction between full-system tests and operational configuration tests.

[6]

U.S. Army to deploy first operational Dark Eagle hypersonic missile with 3,500 km range in coming weeks

Published: March 20, 2026

Army Recognition Group

https://www.armyrecognition.com/news/army-news/2026/us-army-to-deploy-first-operational-dark-eagle-hypersonic-missile-with-3-500-km-range-in-coming-weeks

Summary: Interviews with Lt. Gen. Frank Lozano on fielding timelines. Details cost overruns ($150M increase in single year), production constraints, and fielding activities schedule.

[7]

U.S. Considers Deploying Dark Eagle Hypersonic Missile To Strike Iranian Ballistic Launchers

Published: April 30, 2026

Army Recognition Group / Defense Analyst Erwan Halna du Fretay

https://www.armyrecognition.com/news/army-news/2026/u-s-considers-deploying-dark-eagle-hypersonic-missile-to-strike-iranian-ballistic-launchers

Summary: Operational and strategic analysis of Dark Eagle deployment request. Discusses Anti-Access/Area Denial implications, dual signal of deterrence vs. resumption preparation, and impact on ceasefire dynamics.

[8]

Report to Congress on U.S. Army's Dark Eagle Hypersonic Weapon

Published: April 7, 2026

Congressional Research Service / U.S. Navy Institute News

https://news.usni.org/2026/04/09/report-to-congress-on-u-s-armys-dark-eagle-hypersonic-weapon

Summary: Formal CRS In Focus report on Dark Eagle (LRHW). Authoritative on program structure, contractor roles, system specifications, employment authority (USSTRATCOM), and Congressional oversight implications.

[9]

The U.S. Army's Long-Range Hypersonic Weapon (LRHW): Dark Eagle

Published: April 7, 2026 (updated April 30)

Library of Congress, Congressional Research Service

https://www.congress.gov/crs-product/IF11991

Summary: Authoritative Congressional reference material on Dark Eagle. Includes battery composition specifications, designated operator unit (Bravo Battery, 1st Battalion, 17th FAR, 3rd MDTF), cost estimates, and historical timeline of test events.

[10]

Magazine depth: Rapid depletion of missile stockpiles in Iran raises concerns about US readiness

Published: March 27, 2026

Small Wars Journal / Payne Institute for International Security

https://smallwarsjournal.com/2026/03/27/magazine-depth-iran-missiles-stockpile-readiness/

Summary: CSIS-Payne Institute analysis of weapon depletion during Operation Epic Fury. Documents PrSM consumption rates, THAAD/Patriot losses, and timeline for inventory reconstitution. Includes expert commentary from Mark Cancian on strategic competition implications.

[11]

U.S. Precision Missile Stockpiles Nearly Halved in Iran War, Creating 'Near-Term Risk'

Published: April 2026

Kyiv Post, citing CSIS analysis and Pentagon sources

https://www.kyivpost.com/post/74474

Summary: Assessment that 45% of PrSM inventory expended in first seven weeks of Operation Epic Fury. Includes classified Pentagon data comparisons and timeline for stockpile rebuilding (4-5 years minimum).

[12]

PRSM Stockpile Remains Despite Iran Usage, U.S. Army Says

Published: April 12, 2026

Aviation Week Network

https://aviationweek.com/defense/missile-defense-weapons/prsm-stockpile-remains-despite-iran-usage-us-army-says

Summary: Army correction of Fires Center official statement on PrSM depletion. Acknowledges significant consumption while clarifying some inventory remains. Details procurement history (130 PrSMs pre-FY2024) and production acceleration plans.

[13]

Army expects to complete fielding of Dark Eagle hypersonic missile in 'early 2026'

Published: January 21, 2026

DefenseScoop

https://defensescoop.com/2026/01/21/dark-eagle-hypersonic-missile-army-fielding-plans/

Summary: Army statement on fielding timeline and activities. Specifies that "fielding activities include the required integration, safety, and readiness steps." Distinguishes between fielding initiation and deployment readiness.

[14]

Precision Strike Missile - Wikipedia

Updated: April 30, 2026

https://en.wikipedia.org/wiki/Precision_Strike_Missile

Summary: Technical documentation of PrSM development under INF Treaty constraints. Documents original 500 km range specification and post-treaty extended-range variants in development.

[15]

The Intermediate-Range Nuclear Forces (INF) Treaty at a Glance

Updated: 2024-2025

Arms Control Association

https://www.armscontrol.org/factsheets/intermediate-range-nuclear-forces-inf-treaty-glance

Summary: Authoritative overview of treaty scope (nuclear AND conventional warheads). Documents Congressional authorization of "treaty-compliant research and development" in FY2018-2019 NDAAs on conventional systems.

[16]

Intermediate-Range Nuclear Forces Treaty

Accessed: 2026

Nuclear Threat Initiative (NTI)

https://www.nti.org/education-center/treaties-and-regimes/treaty-between-the-united-states-of-america-and-the-union-of-soviet-socialist-republics-on-the-elimination-of-their-intermediate-range-and-shorter-range-missiles/

Summary: Full treaty text and technical clarifications. Documents the 1988 clarification covering missiles "irrespective of whether they were equipped with nuclear, conventional, or 'exotic' warheads." Explains R&D exemption and production/flight-testing bans.

[17]

After the INF Treaty, What Is Next?

Published: January 2019

Arms Control Association

https://www.armscontrol.org/act/2019-01/news/after-inf-treaty-what-next

Summary: Documents Congressional action (FY2018 NDAA) authorizing Pentagon R&D on conventional systems. Notes Pentagon was to develop "concepts and options" for conventional systems with 500-5,500 km range.

[18]

U.S. Withdrawal from the INF Treaty: What's Next?

Published: 2019

Congressional Research Service

https://www.congress.gov/crs_external_products/IF/PDF/IF11051/IF11051.7.pdf

Summary: Detailed legislative history. FY2018 NDAA (P.L. 115-91, §1243) authorized DOD "program of record" to develop new ground-launched cruise missile. FY2015 and FY2016 NDAAs called for study and planning of military options.

Note on Sources: All sources cited represent reporting published between April 7–30, 2026, plus historical treaty documentation. The analysis integrates official Pentagon statements, Congressional Research Service reports, CSIS defense analysis, expert commentary from established defense policy institutions, and wire service reporting from Bloomberg, Reuters, and Aviation Week. No classified information is incorporated; all material is from unclassified public sources or authorized official statements.

 

Beneath the Plaster: Ancient DNA Rewrites the Last Hours of Pompeii

Scientists Were WRONG About Pompeii | Here's What The DNA Shows

Genome-wide sequencing of skeletal fragments embedded in the famous 19th-century body casts overturns long-held assumptions about who Vesuvius killed — and reveals an Imperial Roman city far more cosmopolitan than the family portraits we have imagined for 150 years.

BOTTOM LINE UP FRONT — 

In November 2024, an international team led by the University of Florence, Harvard Medical School, and the Max Planck Institute for Evolutionary Anthropology reported in Current Biology the first genome-wide ancient DNA recovered from skeletal fragments embedded in Pompeii's plaster casts [1, 14]. Of 14 casts sampled during ongoing restoration of 86 specimens, five yielded sufficient nuclear DNA for genome-wide analysis. The genetic results contradict three iconic interpretations: the "mother and child" of the House of the Golden Bracelet was an unrelated adult male holding an unrelated child; the "embracing sisters" of the House of the Cryptoporticus included at least one male and were not maternally related; and four victims long presented as a nuclear family at the Golden Bracelet shared no first-, second-, or third-degree biological kinship. All five sequenced individuals derive most of their ancestry from the eastern Mediterranean — chiefly Anatolian and Levantine Neolithic farming populations — consistent with parallel results from Imperial Rome and confirming the cosmopolitan, mobile character of the Roman Empire in the first century CE. The findings do not erase a tragedy; they correct a Victorian-era story that researchers themselves now describe as "modern assumptions about gendered behaviors" projected onto the dead.

A morning in autumn, 79 CE

The traditional date for the eruption of Mount Vesuvius — August 24, 79 CE — comes from a single source: a letter written by Pliny the Younger to the historian Tacitus roughly a quarter century after the event. That date has been steadily eroded by physical evidence. Autumn fruits, heavier clothing on victims, a coin in the House of the Golden Bracelet whose mint date may post-date August, and most strikingly a charcoal graffito found in 2018 in Regio V dated XVI K(alendas) Nov(embris) — October 17 — together point to a late-October eruption, most often given as October 24–25, 79 CE [1, 2]. The August date persists in popular accounts (and in the YouTube transcript that prompted this article) because the surviving medieval manuscripts of Pliny preserve it, and because a 2022 reassessment by Pedar Foss of the manuscript tradition has reopened, rather than closed, the debate [13]. The Pompeii Archaeological Park itself has oscillated. What is no longer in dispute is that the city died in a single day's worth of sequential pyroclastic events.

The killing mechanism has also been revised. For more than a century, ash suffocation was the standard textbook cause of death. Multidisciplinary work by Giuseppe Mastrolorenzo and colleagues at Italy's National Institute of Geophysics and Volcanology, beginning with a 2010 PLOS One paper, demonstrated that the pyroclastic density currents (PDCs) that reached Pompeii — roughly 10 km from the vent — carried temperatures sufficient to cause instantaneous thermal death even inside buildings [3]. Pompeii's surges struck with temperatures estimated between roughly 250 °C and 300 °C; closer in, at Herculaneum and Oplontis, peripheral surge temperatures reached 500–600 °C. The contorted, "pugilistic" postures preserved in the casts are now interpreted as cadaveric heat spasm, not protracted agony.

That thermal picture was sharpened again in February 2025, when Guido Giordano of Roma Tre University and colleagues published in Scientific Reports the calorimetric analysis of vitrified organic matter recovered from inside the skull and spinal column of a young man found in the Collegium Augustalium at Herculaneum [4]. Differential scanning calorimetry indicated his brain tissue had been heated above 510 °C and then cooled rapidly enough to bypass crystallization — the first reported instance of natural high-temperature vitrification of soft animal tissue. The team attributes the event to a brief, dilute, very hot ash cloud that preceded the main pyroclastic flow. (Skepticism remains: Alexandra Morton-Hayward of Oxford has questioned both the identification and the thermal scenario.) For Pompeii's lower-altitude victims, however, the killing was less exotic: hot enough, fast enough, fatal in seconds.

Fiorelli's invention — and its limits

The plaster casts themselves are an artifact of 19th-century method, not of antiquity. Excavations of Pompeii began in 1748 under the Bourbon kings of Naples but proceeded haphazardly until Giuseppe Fiorelli took charge in 1863. Fiorelli realized that the cavities in the hardened ash were the negative impressions of bodies whose soft tissue had decomposed, and he devised the technique of pouring liquid plaster into those voids through small bore-holes, then chipping away the surrounding matrix. Roughly 104 casts were eventually produced from the estimated 1,000-plus victims recovered at the site.

What Fiorelli's technique did not do was preserve a complete osteological record. When the Pompeii Archaeological Park began a systematic restoration of 86 casts in 2015 and subjected 26 of them to CT scanning or X-ray imaging, the results were sobering. None contained a complete skeleton. Many had been "creatively restored" in the past — bones removed, metal armatures inserted, postures adjusted. The Pilli et al. paper notes dryly that the casts have served as "vehicles for storytelling" and that "stylistic variations between casts in part reflect aesthetic preferences of the periods in which they were made" [5]. The most famous example: a "pregnant woman" whose distended abdomen turned out, on imaging, to be bunched-up garments.

This means the genetic study did not have to overturn a settled scientific record so much as a popular and museological one. The narratives the new DNA contradicts were largely constructed, restored, and curated; they were not derived from rigorous bioarchaeological assessment.

What the sequencers actually did

The methodology, described in the Current Biology paper and its STAR Methods supplement, is forensic in its caution [5]. Sampling occurred at the Pompeii Archaeological Park during cast restoration, accessing fragmented bone and teeth through pre-existing damage in the casts rather than breaching them. Samples were processed at the Molecular Anthropology Unit of the University of Florence — a dedicated ancient-DNA clean facility — with outer surfaces mechanically abraded and ultraviolet-irradiated to suppress modern contamination.

DNA extracts of the first set of six samples were quantified using the Quantifiler Trio kit. Illumina sequencing libraries were prepared in two formats: non-UDG-treated (preserving the deamination damage patterns that authenticate ancient DNA) and partial-UDG-treated (cleaner, suitable for capture). At Harvard Medical School, libraries were enriched in solution for the mitochondrial genome plus roughly 3,000 nuclear screening SNPs, then for those that passed, for the standard 1,237,207-SNP "1240K" capture panel. Sequencing ran on Illumina MiSeq and NextSeq 500 instruments. Of 14 sampled casts, seven yielded enough DNA to attempt 1240K capture; five produced data covered on more than 50,000 SNPs and were retained for population genetic analysis [5].

For one individual — Cast 25 from the Villa of the Mysteries, the best-preserved cast in the set — a lower premolar was also processed at the University of Florida for strontium and oxygen isotope ratios via thermal ionization and isotope-ratio mass spectrometry, providing a complementary signal of childhood residency [5].

Three corrected stories

The House of the Golden Bracelet. Excavated in 1974, this terraced villa in Insula 17 of Regio VI yielded four victims long presented as a nuclear family fleeing toward the seafront. Cast 52 — the adult on whom a 6.1-gram gold bracelet was found, giving the house its name — was traditionally identified as a mother because of the bracelet and because a young child (Cast 51) appeared to be on the adult's hip. Cast 50, an adjacent adult, was cast as the father; Cast 53, a four-year-old child found nearby, as a son. DNA quantification using the Quantifiler Trio kit's Y-target showed all four were biologically male. Where nuclear coverage was sufficient (Casts 51, 52, 53), the result is unambiguous: XY karyotypes. Crucially, BREADR and KIN relatedness analyses found no biological kinship up to the third degree among any of the four. They were not a family. Mitochondrial haplogroups (U1a1 for Cast 52; T2c1c for Cast 51; H for Cast 53) further rule out maternal lineage [5]. The bracelet, in this revised reading, simply reflects what historians of Roman material culture have long noted: high-status Roman men wore gold.

The House of the Cryptoporticus. Excavated in 1914, this house in Insula 6 of Regio I produced a pair of victims — Casts 21 and 22 — found in what archaeologists described as an embrace. The narrative of "two sisters," "mother and daughter," or "lovers" entered the popular literature without any osteological sex determination. CT analysis estimated Cast 21 at 14–19 years old and Cast 22 as a young adult, but produced no reliable sex attribution. Genetic analysis succeeded for Cast 22, identifying him as male (Y-haplogroup J2b2a1, mtDNA N1b1a1). Cast 21 yielded only mitochondrial data, but its haplogroup R is incompatible with N1b1a1, ruling out a mother–daughter relationship [5]. The intimacy of the pose, in other words, is a fact of physical proximity in the moment of death, not of biological or necessarily social relationship.

The Villa of the Mysteries. Cast 25, found alone on a layer of ash on the upper floor of the farm wing with an iron ring, five bronze coins, and a whip, has been interpreted since excavation as the villa's faithful steward. Genetics confirmed male sex (Y-haplogroup E1b1b1b1b, mtDNA H). Strontium analysis returned 87Sr/86Sr = 0.7084729 ± 0.00001, compatible with the southern Campanian plain (0.7075–0.7085); δ¹⁸O of 26.77‰ VSMOW is consistent with coastal central Italy [5]. The isotopes do not exclude a Pompeian childhood, but neither do they require it; similar geochemical signatures recur across the Mediterranean. His genome-wide ancestry suggests a mixed Eastern Mediterranean and European origin, distinct from the other four sequenced individuals.

"At two of the villas we analyzed, individuals previously assumed to be women, in absence of careful osteological assessment, were found to be genetically male... These discoveries challenge longstanding interpretations, such as associating jewelry with femininity or interpreting physical closeness as indicators of biological relationships." — Pilli et al., Current Biology, 2024 [1, 12]

A cosmopolitan port

The ancestry results align with a picture that has been emerging from ancient-genomics work on Imperial Rome over the past five years. On principal component analysis projected against modern West Eurasian and worldwide reference panels, the five Pompeian genomes plot away from modern Italians, Iron Age Italians, and contemporaneous Etruscans, and cluster instead with eastern Mediterranean and Levantine populations. ADMIXTURE analysis at k=6 places them close to Imperial Roman individuals from central Italy and to contemporaneous individuals from the Aegean and Anatolia [5].

Formal qpAdm modeling using distal source populations attributes 48–75% of ancestry in each individual to Anatolian and/or Levantine Neolithic farmers, with most of the remainder from Iranian/Zagros Neolithic farmers. Cast 52 is an outlier: he is best modeled as roughly 58% Levantine Pre-Pottery Neolithic and 42% Iranian Neolithic, with no Anatolian Neolithic contribution — a profile most parsimoniously explained by recent Levantine ancestry, possibly Hellenistic Egyptian. Phenotype prediction using HIrisPlex-S indicates Cast 52 likely had black hair and dark skin; Casts 25, 51, and 53 likely had brown eyes [5]. The single individual (Cast 52) with sufficient genome coverage to evaluate runs of homozygosity (ROH) showed only one short ROH — inconsistent with consanguinity or origin in a small founding population, and consistent with a large, mixed urban gene pool.

This matches what historians have long inferred from inscriptions, trade goods, and the writings of authors such as Strabo and Tacitus: that Pompeii, a port at the mouth of the Sarno river, was a node in an empire whose population was constantly redistributed by commerce, military service, and the Roman institution of slavery. The previously published whole genome from a victim recovered in the Casa del Fabbro [6] showed the same eastward-shifted ancestry, as did Antonio et al.'s landmark 2019 Science paper on the genomic history of Imperial Rome [7].

Pompeii is still being uncovered

The DNA paper landed in the middle of an unusually productive period for Pompeii's archaeologists, working under park director Gabriel Zuchtriegel — himself a co-author of the genetic study and the official authority who must approve sampling. A non-exhaustive list of recent finds:

• January 2025: Excavation of an unusually large private bathhouse complex in Regio IX, capable of accommodating around 30 people across calidarium, tepidarium, frigidarium, and a cold plunge pool [8].
• February 2025: Discovery of a near-life-size Dionysian frieze on the walls of a banquet room, depicting a Bacchic mystery cult procession.
• April–May 2025: The "House of Helle and Phrixus" yielded the remains of four victims, including a child, who had barricaded a bedroom door with a bed frame against the inrushing lapilli [9].
• August 2025: Excavations in the Insula Meridionalis, published in the E-Journal of the Excavations of Pompeii, documented sustained reoccupation of the city's upper floors and cellars from the late first through fifth centuries CE — including a ceramic lamp bearing an early Christian symbol — overturning the long-held assumption that the site was simply abandoned after 79 CE [10, 11]. This finding has a forensic implication for the genetic and isotopic work: not every organic trace recovered above the destruction layer necessarily belongs to a 79 CE victim.
• December 2025: Reconstruction work at the Casa del Tiaso (House of the Thiasos) and CNN reporting indicated evidence of a multi-story tower in a luxury residence — architecturally unprecedented for Pompeii [15]. New finds at the Villa Poppaea at Oplontis, traditionally associated with Nero's wife Poppaea Sabina, included a peahen fresco, an Atellan-comedy theatrical mask of Pappus, and four previously unknown rooms [16].
• April 2026: The Pompeii park, in collaboration with the University of Padua, released an AI-assisted facial reconstruction of a victim from the Porta Stabia necropolis who had attempted to shield his head from falling lapilli with a terracotta mortar [17].

None of these finds individually overturns the genetic results, but together they reinforce the methodological argument the Pilli et al. team made implicitly: any single interpretive lens — archaeological, osteological, genetic, isotopic — gives a partial view. The casts read as a tableau of Roman family life; the genomes read as a port city of strangers; the new excavations read as an "invisible" post-eruption favela. All three are true at once.

The instrument behind the result: Illumina sequencing in ancient DNA

The Pompeii study is one application of a now-standard toolkit — instruments, chemistries, library protocols, capture reagents, bioinformatic pipelines, and curated databases — that has reshaped the study of the human past since roughly 2010. None of the science in the Current Biology paper is possible without that infrastructure, and a few sentences of background help explain both why the result took so long to obtain and why it is trustworthy.

Sequencing chemistry. Illumina's platforms all use sequencing-by-synthesis (SBS) with reversible-terminator chemistry, originally developed at Solexa and acquired by Illumina in 2007. DNA fragments are immobilized on a flow cell, amplified into clonal clusters by bridge PCR, and then sequenced by sequential incorporation of fluorescently labeled, 3′-blocked nucleotides; after each cycle the fluorescent tag and the blocking group are cleaved and the next base added [18]. Because each cluster is read in parallel, a single run yields hundreds of millions to tens of billions of short reads — typically 75–150 bp paired-end. The newer NovaSeq X and NextSeq 1000/2000 platforms run on Illumina's "XLEAP-SBS" chemistry, introduced in 2023, which improves read quality and throughput per run.

Ancient DNA work, however, almost never needs the highest-throughput platform. Endogenous DNA in archaeological bone is usually fragmented to fewer than 100 base pairs, often fewer than 50, and is present in vanishingly small quantities relative to environmental and microbial DNA. The Pilli et al. study used the Illumina MiSeq for the initial mitochondrial-capture screen at Florence and the Illumina NextSeq 500 at Harvard for genome-scale capture data — both v2 chemistry, paired-end 2 × 76 cycles [5]. These are mid-tier benchtop instruments, well matched to the read lengths the input material can support.

Library preparation. Before any sequencing happens, fragmented ancient DNA must be converted into a "library" — a set of molecules with the right sequencing adapters at each end so the flow cell can capture them. Two protocol families dominate aDNA work. The double-stranded protocol of Meyer and Kircher (2010, Cold Spring Harbor Protocols) is what Pompeii's samples received: blunt-end repair, ligation of two adapters in a single reaction, and a fill-in step, with unique dual indexes added by PCR for sample identification [19]. The Pilli team used both fully untreated libraries (which preserve the C-to-T deamination damage at fragment ends that authenticates ancient DNA) and partial-UDG-treated libraries, in which uracil-DNA glycosylase removes most damaged uracils from the interior of reads while leaving terminal damage intact for authentication [5, 20]. The alternative single-stranded protocol developed by Gansauge and Meyer at the Max Planck Institute for Evolutionary Anthropology (2013, refined 2017) uses CircLigase II or T4 DNA ligase to attach adapters strand-by-strand, recovering ultra-short fragments that double-stranded methods miss; it is the workhorse for Neanderthal, Denisovan, and Sima de los Huesos hominin sequencing [21]. Pompeii didn't need it — the bone fragments inside the casts, while degraded, were young enough (ca. 1,950 years) to yield workable double-stranded libraries.

In-solution SNP capture. Direct shotgun sequencing of a Pompeian library would waste roughly 99% of reads on environmental DNA. The standard solution since 2015 is targeted enrichment: synthetic biotinylated RNA or DNA "baits" complementary to a panel of informative human SNPs are mixed with the library, captured on streptavidin beads, and washed clean of off-target sequence. The reference panel that the Reich Lab established and that has been used in roughly 70% of all published aDNA studies to date is the so-called 1240K reagent — 1,237,207 SNPs across the autosomes plus targeted Y-chromosomal and ancestry-informative sites [22]. The Pilli team used two rounds of 1240K capture on partial-UDG libraries, after a smaller pre-screen on roughly 3,000 SNPs plus a mitochondrial bait set originally described by Maricic et al. (2010) [5].

Because synthesizing 1240K baits in-house was prohibitively expensive for most laboratories, in 2021 two companies — Daicel Arbor Biosciences and Twist Bioscience — released commercial assays targeting the same core SNPs. Rohland et al. (2022, Genome Research) benchmarked all three on 27 common libraries and found Twist's panel produced the most uniform coverage, the lowest allelic bias, and the cleanest co-analysis with shotgun data; Harvard has since transitioned to Twist for new captures [22]. The 1240K dataset, however, remains the lingua franca of the field because it is what existing published genomes were genotyped against.

Authenticating that the DNA is actually ancient. Modern human DNA is the universal contaminant in any aDNA lab. Three signals together establish authenticity: (1) the characteristic deamination damage pattern — elevated C-to-T misincorporations at the 5′ end of reads (and G-to-A at the 3′ end for double-stranded libraries), quantified by tools such as mapDamage 2.0 [23] and DamageProfiler; (2) X-chromosomal heterozygosity in putative males, estimated by ANGSD's contamination module — Pilli et al. reported below 4% in the two Pompeii samples with sufficient X-chromosome coverage [5]; and (3) mitochondrial contamination estimates from contamMix or Schmutzi. Reads also carry expected fragment-length distributions (most molecules under 100 bp). Anything with full-length reads and no terminal damage is contamination, and is rejected.

Bioinformatics pipelines. The Florence group used EAGER (Efficient Ancient Genome Reconstruction; Peltzer et al. 2016) for read processing in the mitochondrial-capture phase: AdapterRemoval/Clip&Merge for adapter trimming and paired-end merging, BWA-aln (a short-read-tuned variant of the Burrows-Wheeler aligner) for mapping to the revised Cambridge Reference Sequence (rCRS) using CircularMapper to handle mtDNA's circular topology, and DeDup for paired-end-aware duplicate removal [24]. The current community-standard successor is nf-core/eager, a Nextflow pipeline released in 2021 with Docker/Singularity containers, automated benchmarking, and integration with most major HPC schedulers — designed so that any researcher in any institution can reproduce a Reich Lab- or Max Planck-quality analysis from raw FASTQ to genotype calls [25].

Downstream population-genetic analysis in the Pompeii paper used the Reich Lab's ADMIXTOOLS suite — qpAdm for fitting admixture models, qpWave for source-rank tests, and pre-computed f-statistics via qpfstats; EIGENSOFT/smartpca for principal component analysis; ADMIXTURE for unsupervised clustering at k = 2 through 15; KIN and BREADR for relatedness inference up to the third degree; hapROH for runs-of-homozygosity (which test for parental relatedness or small-population effects); sexDetERRmine for genetic sex determination from X/Y read ratios; and HIrisPlex-S for skin, eye, and hair pigmentation prediction [5]. Haplogrep3 handles mitochondrial haplogroup assignment against the PhyloTree reference; Y-chromosomal haplogroups were assigned against the YFull v8.09 phylogeny.

Reference databases. Two repositories anchor the field. Raw sequencing reads from virtually all published aDNA studies — including the Pompeii data, accession PRJEB74999 — go into the European Nucleotide Archive (ENA) or the U.S. Sequence Read Archive (SRA), where they are publicly accessible to anyone [29]. Curated, uniformly reprocessed genotype calls live in the Allen Ancient DNA Resource (AADR), maintained at Harvard Medical School by Mallick, Micco, Mah, Ringbauer, Lazaridis, Olalde, Patterson, and Reich [26]. The AADR's most recent public release at the time of this writing — version 9.0 / v62.0, dated 16 September 2024 — contains 13,571 ancient individuals plus 4,054 present-day reference samples drawn from the 1000 Genomes Project, the Simons Genome Diversity Project, and the Human Genome Diversity Project, all genotyped at the same core 1.23-million-SNP positions and aligned to the hg19 reference genome [27]. The dataset crossed 10,000 ancient individuals at the end of 2022 and is updated roughly twice a year; an ArcGIS-based AADR Visualizer went online in 2025 [28]. Without this infrastructure, comparing Cast 52 to Hellenistic Egyptians, Iron Age Italians, and Imperial Roman individuals from Latium would not be a one-day analysis — it would be a multi-year project.

What this means for the Pompeii result. The 14 cast samples Pilli et al. drilled were processed through this entire pipeline twice — once at Florence's Molecular Anthropology Unit and once at Harvard Medical School — using independent library preparations and independent capture protocols. The mitochondrial haplogroups recovered from each laboratory matched. The X-chromosomal contamination estimates were below 4%. The damage patterns were as expected for ~2,000-year-old DNA. The five usable genomes were then projected onto the AADR's reference space and modeled with qpAdm against deeply curated source populations. None of this proves the result correct in any philosophical sense, but it does mean that for a popular narrative — "the mother in the Golden Bracelet" — to survive contact with this evidence, every one of these independent checks would have to fail in the same direction. They didn't.

What the data do not say

It is worth being clear about the limits of the genetic evidence, because public summaries (including the YouTube transcript that prompted this article) tend to overshoot. The study analyzed five individuals — not the population of Pompeii. The ancestry signal is robust and aligns with parallel work on Imperial Rome, but the headline figure sometimes given as "70% eastern Mediterranean ancestry" is a description of these specific genomes, not an estimate of the city's population structure. Cast 50 yielded only mitochondrial data, so a paternal-line relationship to the other Golden Bracelet individuals cannot be formally excluded. Phenotypic predictions for skin, eye, and hair color were possible only because the HIrisPlex-S panel is small and well-calibrated; predictions of disease susceptibility from the same low-coverage data were not reliable. And the absence of biological kinship does not preclude social, household, or affective relationships among the dead. The genome is silent on whether the man holding the child loved him.

What the study does establish, with the rigor characteristic of David Reich's group and the Italian aDNA consortia, is that the popular narratives attached to these casts since the 19th century cannot be defended as factual claims. They were inferences from posture, ornament, and Victorian sentiment. They are now testable — and several have failed the test.

A note on dates and details. Some popular accounts of this story (including the YouTube transcript that prompted this article) state that the eruption began on August 25, 79 CE, that the casts were initially called "the Lady of Vesuvius," and that the first cast was made in 1863. The August date is the traditional one but is increasingly displaced by an October date based on the 2018 charcoal graffito and supporting evidence; Fiorelli's first cast is conventionally dated to 1863, but his systematic excavation began in 1860 and the casting technique was refined over several years. "Lady of Vesuvius" is not standard terminology in the peer-reviewed literature for Fiorelli's earliest casts. Temperature figures of "500 °C at Pompeii" should be read with care: the 500–600 °C estimates apply to Herculaneum and Oplontis, not to Pompeii, where surge temperatures were closer to 250–300 °C.

Sources

1. Pilli, E., Vai, S., Moses, V. C., et al. "Ancient DNA challenges prevailing interpretations of the Pompeii plaster casts." Current Biology 34(22): 5307–5318.e7 (November 18, 2024). DOI: 10.1016/j.cub.2024.10.007. Open-access manuscript at PubMed Central.
   https://www.cell.com/current-biology/fulltext/S0960-9822(24)01361-7 · https://pmc.ncbi.nlm.nih.gov/articles/PMC11627482/
2. Osanna, M., et al. Statement on charcoal inscription dated XVI K. Nov. (October 17, 79 CE) found in Regio V, Pompeii, October 16, 2018. Reported in Daley, J., "Ancient graffiti shifts date of Pompeii's destruction by 2 months," Science, October 17, 2018.
   https://www.science.org/content/article/ancient-graffiti-shifts-date-pompeii-s-destruction-back-2-months · https://phys.org/news/2018-10-pompeii-evidence-rewrites-vesuvius-eruption.html
3. Mastrolorenzo, G., Petrone, P., Pappalardo, L., and Guarino, F. M. "Lethal Thermal Impact at Periphery of Pyroclastic Surges: Evidences at Pompeii." PLOS ONE 5(6): e11127 (June 2010). DOI: 10.1371/journal.pone.0011127.
   https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0011127
4. Giordano, G., Pensa, A., Vona, A., et al. "Unique formation of organic glass from a human brain in the Vesuvius eruption of 79 CE." Scientific Reports 15: 4567 (February 27, 2025). DOI: 10.1038/s41598-025-88894-5. See also Petrone, P., et al., "Heat-Induced Brain Vitrification from the Vesuvius Eruption in c.e. 79," NEJM 382: 383–384 (2020), DOI: 10.1056/NEJMc1909867.
   https://www.nature.com/articles/s41598-025-88894-5 · https://www.nejm.org/doi/full/10.1056/NEJMc1909867
5. Pilli et al. 2024 (full STAR Methods, supplementary tables, and dataset descriptions). Same DOI as [1]. All quantitative claims about cast individuals, mtDNA/Y haplogroups, sex determination, qpAdm models, ROH, HIrisPlex-S phenotypes, and strontium/oxygen isotope values are drawn from this source.
6. Scorrano, G., Viva, S., Pinotti, T., et al. "Bioarchaeological and palaeogenomic portrait of two Pompeians that died during the eruption of Vesuvius in 79 AD." Scientific Reports 12: 6468 (May 26, 2022). DOI: 10.1038/s41598-022-10899-1. The first published genome from a Pompeian victim (the Casa del Fabbro individual).
   https://www.nature.com/articles/s41598-022-10899-1
7. Antonio, M. L., Gao, Z., Moots, H. M., et al. "Ancient Rome: A genetic crossroads of Europe and the Mediterranean." Science 366(6466): 708–714 (November 8, 2019). DOI: 10.1126/science.aay6826. The reference work establishing eastern-Mediterranean-shifted ancestry in Imperial Rome.
   https://www.science.org/doi/10.1126/science.aay6826
8. Associated Press / CBS News. "Pompeii excavation reveals large private bathhouse built 2,000 years ago." January 17, 2025.
   https://www.cbsnews.com/news/pompeii-excavation-thermal-complex-discovery/
9. Archaeology Magazine. "New Pompeii Excavations Reveal How One Family Tried to Save Themselves" (House of Helle and Phrixus). May 5, 2025.
   https://archaeology.org/news/2025/05/05/new-pompeii-excavations-reveal-how-one-family-tried-to-save-themselves/
10. Parco Archeologico di Pompei. "Pompei fu rioccupata dopo la distruzione del 79 d.C." Press release and article in the E-Journal degli Scavi di Pompei, August 6, 2025.
    https://pompeiisites.org/
11. CBS News / CNN. Coverage of the Insula Meridionalis reoccupation finding, August 6–14, 2025.
    https://www.cbsnews.com/news/pompeii-vesuvius-eruption-survivors-reoccupation-precarious-conditions/ · https://www.cnn.com/2025/08/14/science/pompeii-reoccupation-after-eruption
12. Krause, J. (commentary). "Archaeogenetics: Four letters from Pompeii." Current Biology 34(22): R1107 (November 18, 2024). DOI: 10.1016/j.cub.2024.10.009. Companion dispatch to Pilli et al.
    https://www.sciencedirect.com/science/article/pii/S0960982224013630
13. Foss, P. W. Pliny and the Eruption of Vesuvius. Routledge, 2022. Reassessment of the manuscript tradition for Pliny the Younger's letters and the eruption date. ISBN 978-1-032-00131-7.
14. Max Planck Institute for Evolutionary Anthropology / Cell Press. "DNA evidence rewrites histories for people buried in volcanic eruption in ancient Pompeii." Press release, EurekAlert!, November 7, 2024.
    https://www.eurekalert.org/news-releases/1063333
15. Strickland, A. (CNN). "An ancient stone staircase seemed to lead nowhere. It's revealing the 'lost Pompeii.'" December 7, 2025. Coverage of the Casa del Tiaso tower reconstruction.
    https://www.cnn.com/2025/12/07/science/pompeii-tower-digital-archaeology
16. GreekReporter. "Pompeii Excavation Reveals Lavish New Finds in Villa Linked to Nero's Wife." December 20, 2025. Villa Poppaea / Oplontis findings.
    https://greekreporter.com/2025/12/20/pompeii-excavation-villa-nero-wife-new-finds/
17. CBS News. "Archaeologists at Pompeii use AI to reveal the face of a victim trying to flee the Mount Vesuvius eruption." April 2026. Pompeii Archaeological Park / University of Padua reconstruction.
    https://www.cbsnews.com/news/pompeii-ai-face-victim-mount-vesuvius-eruption/
18. Bentley, D. R., Balasubramanian, S., Swerdlow, H. P., et al. "Accurate Whole Human Genome Sequencing using Reversible Terminator Chemistry." Nature 456: 53–59 (2008). DOI: 10.1038/nature07517. The foundational paper for Illumina sequencing-by-synthesis. See also Illumina's technology overview.
    https://www.illumina.com/science/technology/next-generation-sequencing/sequencing-technology.html
19. Meyer, M., and Kircher, M. "Illumina sequencing library preparation for highly multiplexed target capture and sequencing." Cold Spring Harbor Protocols 2010(6): pdb.prot5448 (June 2010). DOI: 10.1101/pdb.prot5448. The double-stranded library preparation protocol used in the Pompeii study and adopted as a community standard for ancient DNA.
    http://cshprotocols.cshlp.org/content/2010/6/pdb.prot5448
20. Rohland, N., Harney, E., Mallick, S., Nordenfelt, S., and Reich, D. "Partial uracil–DNA–glycosylase treatment for screening of ancient DNA." Philosophical Transactions of the Royal Society B 370(1660): 20130624 (January 19, 2015). DOI: 10.1098/rstb.2013.0624. Establishes the partial-UDG protocol used to retain terminal damage signal while removing internal uracils.
    https://royalsocietypublishing.org/doi/10.1098/rstb.2013.0624
21. Gansauge, M.-T., and Meyer, M. "Single-stranded DNA library preparation for the sequencing of ancient or damaged DNA." Nature Protocols 8: 737–748 (2013). DOI: 10.1038/nprot.2013.038. Updated in Gansauge, M.-T., et al., "Single-stranded DNA library preparation from highly degraded DNA using T4 DNA ligase," Nucleic Acids Research 45(10): e79 (2017). DOI: 10.1093/nar/gkx033.
    https://www.nature.com/articles/nprot.2013.038 · https://pmc.ncbi.nlm.nih.gov/articles/PMC5449542/
22. Rohland, N., Mallick, S., Mah, M., Maier, R., Patterson, N., and Reich, D. "Three assays for in-solution enrichment of ancient human DNA at more than a million SNPs." Genome Research 32: 2068–2078 (2022). DOI: 10.1101/gr.276728.122. Benchmarks the Reich Lab 1240K reagent against commercial Daicel Arbor Biosciences and Twist Bioscience panels. See also the foundational 1240K probe design in Mathieson, I., et al., Nature 528: 499–503 (2015), DOI: 10.1038/nature16152, and Haak, W., et al., Nature 522: 207–211 (2015), DOI: 10.1038/nature14317.
    https://pmc.ncbi.nlm.nih.gov/articles/PMC9808625/
23. Jónsson, H., Ginolhac, A., Schubert, M., Johnson, P. L. F., and Orlando, L. "mapDamage2.0: fast approximate Bayesian estimates of ancient DNA damage parameters." Bioinformatics 29(13): 1682–1684 (2013). DOI: 10.1093/bioinformatics/btt193. The standard tool for quantifying terminal C-to-T deamination patterns that authenticate ancient DNA.
    https://academic.oup.com/bioinformatics/article/29/13/1682/184965
24. Peltzer, A., Jäger, G., Herbig, A., Seitz, A., Kniep, C., Krause, J., and Nieselt, K. "EAGER: efficient ancient genome reconstruction." Genome Biology 17: 60 (2016). DOI: 10.1186/s13059-016-0918-z. The pipeline used by the Florence laboratory in the Pompeii study.
    https://genomebiology.biomedcentral.com/articles/10.1186/s13059-016-0918-z
25. Fellows Yates, J. A., Lamnidis, T. C., Borry, M., et al. "Reproducible, portable, and efficient ancient genome reconstruction with nf-core/eager." PeerJ 9: e10947 (March 2021). DOI: 10.7717/peerj.10947. The Nextflow successor to EAGER, the current community-standard pipeline. Project repository at github.com/nf-core/eager.
    https://peerj.com/articles/10947/
26. Mallick, S., Micco, A., Mah, M., Ringbauer, H., Lazaridis, I., Olalde, I., Patterson, N., and Reich, D. "The Allen Ancient DNA Resource (AADR): a curated compendium of ancient human genomes." Scientific Data 11: 182 (February 10, 2024). DOI: 10.1038/s41597-024-03031-7.
    https://www.nature.com/articles/s41597-024-03031-7
27. Allen Ancient DNA Resource (AADR), version 9.0 / v62.0. Released September 16, 2024. Harvard Dataverse, DOI: 10.7910/DVN/FFIDCW. Contains 13,571 ancient and 4,054 present-day individuals. Release page: https://reich.hms.harvard.edu/allen-ancient-dna-resource-aadr-downloadable-genotypes-present-day-and-ancient-dna-data · Versioned releases: https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/FFIDCW
28. Cheronet, O., et al. "AADR Visualizer: an ArcGIS online visualizer for ancient human DNA from the Allen Ancient DNA Resource." Bioinformatics Advances 5(1): vbaf199 (August 2025). DOI: 10.1093/bioadv/vbaf199.
    https://academic.oup.com/bioinformaticsadvances/article/5/1/vbaf199/8238351
29. European Nucleotide Archive (ENA). Sequencing data for Pilli et al. 2024, accession PRJEB74999. Reich Lab genotype data: https://reich.hms.harvard.edu/datasets.
    https://www.ebi.ac.uk/ena/browser/view/PRJEB74999

The CubeSat Comes of Age:

A Guide To CubeSat Mission And Bus Design | Hackaday

Aerospace Engineering · Document Review & Industry Analysis

Bus Design in the Era of the Million-Dollar Spacecraft

A 1,749-page open-source textbook from the University of Hawai‘i tries to teach the world how to build a CubeSat. It mostly succeeds — but the gaps it leaves behind reveal how much the discipline has changed since the standard was written.

A review of A Guide to CubeSat Mission and Bus Design (Frances Zhu, ed., 2023), with industry context drawn from peer-reviewed literature, NASA technical reports, FCC filings, and small-satellite conference proceedings through April 2026.

Bottom Line Up Front 

 Frances Zhu's A Guide to CubeSat Mission and Bus Design is the most comprehensive open-source spacecraft engineering textbook available — funded by NASA's Artemis Student Challenge, anchored to an actual flight-ready 1U kit, and rich with mathematics in the attitude determination and control (ADCS) and electrical power (EPS) chapters. But three structural gaps undercut it: no dedicated propulsion chapter in a book whose own contributing author is a propulsion specialist; no dedicated mission operations chapter, despite the textbook's claim that one of its co-authors literally wrote the operations chapter of the SMAD reference text; and a radiation-hardening discussion that is dangerously thin for the COTS-heavy ethos the book promotes. The CubeSat industry, meanwhile, has galloped past the 2,700-launched mark and is on track for a $1.7-billion-plus market by 2034, while four of ten CubeSats on the Artemis I flight failed outright — including NASA's own NEA Scout. Bus design is no longer a student exercise. It is a high-stakes engineering discipline with a 25-to-48-percent infant-mortality rate, and the next generation of textbooks needs to teach it that way.

I. The Document, in Brief

In late 2023, Dr. Frances "Frankie" Zhu, an assistant research professor at the University of Hawai‘i at Mānoa and Principal Investigator for the Artemis CubeSat Kit, released a Creative Commons textbook titled A Guide to CubeSat Mission and Bus Design. The 1,749-page volume — produced through Pressbooks 6.14.0 and rendered to PDF via Prince 15.1 — is the curricular spine of NASA's Artemis Student Challenge, an effort to put a flight-ready 1U CubeSat kit into the hands of universities, community colleges, and even middle schools for under $5,000.

The book is enormous, ambitious, and openly idealistic. Its preface declares an intention to "get rid of the silly notion that you need to be a 'rocket scientist' to work [on] stuff that goes to space." It is, in that sense, a direct intellectual descendant of Wertz, Larson, and Everett's Space Mission Engineering — The New SMAD (Microcosm Press, 2011), but explicitly retargeted at the CubeSat-class missions that SMAD's last revision did not cover.

Authorship is collective. Zhu wrote most of the content. Avionics engineer Amber Imai-Hong of the Hawai‘i Space Flight Laboratory (HSFL) reviewed the electrical power and command-and-data-handling chapters. Dr. Trevor Sorensen — author of the Mission Operations chapter in The New SMAD, AIAA Fellow, and former Clementine Lunar Mission Manager — wrote the space-environment, orbital-mechanics, and propulsion sections. The book is licensed CC BY 4.0 and remains free.

What the textbook covers

The structure follows a recognizable spacecraft-engineering arc:

Ch.	Title	Approx. depth
1	Introduction (When/Who/Why/What/How)	Light, contextual
2	Systems Engineering, Requirements, Risk	Substantial
3	Design Drivers, Space Environment, Orbital Mechanics	Heavy
4	Structures & Mechanisms	Substantial; FEA-light
5	Electrical Power System (EPS)	Heavy
6	Communications & RF (Link Budget)	Heavy
7	Thermal Control	Substantial
8	Attitude Determination, Control & Sensing (ADCS)	Very heavy — the book's strongest chapter
9	Command & Data Handling / Avionics / Software	Heavy; conflated with ops
11	Verification, Validation, & Test	Moderate
12	Engineering Ethics (5 cases)	Brief

Note the absent number. There is no Chapter 10. Propulsion does not have its own chapter at all — only scattered sub-sections inside ADCS (under "Internal Torques → Thrusters") and isolated paragraphs elsewhere. Mission Operations, similarly, is folded into the CDH chapter rather than treated as its own discipline. For a book whose front matter explicitly credits Dr. Sorensen with "the propulsion sections" and whose academic counterpart (SMAD) devotes a full chapter to ops, these are conspicuous omissions.

II. The Bus, Decomposed

To understand what the textbook does well — and where it falls short — it helps to step back and define the discipline it teaches.

A spacecraft bus is everything that is not the payload. In the canonical decomposition that Zhu adopts from SMAD and the NASA Systems Engineering Handbook, a CubeSat bus comprises seven subsystems plus the payload itself:

1. Structures & Mechanisms. The aluminum skeleton (typically 6061-T6, hard-anodized) that holds everything together, survives a 14.1-grms vibration environment on launch, and complies with the rail tolerances in Cal Poly's CubeSat Design Specification Rev. 14.1. Includes deployables: antennas, solar panels, booms.
2. Electrical Power System (EPS). Solar cells, batteries, power conditioning. For a 1U in low Earth orbit, this is roughly 1–2 W average generation against a duty cycle of roughly half-eclipse.
3. Command & Data Handling (C&DH). The flight computer, the bus that connects subsystems (typically I²C, SPI, CAN, or SpaceWire), and the watchdog timers that keep a single-event upset from becoming a mission-killer.
4. Communications/RF. Typically UHF or S-band for telemetry and command, with X-band increasingly common for high-rate payload downlink.
5. Attitude Determination, Control & Sensing (ADCS). The hardest discipline on the bus. Sun sensors, magnetometers, IMUs, and star trackers feed quaternion-based filters (TRIAD, q-method, Kalman); reaction wheels, magnetorquers, and increasingly micro-thrusters apply control torques.
6. Thermal Control. Passive in nearly every CubeSat — multi-layer insulation, paint coatings, thermal straps — with active heaters as exceptions.
7. Propulsion. Optional in most missions, but increasingly a make-or-break subsystem for any CubeSat that needs to maneuver, hold formation, deorbit, or reach beyond LEO.

"The capacity or information that can be obtained by the CubeSats is limited because they lack power generation, a reliable position determination and control system, and a propulsion system for on-orbit mobility."
— Spherical Insights industry analysis, 2024

That single sentence captures the engineering problem the textbook is trying to solve. Bus design, properly understood, is the art of compromising among power, mass, volume, thermal load, attitude stability, and reliability against the tyrannical constraint of the 10×10×10 cm CubeSat unit. Zhu's textbook teaches this compromise reasonably well in five of seven subsystems. It teaches it weakly in two.

III. Where the Textbook Excels

The ADCS chapter is genuinely outstanding

Chapter 8 — written by Zhu, who was the Attitude Dynamics, Control, and Sensing lead for what she describes as "the most agile declassified small satellite at the time" during her undergraduate years at Cornell — runs through Euler angles, rotation matrices, Euler axis/axis-angle, and quaternions, then derives quaternion kinematics and Euler's rigid-body equations. It moves through TRIAD, Wahba's problem (with both SVD and q-method solutions), and the discrete-time Kalman filter for attitude estimation. It then catalogs sensors (sun, horizon, star trackers, magnetometers, MEMS gyros, IMUs, GPS) and actuators (magnetorquers, reaction wheels, control moment gyros, thrusters), and ends with pointing budgets and mode logic.

This is graduate-level material delivered with classroom clarity. It is, frankly, the best free treatment of CubeSat ADCS in the public domain.

The EPS and CDH chapters are pragmatic and kit-anchored

Chapter 5 (EPS), reviewed by Imai-Hong, walks through power generation (solar cell efficiency, MPPT), consumable storage (primary cells), rechargeable storage (lithium-ion chemistry, depth-of-discharge cycling), power management and distribution, and — critically — power budgeting and profiling against orbital duty cycles. Chapter 9 (CDH) treats flight software architecture, real-time operating systems (VxWorks, RTEMS, FreeRTOS), watchdog timers, and the COSMOS Comprehensive Open-architecture Solution for Mission Operations Systems framework that HSFL itself developed. The discussion of watchdog circuits — "an 'I'm okay' method of SEU detection" that resets the microcontroller via a load switch when a Single-Event Functional Interrupt occurs — is directly drawn from Vanderbilt's COTS-radiation work and is the kind of system-level mitigation that sober CubeSat builders actually use.

The book is honest about Class D risk

Zhu writes plainly that the Artemis Kit's components are not space-rated, that the kit operates in NASA's Class D mission category — "low priority, high risk, minimally complex … significant alternative or re-flight opportunities" — and that a CubeSat program exists at the extreme end of that risk envelope. This honesty is rare in educational materials and important. It tells the student that what they are building is not a Mars rover.

IV. Where the Textbook Falls Short

GAP #1 — STRUCTURAL OMISSION

No dedicated propulsion chapter

Sorensen, per his own bio in the book, "wrote the space environment, orbital mechanics, and propulsion sections." The first two appear as full subsections of Chapter 3. The third does not. There is no Chapter 10. Propulsion appears only as scattered fragments — a few paragraphs about thrusters as ADCS internal torques, brief mentions of orbit control inside Chapter 9, and a passing reference to a GMAT solution using "a low thrust propulsion system."

This omission is no longer defensible in 2026. Of the four CubeSats on Artemis I that were intended to perform propulsive maneuvers — TACHELES, ATENEA, K-RadCube, and SHAMS — only one (SHAMS) successfully fired its thrusters to raise perigee. The other three burned up in the atmosphere. And on the same flight, NEA Scout, NASA's own 6U solar-sail mission, was lost — never deployed its sail, never reached its asteroid target. The propulsion subsystem is now squarely on the critical path for any CubeSat that does more than tumble in a parking orbit, and a textbook that omits it omits the most failure-prone discipline in the bus.

The rapid pace of micro-propulsion development makes the omission even more pressing. MIT's Space Propulsion Laboratory (Lozano, Krejci, Velásquez-García) has now published peer-reviewed designs for additively manufactured iodine-fed and ionic-liquid electrospray thrusters that fit eight modules of four emitters each into a sub-1U envelope, producing 75 µN at specific impulses of 800–1,600 s and over 350 m/s of delta-V from a 1 kg CubeSat. A 2025 Advanced Science paper from the same group demonstrated 3D-printed, throttleable electrospray emitters with near-100% extractor transmission. None of this appears in Zhu's textbook.

GAP #2 — STRUCTURAL OMISSION

No dedicated mission operations chapter

Mission operations — the discipline of planning passes, scheduling commands, monitoring telemetry, and managing flight dynamics — is folded entirely into the CDH/avionics chapter. This is a categorical confusion. CDH is hardware-and-firmware. Operations is a human-and-process discipline that has its own NASA handbooks, its own software stack (in this case HSFL's own COSMOS framework), and its own failure modes.

BioSentinel, the 6U deep-space CubeSat that Artemis I deployed in November 2022, is a case in point. Its biology payload failed within weeks, but the bus is still alive. As of mid-2025, the spacecraft was approximately 70 million kilometers from Earth, communicating via the NASA Deep Space Network roughly once per week. Its LET radiation spectrometer continued returning data through solar maximum. The reason the bus survived is not because the hardware was special — most of it was COTS — but because the operations team rehearsed orbit determination, coordinated trajectory work with the DSN and ESA, and built a contact schedule that absorbed deployment-state uncertainty from the SLS Interim Cryogenic Propulsion Stage. That entire body of practice is essentially missing from Zhu's text.

GAP #3 — TECHNICAL DEPTH

The radiation-hardening discussion is too thin

The textbook acknowledges Single-Event Effects (SEEs) — Single-Event Upsets, Latchups, and Functional Interrupts — and discusses watchdog timers and current-limiting load switches at the system level. But it does not treat Total Ionizing Dose (TID) budgeting, displacement damage, the Careful COTS upscreening methodology, or the radiation-hardness assurance (RHA) standards (MIL-STD-883 TM1019, JEDEC JESD57, ECSS-Q-ST-60-15C) that govern qualification.

This matters because the book's pedagogy explicitly endorses non-space-rated COTS components, and yet it does not teach the parts-screening and lot-control practices that distinguish a 30-krad mission that flies from a sub-1-krad part that fails on day one. Vanderbilt's Goal Structuring Notation work for CubeSat radiation reliability — formally adopted by NASA SMA — is a far better starting point for the student who wants to fly a real Class D mission. The 2024 release of ECSS-Q-ST-60-15C and ongoing Canadian Space Agency RADHARD work on Canadarm3 represent active developments the textbook cannot capture because of its 2023 cut date, but the omission of even the foundational concept of a radiation design margin (RDM) is harder to forgive.

GAP #4 — FACTUAL/CITATION HYGIENE

Sourcing leans heavily on Wikipedia and informal references

Many of the textbook's technical claims are cited inline as "[Wikipedia]," "[NASA]" without document number, "[SMAD]," or simply "[Newcomb]" / "[Whitwam]" — the latter two appear to be popular-press articles cited without dates, URLs, or DOIs. For a free educational resource targeted at students, this sets a poor example of citation hygiene. Mature aerospace engineering texts cite primary sources: NASA Technical Reports Server documents (NTRS), AIAA conference papers, ECSS standards, and peer-reviewed journals. Zhu's appendix does point students toward the NASA Systems Engineering Handbook, NASA Cost Estimating Handbook, and Doody's Basics of Spaceflight, but the inline citations throughout the body do not consistently follow.

GAP #5 — REGULATORY CURRENCY

FCC orbital-debris rules are not addressed

Any CubeSat operator authorized by the United States is now bound by the FCC's five-year post-mission disposal rule, codified in 47 CFR Part 25 and effective for any satellite launched after 29 September 2024. The rule replaced the long-standing 25-year guideline and applies to all Commission-licensed and -market-access NGSO systems. The FCC has gone further: the 28 October 2025 Space Modernization for the 21st Century NPRM proposes to replace Part 25 entirely with a new Part 100, introducing a "Variable Trajectory Spacecraft System" license category for lunar, ISAM, and orbital-transfer missions.

Cal Poly's CubeSat Design Specification Rev. 14.1 (February 2022) is referenced in the textbook, which is appropriate. But the FCC framework that determines whether any of the kits Zhu's program ships will ever legally talk to the ground is not. NASA's Debris Assessment Software (DAS, version 3.2.5 as of February 2024) is the tool every applicant must run, and it is unmentioned.

GAP #6 — MINOR ERRORS

Small factual slips and outdated context

• The book claims SMAD's last revision was in 2011. Space Mission Engineering: The New SMAD, edited by Wertz, Everett, and Puschell, was published by Microcosm Press in 2011 — that is correct — but the textbook does not acknowledge that SMAD has been the subject of considerable critical commentary in the small-satellite community for being insufficiently CubeSat-aware. This is, in fact, Zhu's stated motivation for writing her book, but the comparison would be sharper with concrete page references.
• The explanation of Sputnik "blinking lights" to confirm survival is poetic but technically wrong. Sputnik 1 (1957) carried a 20.005 / 40.002 MHz radio beacon emitting 0.3-second pulses; it had no optical signaling. Subsequent Soviet satellites used optical reflection from highly polished surfaces for ground tracking, not as a survival indicator.
• The CubeSat Design Specification is cited as "Rev. 14" in the chapter outline but should be Rev. 14.1, the version actually published by Cal Poly in February 2022.
• Several H5P interactive elements and embedded YouTube videos are referenced in-line as "[An interactive H5P element has been excluded from this version of the text]" — appropriate for a PDF export, but the text never tells the reader what they are missing or how to access the live Pressbooks edition. A simple URL or QR code at each excised block would solve this.

V. The Industry Context: Why Bus Design Has Gotten Harder

Zhu's textbook describes a CubeSat ecosystem that is, in 2026, three to five years behind the curve. The discipline is no longer the educational toy of the early 2000s.

The numbers are now industrial-scale

According to Erik Kulu's authoritative Nanosats Database at IAC 2024, the cumulative CubeSat-and-nanosatellite count surpassed 4,200 entries with more than 2,714 actually launched. A record 390 nanosatellites flew in 2023 alone — 359 of them CubeSats — with Planet Labs leading at 72, SpaceX/Swarm at 24, and Spire at 22. Roughly 75% of nanosats now ride on Falcon 9. The 2,000th launched CubeSat flew in early 2023; the first thousand had taken nearly 16 years, the second thousand fewer than four.

Market-research consensus places the 2025 CubeSat market at $480–540 million, with multiple analysts (IMARC, Market Research Future, SkyQuest, Fortune Business Insights) projecting compound annual growth rates of 11–16% through 2033–2034 and totals approaching $1.7–2.2 billion by mid-decade. North America holds roughly three-quarters of the market by revenue. The 3U form factor is now the industry workhorse, with 6U and 12U buses growing fastest for commercial Earth observation and deep-space missions.

The reliability problem has not gone away

The most rigorous statistical work — Langer and Bouwmeester's analyses through 2017, updated by Kulu through 2024 — shows infant-mortality (dead-on-arrival or sub-30-day failure) rates of 25–48 percent for university-class CubeSats. After 30 days, the EPS becomes the dominant failure mode (40+%); after 90 days, the communications subsystem accounts for nearly 30% of failures. About one-third of failed missions never received a single radio signal after launch. Subsystem-level redundancy and improved testing — particularly hardware-in-the-loop simulation and disciplined system-level integration testing — have been shown to reduce these failures, but no university CubeSat textbook (Zhu's included) yet treats reliability engineering as a first-class discipline alongside ADCS or EPS.

Of ten secondary-payload CubeSats on Artemis I, four failed outright. NEA Scout, OMOTENASHI, Team Miles, and LunIR either never made contact or returned only weak signals.

Deep space changes everything

The Artemis I CubeSat manifest of November 2022 was both a triumph and a wake-up call. Of the ten 6U secondaries deployed from the SLS Interim Cryogenic Propulsion Stage, four were declared mission failures within weeks. JAXA's OMOTENASHI lunar lander could not establish stable communications. NASA's NEA Scout never deployed its 86-square-meter solar sail. Lockheed Martin's LunIR returned only a weak signal. Team Miles never made contact at all. The survivors — BioSentinel chief among them, alongside ArgoMoon, BioSentinel, EQUULEUS, and the LunaH-Map mission that eventually lost its propulsion system — taught the community that deep-space CubeSat operations require fundamentally different bus design choices than LEO.

BioSentinel's after-action papers, presented at the 2023 Small Satellite Conference and at the 2024 IEEE Aerospace Conference, identify three key bus-design lessons: (1) the JPL Iris transponder, designed specifically for the Deep Space Network, was the single most critical enabler; (2) autonomous attitude control with on-board momentum management was indispensable because round-trip light time made human-in-the-loop pointing impractical; and (3) micro-propulsion was needed not for trajectory changes but simply for desaturation of reaction wheels in the absence of a usable Earth magnetic field. The ICPS deployment dropped BioSentinel within "a few hundred kilometers" of lunar impact — a cautionary tale about the dispersion of CubeSat deployment from a spinning upper stage.

CAPSTONE, Advanced Space's 25 kg, microwave-oven-sized CubeSat that reached the Near Rectilinear Halo Orbit around the Moon in November 2022, told a similar story. After early in-orbit anomalies that nearly cost the mission, software patches uploaded via DSN restored attitude control and enabled cross-link experiments with the Lunar Reconnaissance Orbiter and an early demonstration of the Cislunar Autonomous Positioning System (CAPS). CAPSTONE has since served as the operational pathfinder for the planned Gateway lunar space station.

Artemis II, now scheduled for early February 2026, will fly four more CubeSats: TACHELES (Germany — electronic component lunar exposure), ATENEA (Argentina — radiation shielding and GPS at lunar distance), K-RadCube (Korea — tissue-simulant radiation effects), and SHAMS (Saudi Arabia — high-altitude space weather). Of these, only SHAMS successfully fired propulsion to raise perigee on the Artemis I rehearsal.

Propulsion technology is the new frontier

The most active area of CubeSat bus innovation in 2024–2026 is propulsion. Cold-gas systems (Imken, Stevenson, & Lightsey, 2015; UT Austin's Cold Gas System aboard NEA Scout) remain the conservative choice, but electric propulsion has matured rapidly. MIT's Ion Electrospray Propulsion System (iEPS) — using room-temperature ionic liquid propellants and arrays of 480 emitter tips per square centimeter — has flown on multiple constellation-management demonstrations. The Velásquez-García group's 2025 demonstration of additively manufactured electrospray thrusters represents a major step toward the routine production of micro-thrusters tailored to specific mission delta-V budgets. Iodine Hall thrusters from Busek and ThrustMe (the latter flown on multiple commercial missions) bring 200–500 N·s/kg total impulse to the 12U-and-up class.

Radiation-tolerant computing has shifted to RISC-V

The other frontier is the flight computer. The traditional CubeSat C&DH solution — a Cortex-M0 or M4 microcontroller wrapped in watchdogs and ECC memory — is being augmented by space-grade FPGAs (Xilinx Zynq UltraScale+, Microchip ProASIC3) and, increasingly, by RISC-V-based fault-tolerant SoCs. The Trikarenos chip from ETH Zürich and the University of Bologna, fabricated in TSMC 28 nm, demonstrates a configurable triple-core lockstep RISC-V microcontroller delivering 21.5× better efficiency than prior space-grade ASICs while running fault-tolerant matrix multiplication at 250 MHz on 15.7 mW. Vorago Technologies' rad-hard Cortex-M0 microcontrollers have become the de facto reference design for supervisor boards on multi-DPU CubeSat avionics. Zhu's textbook predates all of this.

VI. What a Second Edition Should Add

If Zhu and the HSFL team produce a 2026–2027 revision — and they should — the highest-leverage additions would be:

1. A standalone propulsion chapter covering cold-gas, monopropellant (the now-ubiquitous green AF-M315E / ASCENT propellant), iodine Hall, electrospray, pulsed plasma, and resistojet/electrothermal options, with delta-V/Isp/power trade trees and the FCC's deorbit-compliance implications baked in.
2. A standalone mission operations chapter, drawing on Sorensen's SMAD operations work, with treatment of pass planning, anomaly response, the Mission Operations Cost Estimation Tool (MOCET), and case studies from BioSentinel and CAPSTONE.
3. A radiation-hardness assurance chapter covering TID budgeting, displacement damage, SEE rates and cross-sections, the Careful COTS methodology, and modern standards (MIL-STD-883 TM1019, JEDEC JESD57, ECSS-Q-ST-60-15C).
4. A regulatory chapter covering FCC Part 25 / Part 100, the September 2024 five-year deorbit rule, NASA DAS workflow, ITU coordination, and ITAR/EAR licensing for international student teams.
5. A reliability engineering chapter using Langer's Weibull analyses and the empirical subsystem-failure-mode data to teach students how to do failure modes and effects analysis (FMEA) appropriate to Class D missions.
6. An expanded deep-space subsystem chapter covering Iris-class transponders, DSN coordination, autonomy requirements, momentum-management strategies in the absence of magnetic torque, and trajectory-uncertainty budgeting.
7. Tightened citations: NTRS document numbers, AIAA paper numbers, DOIs for journal citations, and removal of bare Wikipedia references in favor of primary sources.

VII. The Verdict

For a free, NASA-funded, Creative-Commons-licensed open-source textbook, A Guide to CubeSat Mission and Bus Design sets a remarkable bar. Its ADCS chapter alone is worth the download. Its EPS, communications, and CDH treatments are pragmatic and grounded in actual flight hardware. Its honesty about Class D risk and its explicit pairing with a sub-$5,000 buildable kit make it pedagogically powerful in ways the SMAD reference cannot be.

But CubeSat bus design has crossed a threshold. The 2,700-launch milestone, the four-of-ten Artemis I CubeSat failure rate, the FCC's five-year deorbit mandate, the rapid proliferation of micro-propulsion options, and the migration of flight computing toward RISC-V fault-tolerant SoCs together constitute an inflection point. A textbook that omits propulsion as a chapter, that conflates operations with avionics, and that treats radiation hardening as a paragraph cannot be the definitive reference for the field as it now stands.

Zhu's textbook is, however, the right starting point. Paired with the Cal Poly CDS Rev. 14.1, the NASA Systems Engineering Handbook, the FCC orbital-debris rules, the SmallSat Conference proceedings, and the Nanosats Database, it gives a determined undergraduate or self-taught engineer most of what they need to design a CubeSat bus that has a reasonable chance of surviving its first 30 days on orbit.

That chance, the data say, is somewhere between 52 and 75 percent. It is going to take a better textbook — and a more rigorously sourced one — to push that number higher.

Reviewer's Note

The Artemis CubeSat Kit and the textbook reviewed here remain freely available at pressbooks-dev.oer.hawaii.edu/epet302 and through the Hawai‘i Space Flight Laboratory at hsfl.hawaii.edu. Mahina Aerospace distributes the physical kit. Despite the gaps identified above, this reviewer recommends the textbook to any student or club beginning serious CubeSat bus development — with the caveat that it should be supplemented by the additional sources cited below.

Verified Sources & Citations

Primary Document Under Review

1. Zhu, F. (ed.) (2023). A Guide to CubeSat Mission and Bus Design (cloned version, August 2023). University of Hawai‘i at Mānoa, Hawai‘i Space Flight Laboratory. Pressbooks. CC BY 4.0.
   https://pressbooks-dev.oer.hawaii.edu/epet302/
2. Sloan, A., Ngo, K., Amendola, C., Clements, L., Takushi, E., Imai-Hong, A., & Zhu, F. (2022). "University of Hawaii's Spaceflight-Ready, Low-Cost, Open-Source, Educational Artemis CubeSat Kit." 36th Annual Small Satellite Conference, SSC22-WKV-04.
   https://digitalcommons.usu.edu/smallsat/2022/all2022/76/

Standards and Reference Texts

3. Johnstone, A. (2022). CubeSat Design Specification Rev. 14.1. The CubeSat Program, California Polytechnic State University, San Luis Obispo. CP-CDS-R14.1.
   https://static1.squarespace.com/static/5418c831e4b0fa4ecac1bacd/t/62193b7fc9e72e0053f00910/1645820809779/CDS+REV14_1+2022-02-09.pdf
4. Wertz, J. R., Everett, D. F., & Puschell, J. J. (eds.) (2011). Space Mission Engineering: The New SMAD. Microcosm Press, Hawthorne, CA. ISBN 978-1881883159.
5. NASA (2017). NASA Systems Engineering Handbook, Rev. 2. NASA/SP-2016-6105.
   https://www.nasa.gov/sites/default/files/atoms/files/nasa_systems_engineering_handbook_0.pdf

Industry Statistics and Market Data

6. Kulu, E. (2024). "CubeSats & Nanosatellites — 2024 Statistics, Forecast and Reliability." 75th International Astronautical Congress (IAC 2024), Milan, Italy, October 14–18, 2024.
   https://www.nanosats.eu/assets/CubeSats-Nanosatellites-2024_ErikKulu_IAC2024.pdf
7. Nanosats Database (2026). World's largest CubeSat database, maintained by E. Kulu.
   https://www.nanosats.eu/
8. IMARC Group (2025). "CubeSat Market Size, Analysis, Trends & Forecast 2026–2034." Market valuation $482.1M (2025) → $1,756.1M (2034), 15.40% CAGR.
   https://www.imarcgroup.com/cubesat-market
9. Market Research Future (2025). "CubeSat Market Size, Share, Growth | Industry Outlook 2035." Projected $495.69M (2025) → $2,204.13M (2035), 16.09% CAGR.
   https://www.marketresearchfuture.com/reports/cubesat-market-7523
10. Fortune Business Insights (2025). "CubeSat Market Size, Share | Global Growth Report [2032]." $488.7M (2024) → $1,115.8M (2032), 11.1% CAGR.
    https://www.fortunebusinessinsights.com/cubesat-market-113707

Reliability and Failure Analysis

11. Langer, M., & Bouwmeester, J. (2016). "Reliability of CubeSats — Statistical Data, Developers' Beliefs and the Way Forward." 30th Annual AIAA/USU Conference on Small Satellites, SSC16-X-2.
    https://digitalcommons.usu.edu/cgi/viewcontent.cgi?article=3397&context=smallsat
12. Bouwmeester, J., Langer, M., & Gill, E. (2022). "Improving CubeSat Reliability: Subsystem Redundancy or Improved Testing?" Reliability Engineering & System Safety, Vol. 220.
    https://www.sciencedirect.com/science/article/pii/S0951832021007584
13. Villela, T., Costa, C. A., Brandão, A. M., Bueno, F. T., & Leonardi, R. (2019). "Towards the Thousandth CubeSat: A Statistical Overview." International Journal of Aerospace Engineering, 2019:5063145.
    https://www.hindawi.com/journals/ijae/2019/5063145/
14. Cho, M. et al. (2019). "CubeSat Mission: From Design to Operation." Applied Sciences, 9(15):3110. (University-led CubeSat early failure rate ≈ 48%.)
    https://www.mdpi.com/2076-3417/9/15/3110

Deep-Space CubeSat Missions

15. Hanson, M. et al. (2025). "NASA's BioSentinel Deep Space CubeSat Mission: Successes and Lessons Learned." Acta Astronautica (in press), available via ScienceDirect.
    https://www.sciencedirect.com/science/article/abs/pii/S009457652500428X
16. NASA Ames Research Center (2024). "BioSentinel: Forging the Path for Deep Space CubeSat Missions." NTRS document 20240000966.
    https://ntrs.nasa.gov/citations/20240000966
17. Hanson, M. et al. (2023). "BioSentinel: Mission Summary and Lessons Learned From the First Deep Space Biology CubeSat Mission." 37th Annual Small Satellite Conference, SSC23-WKII-02.
    https://digitalcommons.usu.edu/smallsat/2023/all2023/67/
18. NASA JPL (2014). "Near-Earth Asteroid Scout." AIAA SPACE 2014 Conference. NTRS 20140012882.
    https://ntrs.nasa.gov/api/citations/20140012882/downloads/20140012882.pdf
19. David, L. (2023). "CAPSTONE Moon Mission — Challenges, Lessons Learned." SpaceRef.
    https://spaceref.com/science-and-exploration/capstone-moon-mission-challenges-lessons-learned/
20. Wikipedia contributors (2026, April). "Artemis II." Wikipedia. (Includes manifest of TACHELES, ATENEA, K-RadCube, and SHAMS CubeSats.)
    https://en.wikipedia.org/wiki/Artemis_II

Propulsion

21. Kim, H., & Velásquez-García, L. F. (2025). "High-Impulse, Modular, 3D-Printed CubeSat Electrospray Thrusters Throttleable via Pressure and Voltage Control." Advanced Science, 12, 2413706. DOI: 10.1002/advs.202413706.
    https://advanced.onlinelibrary.wiley.com/doi/10.1002/advs.202413706
22. Krejci, D., & Lozano, P. (2018). "Micro-machined Ionic Liquid Electrospray Thrusters for CubeSat Applications." MIT Space Propulsion Laboratory.
    https://www.researchgate.net/publication/320335334
23. Krejci, D., Mier-Hicks, F., Thomas, R., Haag, T., & Lozano, P. (2018). "CubeSat Constellation Management Using Ionic Liquid Electrospray Propulsion." Acta Astronautica, Vol. 148.
    https://www.sciencedirect.com/science/article/abs/pii/S0094576517312511
24. Imken, T. K., Stevenson, T. H., & Lightsey, E. G. (2015). "Design and Testing of a Cold Gas Thruster for an Interplanetary CubeSat Mission." Journal of Small Satellites, 4(2):371–386.

Radiation Effects and COTS Components

25. Austin, R. A., Sierawski, B. D., & Witulski, A. F. (2017). "A CubeSat-Payload Radiation-Reliability Assurance Case Using Goal Structuring Notation." 2017 IEEE Aerospace Conference.
    https://ieeexplore.ieee.org/document/7889672
26. Sinclair, D., & Dyer, J. (2013). "Radiation Effects and COTS Parts in SmallSats." 27th AIAA/USU Small Satellite Conference.
    https://digitalcommons.usu.edu/cgi/viewcontent.cgi?article=2934&context=smallsat
27. Rogenmoser, M., & Benini, L. (2023). "Trikarenos: A Fault-Tolerant RISC-V-based Microcontroller for CubeSats in 28nm." ETH Zürich / University of Bologna. arXiv:2310.02045.
    https://arxiv.org/pdf/2310.02045
28. Vanderbilt University Space Electronics group (2017). "Goal Structuring Notation in a Radiation Hardening Assurance Case for COTS-Based Spacecraft." NASA Office of Safety and Mission Assurance.
    https://sma.nasa.gov/docs/default-source/News-Documents/goal-structuring-notation-in-a-radiation-hardening-assurance-case-for-cots-based-spacecraft.pdf
29. "Hardening and Advancing COTS FPGA/GPU Integrated Circuits for the Realization of Space-Grade System-on-Module" (2025). 39th Annual AIAA/USU Conference on Small Satellites, SSC25-95.
    https://digitalcommons.usu.edu/smallsat/2025/all2025/95/

Regulatory and Government

30. Federal Communications Commission (2022). "Mitigation of Orbital Debris in the New Space Age, Second Report and Order." FCC 22-74. (Five-year post-mission disposal rule, effective 29 September 2024.)
    https://docs.fcc.gov/public/attachments/FCC-22-74A1.pdf
31. Federal Communications Commission (2024). "Space Innovation; Mitigation of Orbital Debris in the New Space Age." 89 FR 65221, 9 August 2024.
    https://www.federalregister.gov/documents/2024/08/09/2024-17093/space-innovation-mitigation-of-orbital-debris-in-the-new-space-age
32. Federal Communications Commission (2025). "Space Modernization for the 21st Century — Notice of Proposed Rulemaking." Adopted 28 October 2025.
    https://docs.fcc.gov/public/attachments/DOC-415048A1.pdf
33. Federal Communications Commission (2024). "FAQ: Orbital Debris."
    https://www.fcc.gov/space/faq-orbital-debris
34. NASA Orbital Debris Program Office (2024). Debris Assessment Software (DAS) v3.2.5. NASA Johnson Space Center.
    https://orbitaldebris.jsc.nasa.gov/mitigation/das.html
35. National Science and Technology Council (2022). National Orbital Debris Implementation Plan. Office of Science and Technology Policy.
    https://www.whitehouse.gov/wp-content/uploads/2022/07/07-2022-NATIONAL-ORBITAL-DEBRIS-IMPLEMENTATION-PLAN.pdf

Article prepared 28 April 2026. Sources verified through that date. The reviewer holds no financial or institutional relationship to the University of Hawai‘i, the Hawai‘i Space Flight Laboratory, Mahina Aerospace, NASA, the FCC, or any commercial CubeSat manufacturer named herein.