DARPA's Autonomous Wildfire Response SBIR Closes Tomorrow: What the ALIAS Pivot Tells Us About Dual-Use Funding

DARPA's Strategic Technology Office published two SBIR topics on April 13, 2026 that close to proposals tomorrow, May 13. One is HR0011SB20254-15, the Unbiased Behavioral Discovery Platforms topic from the Biological Technologies Office. The other is HR0011SB20254XL-01 — ALIAS Missionized Autonomy for Emergency Services — and it is the topic that is going to be discussed in policy circles for the next year, regardless of how the awards land.

The ALIAS topic asks for "development and demonstration of missionized autonomy for emergency services, initially focusing on autonomous wildfire response." On its face, that is unremarkable; DARPA has been funding autonomous flight systems for two decades. What is unusual is the combination of the SBIR XL designation, the explicit civilian use case, and the Tactical Technology Office home — a combination that tells small businesses considering federal autonomy funding more about the next eighteen months than any policy statement out of OMB or the White House Office of Science and Technology Policy.

For background on the broader SBIR landscape in 2026, including the new $30 million Strategic Breakthrough Awards and the foreign-risk screening regime, see our reauthorization analysis. ALIAS sits inside that statutory framework, but it is testing how far the framework can stretch toward civilian missions.

What ALIAS is actually procuring

The ALIAS program — Aircrew Labor In-Cockpit Automation System — is one of DARPA's longest-running tactical autonomy programs. Originally framed as a way to reduce crew workload in military rotorcraft and fixed-wing aircraft, it has matured into a software-defined autonomy stack that can be ported onto certified airframes. That porting work is the technical substrate for the new SBIR topic.

The May 13 close is for an "XL" designation, which signals a larger-scope SBIR award than the standard Phase I size. DARPA does not publish the specific dollar ceiling in the topic abstract, but the XL framing has historically supported Phase I efforts up to several million dollars rather than the standard sub-$1M Phase I norm. Award size matters here because the topic is not asking for paper studies — it is asking for "development and demonstration," which implies hardware integration with actual airborne platforms.

The technical scope identified in the topic is autonomous wildfire response. That is a specific operational concept that touches several distinct capability areas. The autonomy stack has to handle aerial firefighting platform integration — air tankers, helicopter water drops, and increasingly unmanned aerial surveillance — in airspace that is unusually congested with civilian aircraft, ground-based personnel, and rapidly shifting weather conditions. It has to interoperate with the U.S. Forest Service incident command structure, which is the dominant operational customer for any aerial firefighting capability. And it has to certify against an FAA framework that has never previously authorized autonomous tactical flight in civilian emergency response.

This is, in short, a procurement that combines defense-grade autonomy with civilian aviation safety with interagency operational coordination. There is no single agency in the federal government that owns all three problems, which is part of why DARPA is the one funding the SBIR.

Why the topic is in the Tactical Technology Office

The institutional location of the topic — DARPA's Tactical Technology Office, not the Defense Innovation Unit or any of the FEMA, USFS, or Cal Fire research programs that fund wildfire technology — is the signal that should command attention.

There is a stated rationale and an unstated one. The stated rationale is that wildfire response shares a substantial autonomy stack with military tactical aviation, and DARPA can fund the autonomy work more credibly than civilian agencies can. That is true. Cal Fire's research budget cannot sustain a multi-million-dollar autonomy demonstration; the U.S. Forest Service's research and development arm has historically been oriented toward fire behavior modeling rather than aircraft autonomy; and FEMA does not fund this kind of capability work at all.

The unstated rationale is more interesting. DARPA has been increasingly willing — for at least three years — to fund what its program managers describe internally as "dual-use" capability development where the civilian application is the front door and the defense application is the eventual customer. Autonomous wildfire response is a perfect fit for that framing. The autonomy stack that can fly an air tanker into a fire incident at night with degraded communications is, with relatively modest adaptation, the autonomy stack that can fly a logistics platform into a contested environment. DARPA is buying the wildfire capability and getting the tactical capability adjacent to it.

Small businesses considering whether to submit should understand this framing. The topic is not a civilian-only opportunity in disguise; it is a defense capability development effort that has chosen a civilian initial mission for technical, political, and operational reasons. Proposals that read as if the wildfire mission is the only relevant outcome will not be competitive against proposals that articulate the broader autonomy roadmap.

The interagency dimension

