Blackbeard's Production Award: What SBIR Phase III Accelerates—and What the Navy Still Has to Prove
Back to Signal
DefenseInnovationManufacturingGovernment

Blackbeard's Production Award: What SBIR Phase III Accelerates—and What the Navy Still Has to Prove

September 25, 2026Peter Galle

Read the award in its actual sequence

Castelion announced an initial production order valued at up to $200 million on September 14. The company identifies the Navy's Portfolio Acquisition Executive for Aviation and its Future Capability Development and Integration Aviation Rapid Capabilities Cell as the awarding organization. It describes Blackbeard as an air-launched hypersonic strike weapon and its development as a partnership combining private investment with military work. That is a materially different story from a privately developed weapon arriving at a government buyer with no government development history. Castelion production announcement

The department's September 14 contract notice separately lists a $43.65 million firm-fixed-price order for 444 all-up rounds, with completion expected in September 2028. It identifies earlier Phase II and Phase III work and Naval Air Warfare Center Aircraft Division, Lakehurst, as the contracting activity. The notice and the broader announcement describe different financial figures; dividing the announcement's maximum value by the round count would not establish an accepted unit price. Neither a contract completion date nor an early capability target should be presented as achieved initial operational capability. Department contract notice

There is an earlier step worth retaining in the story. In June, Castelion announced a $23.4 million order for 50 early operational capability pre-production prototypes and their containers, expected to finish in 2027. That announcement explicitly described continued maturation. A production announcement therefore belongs in a sequence of integration, test, prototype, and manufacturing work; it cannot by itself settle which of those activities has finished. June prototype order

What Phase III actually buys

Under the SBA's policy directive, Phase III work must derive from, extend, or complete earlier SBIR/STTR work and use funding outside those programs. It can include further research, production, services, or a combination. Funding may come from other federal accounts or private sources. Prior Phase I or II competition can satisfy the competition requirement for the follow-on, and Phase III has no dollar ceiling. Private investment alone does not establish eligibility. SBA policy directive, section 4(c)

The practical advantage is continuity. A buyer can carry qualifying technology forward without rerunning a broad source selection simply to reach the next application. That can preserve engineering momentum, reduce transaction time, and give a supplier a stronger basis for investing in capacity. It also places real weight on the government's explanation of how the new work relates to the earlier award.

Contracting authority and production readiness answer different questions. An authorized follow-on can still contain development risk. Calling the work production does not establish that its design is stable, its manufacturing process is repeatable, or its integration schedule is executable. Those judgments require evidence specific to the deliverable.

Private capital changes the risk discussion

Castelion says private investment, vertical integration, and commercial manufacturing methods support its approach. The work is planned for its Project Ranger campus in Rio Rancho and its Torrance facility. Those are supplier commitments and strategy statements, not independent proof of sustained output. Company production announcement

The attraction for the government is clear: investment and engineering activity can move before the full traditional acquisition sequence would finance them. The concern is equally concrete. If unresolved design work reaches the production line, fixed-price terms do not recover a lost fleet delivery window. A supplier may absorb certain cost overruns while the government still carries the operational consequence of delay.

Comparisons with Conventional Prompt Strike need the same discipline. An air-launched weapon and a ship-launched strategic strike system have different integration demands, missions, and acceptance criteria. A faster contracting route is worth examining, but a headline-to-headline schedule comparison cannot isolate whether the acquisition method, technical scope, funding history, or production maturity drove the difference.

Five questions before repeating the model

  1. Establish the lineage. Show which earlier SBIR work the proposed delivery order extends and which new tasks remain developmental.
  2. Separate the milestones. Track contract award, design stability, test completion, platform certification, accepted rounds, and operational availability as distinct events.
  3. Test the production plan. Examine demonstrated throughput, supplier dependencies, inspection capacity, and the consequences of late design changes.
  4. Make acceptance enforceable. Tie deliverables and payment decisions to measurable requirements, with named responsibility for technical and safety approvals.
  5. Fund the fleet relationship. Include training, handling, maintenance, configuration control, and replenishment in the plan that follows the initial lot.

These questions preserve the value of acceleration. They prevent the contracting method from becoming a substitute for the work needed to deliver safely and reliably.

Distinguish a factory delay from an acceptance delay

Consider a hypothetical follow-on program whose supplier finishes an initial lot while a government-controlled integration event moves to a later date. Production has progressed, but the buyer cannot yet conclude that the delivery supports the intended operational milestone. The schedule problem differs from a lot that must return for manufacturing rework. Combining both under “late delivery” conceals which party can resolve the constraint.

The program's recovery discussion should separate the causes before negotiating a response. If a government event is the limiting dependency, leadership needs an accountable owner for that event and a clear account of the consequences for storage, acceptance, payment, and subsequent work. If manufacturing rework is limiting progress, the supplier needs a credible corrective-action plan and evidence that the same problem will not recur. This is an acquisition-management example, not a report of either condition in Blackbeard.

An integrated milestone record helps keep those distinctions intact. It should show the contractual deliverable, the event needed to accept it, the responsible organization, and the decision that depends on completion. Commercial production activity, government assessment, and operational availability can then be discussed together without being represented as the same accomplishment.

That record also makes alternative decisions easier to assess. Continuing unaffected work may preserve momentum. Holding an affected lot may avoid accumulating items that require later changes. Neither response is automatically correct; the decision depends on the contract, the unresolved condition, and the evidence available. A supplier's investment already spent is relevant context, but it cannot establish that a deliverable meets the agreed requirement.

Make the follow-on review useful to the next program

Before adopting the approach elsewhere, acquisition leaders should ask what actually reduced elapsed time. Was it reuse of the prior competition, earlier supplier investment, an existing government relationship, or a narrower deliverable? Which activities continued after award? A fair comparison accounts for those differences rather than attributing every gain to the contract label.

The same review should capture costs shifted outside the headline award: government integration work, assessment resources, support arrangements, and later changes where applicable. That is not an argument against Phase III. It is how a buyer determines which parts of an approach are transferable and what the next program must fund to repeat them.

For the next review, request two linked records: the basis for the follow-on authority and the plan for accepting and supporting the deliverables. The contracting lead owns the first; program, technical, and support leadership must make the second executable. Agreement on both gives an accelerated procurement a stronger foundation than either record alone.

The result to watch

Blackbeard offers a useful test of whether an existing follow-on authority can support meaningful industrial scale. Its significance will grow if the Navy receives accepted rounds on a credible schedule and can integrate and sustain them at the intended pace. If dates move, the review should distinguish manufacturing performance, technical changes, certification, and government decisions rather than assigning every outcome to Phase III.

The model becomes repeatable when the next program can understand both the time saved and the controls that made that time saving responsible. Fleet readiness reports will ultimately say more than the size of the announcement.

Sources and further reading

Spartan X's program execution, engineering, and logistics practices connect acquisition decisions to the integration and sustainment work that makes a production award useful to the fleet. That combined perspective is especially valuable when a faster contract brings delivery commitments forward.

Share this article
LinkedIn

BUILD WITH US

Ready to Solve Hard Problems?

Spartan X builds AI systems, autonomous platforms, and cybersecurity solutions for defense and national security.