Navy SBIR/STTR FY26 Release 3: 12 BAA Topics, One Counter-UAS CSO, and a 28-Day Submission Window From June 24 to July 22 That Reshapes the Naval Innovation Pipeline

The Department of the Navy pre-released its FY26 Release 3 SBIR/STTR solicitation on June 3, 2026 — 12 Broad Agency Announcement topics and one Commercial Solutions Opening area of interest centered on counter-unmanned air systems. The technical-questions window closes June 23. The proposal submission window opens June 24 and closes July 22, 2026. Naval Air Systems Command and Naval Sea Systems Command co-host a Counter-UAS webinar on June 16. Phase I funding tops out at $315,000. The release lands in the middle of a remarkable June for DoD SBIR/STTR activity — DARPA's Defense Sciences Office and Biological Technologies Office both dropped topic packages in the same window, and Release 3 is the second BAA release the Navy has put into the FY26 calendar.

The structural news in this release isn't the 12 conventional BAA topics — it's the Counter-UAS CSO. Commercial Solutions Openings are a flexible acquisition vehicle the DoD developed to fund innovative commercial technology outside the Federal Acquisition Regulation's traditional contracting structures. The use of a CSO inside a SBIR/STTR release is unusual. It signals that the Navy wants to bring in commercial drone-defense technology fast — without the topic-specific scoping that defines the BAA path — and is willing to use a less conventional vehicle to do it.

For real-time coverage, see Granted News. For broader context on this month's DoD SBIR activity, see our coverage of DARPA DSO's SBIR XL drop and DARPA BTO's biotech and photonics topics.

The Counter-UAS CSO — Why This Vehicle Matters

The CSO for Counter-Unmanned Air Systems seeks technologies that "detect, track, identify, and neutralize hostile drones and drone swarms, with innovative AI, machine learning, sensor fusion, and non-kinetic defeat solutions to protect military forces, critical infrastructure, and operational assets." That sentence packs four distinct capability areas — detect, track, ID, defeat — and explicitly invites both kinetic and non-kinetic approaches, including the AI/ML-enabled solutions that have dominated the post-Ukraine counter-drone conversation.

The vehicle choice matters as much as the topic. Conventional SBIR Phase I contracts run on a fixed scope, fixed budget, fixed schedule. The CSO structure allows for variable scope, milestone-driven contracting, and direct alignment between technical performance and award value. For commercial drone-defense companies that already have funded R&D programs and don't need NSF-style seed capital, the CSO is the more attractive vehicle: it gets product-market fit work funded without forcing the company to re-pose its commercial roadmap as a Phase I research project.

The CSO comes alongside an open topic structure that means the Navy isn't dictating what specific technical approach matters. AI-driven sensor fusion is in scope. Acoustic detection is in scope. RF cueing is in scope. Directed-energy defeat is in scope. Kinetic intercepts using next-generation interceptors are in scope. Cyber and electronic warfare countermeasures against drone command links are in scope. The breadth signals that NAVAIR has not yet converged on a preferred technical architecture — it's casting the widest possible net at the same moment that the Russia-Ukraine war and Red Sea operations have made drone-swarm defense the single most urgent maritime force protection problem.