Wildfire response in the United States is run through a tangle of federal, state, tribal, and local authorities that no single funding line touches cleanly. Any autonomous capability funded through ALIAS will eventually need to integrate with:

• The National Interagency Fire Center in Boise, which coordinates federal aerial assets
• Cal Fire and other state agencies that run substantial aerial firefighting fleets
• The FAA's certification framework for autonomous flight in the National Airspace System
• The U.S. Forest Service incident command and air operations branches
• Tribal land management offices in fire-prone regions

DARPA does not own any of these relationships. The agency is funding the technical capability with the expectation that operational adoption will happen through a separate pipeline — likely involving the Defense Innovation Unit, the National Guard's Modular Airborne Fire Fighting System, and direct procurement contracts with state firefighting agencies. Applicants who can credibly map their proposed work to one or more of these adoption pathways will have a meaningful advantage in DARPA's evaluation. Applicants who treat ALIAS as a standalone R&D opportunity will likely lose to teams that frame it as the front end of a multi-pathway commercialization plan.

This is the operational reality that distinguishes successful DARPA SBIR performers from unsuccessful ones across every topic area. DARPA program managers evaluate proposals as much on transition strategy as on technical merit, and the transition strategy for a wildfire autonomy capability requires naming the customer in a way that the agency can verify.

What the May 13 deadline tells us about dual-use procurement

The most important policy signal in the ALIAS topic is the deadline itself.

DARPA pre-released the topic on April 13, 2026, and is closing it on May 13 — a one-month response window. That is short for any SBIR topic and extremely short for a topic that contemplates hardware integration and demonstration. The compressed timeline is consistent with two interpretations.

The first is that DARPA already knows which performers are competitive and is using the topic to formalize a pipeline of work the agency has been developing through other mechanisms. This is a common pattern at DARPA. The SBIR mechanism in these cases is less a competitive open call and more a procurement formalization for performers who have been engaged through prior contracts, broad agency announcements, or program-specific industry days. Applicants who have not previously engaged with DARPA's ALIAS program leadership are competing against performers who have been in conversation with the agency for months.

The second interpretation, not exclusive of the first, is that DARPA is signaling urgency about the wildfire mission specifically. The 2026 fire season in the western United States is forecast — by the National Interagency Fire Center's preliminary outlook — to be among the most severe on record. A capability demonstration that lands inside the 2026 fire season has substantially more political and operational value than one that lands in 2027. The one-month topic window is consistent with an agency posture of "we need this in the field this year, not next."

Either interpretation suggests that the applicants who succeed will be those who already have the technical foundation in place. A team that needs to develop the autonomy stack from scratch under a Phase I award will not deliver inside the operational window DARPA is implicitly signaling. A team that has an existing autonomy product and is using ALIAS funding to harden it for emergency services use is the kind of performer this topic is designed to fund.

What to do today

For small businesses that have an autonomy capability and have not yet decided whether to submit by tomorrow's close, three concrete moves are worth making in the next twenty-four hours.

The first is to read the topic abstract against the firm's actual technical readiness. ALIAS is not a paper SBIR. If the firm cannot credibly claim Technology Readiness Level 5 or higher in the relevant autonomy capability, the proposal will be evaluated against teams that can, and the gap will be visible to DARPA reviewers.

The second is to identify and contact at least one operational user — Cal Fire air operations, a Forest Service incident commander, a Defense Innovation Unit program manager working on wildfire — who can supply a letter or memorandum of support. The transition strategy is the differentiator in DARPA SBIR evaluation, and the transition strategy is not credible without an identified customer.

The third is to decide whether the proposal is worth submitting at all. ALIAS is the kind of topic where a weak submission is worse than no submission — DARPA's program managers remember which firms submit unprepared proposals, and a name that lands on the wrong side of that ledger may have a harder time engaging the agency in the future. Firms that cannot credibly compete should focus on the June 3 closing topics in the same office, where the response window is longer and the competitive field will be less concentrated.

The broader policy implication of ALIAS is that the dual-use procurement pattern — defense agencies funding civilian-mission capabilities that share a technical stack with military needs — is going to continue expanding through 2026 and beyond. Small businesses that have organized themselves around either pure civilian grant funding or pure defense contracting will find themselves at a structural disadvantage relative to teams that can credibly operate across both. ALIAS is the most explicit current example of that pattern, but it is not going to be the last.