The June 16 webinar — co-hosted by NAVAIR and NAVSEA — is unusual for the same reason. NAVAIR owns naval aviation. NAVSEA owns ships. The joint hosting reflects the reality that maritime drone defense crosses both organizations' lanes: drones threaten aircraft carriers, escorts, and amphibious ships (NAVSEA's customers) but the kill chain often runs through fixed-wing and rotary aviation (NAVAIR's customers). The joint webinar is also a useful diagnostic for which platforms the Counter-UAS CSO is meant to protect: anything that floats and anything that flies.

The 12 BAA Topics — What the Navy Actually Wants This Cycle

The 12 conventional BAA topics span a recognizable Navy SBIR portfolio: adaptive sensor management, anomalous behavior detection, satellite imagery optimization, real-time zero-trust data for combat systems, and gun weapon systems modernization. Three observations on the topic structure.

One — the sensor-management and anomalous-behavior topics signal a continued shift toward edge AI on naval platforms. The Navy is procuring platforms (Aegis combat system upgrades, the Constellation-class frigate, Block V Virginia-class submarines) with substantially higher onboard compute than legacy platforms. Topic structures that ask small businesses to deliver AI/ML capability at the platform edge — rather than as cloud-dependent services — reflect the recognition that maritime warfare cannot assume reliable cloud connectivity. Anomalous-behavior detection in particular is a topic where commercial AI/ML capability is mature; the Navy's specific contribution is the operational data that lets commercial models be tuned to naval-specific patterns of life and threats.

Two — the satellite imagery optimization topic reflects the proliferation of commercial space-based ISR. A decade ago, Navy ISR was a closed government enterprise. Today, commercial constellations from Planet, BlackSky, Capella, ICEYE, and Umbra produce more ISR data than DoD analysts can consume. The topic structure suggests the Navy is looking for small businesses that can fuse, prioritize, and tip-and-cue across multiple commercial and government ISR sources in ways the legacy GEOINT enterprise can't.

Three — the real-time zero-trust data topic for combat systems is the structural sleeper. Zero-trust architecture has been a DoD policy priority since 2022, but the gap between policy and operational combat systems remains substantial. Aegis, SSDS, and other combat systems run on data fabrics designed for an earlier security model — trusted internal networks with perimeter defense. Retrofitting zero-trust into those systems without breaking real-time performance is a genuinely hard problem and one where small businesses with both cybersecurity and combat-systems experience can plausibly contribute. Expect this topic to attract submissions from the small set of companies — Hypori, Anduril's defense network business, smaller niche players — that have credibly demonstrated zero-trust performance in real-time mission-critical contexts.

Four — the gun weapon systems modernization topic is a reminder that not all Navy SBIR is about software and AI. Naval surface gunnery — the 5-inch Mk 45 mount, the 25mm and 30mm chain guns on small combatants — has been due for modernization for two decades. Topics in this area attract a smaller set of qualified bidders (companies with weapons-systems integration experience) and are more amenable to traditional Phase I research scopes. For companies in the precision-engineering, advanced-materials, or low-observable-coatings adjacencies, the gun systems topic is worth evaluating even if it sits outside the typical software-and-AI Navy SBIR center of gravity.

Eligibility, Funding, and the 28-Day Submission Window

Standard SBIR eligibility applies: U.S.-based for-profit small businesses with fewer than 500 employees and majority U.S. ownership. STTR variants require a research-institution partner with at least 30 percent of work performed at the partner. The reauthorization-era foreign ownership and influence due diligence applies — Navy has been particularly focused on Chinese investor presence on cap tables, given Navy's combat-systems data sensitivity.

Phase I funding tops out at $315,000. That's slightly above the FY25 cap and roughly $10K above the NSF Phase I ceiling. The 28-day submission window from June 24 to July 22 is tight for companies starting from scratch — most successful Navy SBIR submissions reflect months of pre-positioning conversations with topic sponsors and technical points of contact. The technical-questions cutoff on June 23 is the last moment to engage with the points of contact for clarification on scope. After June 23, the submission becomes a unilateral process: the proposal goes in, and evaluation runs without further contractor-government dialogue.

For Counter-UAS CSO submissions, the technical questions cutoff is less binding because CSO vehicles are inherently more flexible. But the underlying point holds: companies that engage with NAVAIR and NAVSEA technical points of contact before June 23 will have a substantial information advantage over companies that submit cold. The June 16 webinar is the obvious vector for that engagement.

How to Win This Cycle — Structural Advice

Three structural recommendations for companies considering Navy Release 3 submissions.

One — pick the right vehicle. For commercial Counter-UAS technology with funded R&D and a near-term product roadmap, the CSO is the right vehicle. For genuine research-stage technology with TRL 3–5 maturity and an exploratory commercial thesis, the BAA path is more appropriate. Submitting Counter-UAS technology under a BAA topic when the CSO is available is suboptimal because BAA topics impose more rigid scope constraints; submitting research-stage technology under the CSO when a relevant BAA topic exists is suboptimal because the CSO is structured for higher-TRL capability buys.

Two — match the topic sponsor. Navy SBIR topics are sponsored by specific NAVAIR, NAVSEA, NAVWAR, or other commands. The sponsor identity matters because the sponsor sets the evaluation criteria and steers the transition to Phase II and Phase III. A topic sponsored by NAVAIR PMA-265 (F/A-18 program office) has different downstream commercialization paths than a topic sponsored by NAVSEA PEO IWS (Integrated Warfare Systems). Companies should research the sponsor's program priorities and recent contracting activity to assess the realistic commercialization pathway before committing proposal effort.

Three — pre-position for Phase II. Navy SBIR Phase II is competitive and selective. Phase I winners that don't make a credible case for Phase II during Phase I execution rarely advance. The pre-positioning work — building program-office relationships, integrating with relevant test events, demonstrating capability against operationally relevant scenarios — happens during the Phase I performance period, not after. Companies that view Phase I as a closed engagement and Phase II as a separate competition tend to wash out at the Phase II transition. Companies that treat Phase I as the first eight months of a 24–36 month sales cycle convert at substantially higher rates.

What This Means Against the Broader DoD SBIR Environment

June 2026 has been one of the most active months in recent DoD SBIR history. DARPA's Defense Sciences Office and Biological Technologies Office dropped multiple topic packages with overlapping July deadlines. DOT opened its FY26 SBIR Phase I. The Department of Education's IES has feasibility deadlines on June 29. The Department of the Navy's Release 3 lands in the middle of that activity. The compression is real and the practical consequence for small businesses is that proposal teams are bottlenecked. Companies pursuing multiple DoD opportunities in this cycle should prioritize ruthlessly — there is not enough proposal capacity in most small firms to credibly compete on more than two or three opportunities in the June 24–July 22 window.

For Counter-UAS companies in particular, the Navy CSO is the marquee opportunity of the cycle. It's open-topic. It uses a flexible vehicle. It addresses the most urgent operational capability gap in the Navy's portfolio. And it lands at the moment when commercial counter-drone technology has matured enough to be operationally relevant. Companies that have been building toward Navy engagement should view the July 22 deadline as a forcing function — and the June 16 webinar as the moment to convert pre-positioning work into a concrete submission strategy.