Autonomous Ground Vehicles for Steep Terrain Wildfire Logistics Prize Challenge 2026

Autonomous Ground Vehicles for Steep Terrain Wildfire Logistics Prize Challenge 2026

If you work at the intersection of autonomy, fire science, and field operations, this was a concrete 2026 federal prize opportunity for teams that could move from idea to demonstrator quickly. The challenge asked participants to build and submit practical autonomous or semi-autonomous ground vehicle concepts that help wildland firefighters move equipment, supplies, and resources through steep terrain where traditional transport is difficult. It was run by Central Florida Tech Grove in partnership with the Naval Air Warfare Center Training Systems Division (NAWCTSD) and the Strategic Environmental Research and Development Program / Environmental Security Technology Certification Program (SERDP/ESTCP).

The application period is closed. The official host page does not announce a successor round, so this page is a historical reference for the completed 2026 cycle rather than an invitation to apply. It was not a traditional research grant with full cost proposals or long-cycle compliance burdens: it was a time-bound federal prize contest in which selected finalists demonstrated in front of judges. The strongest fit was for teams able to show a prototype with operational promise, not just an appealing concept.

Key details

The official page consistently gives the total as $85,100 and gives the first two awards as $40,000 and $25,000. Its wording for the third award is inconsistent: one summary says $20K, another says $20,100K, while the timeline and detailed prize section say $20,100. This listing preserves that source discrepancy for review instead of presenting the conflicting third-award wording as settled.

What this opportunity is (and is not)

This opportunity is a field-impact challenge designed around wildland fire readiness, not a standard lab-only R&D award.

What it is:

• A competition for practical systems that can operate safely in steep wildfire zones.
• A phase-based process with initial submission, semi-finalist filtering, and Demo Day.
• A prize model where up to three teams are financially rewarded.
• A pathway for teams to gain access to DoD and federal innovation stakeholders, including possible follow-on follow-through through OTAs, CRADAs, or related federal procurement mechanisms.

What it is not:

• It is not a multi-year research grant with overhead rates, indirect cost rates, or annual progress report cycles.
• It is not automatically available to everyone. Eligibility and federal participation rules are enforced by phase.
• It is not primarily aimed at publishing a broad white paper. Teams are evaluated on how solutions are built, demonstrated, and tied to operational criteria.

The host page explicitly describes the challenge as addressing the logistical burden on wildland crews in steep environments and explicitly asks for deployable prototypes that can carry significant payloads, operate over rough ground, and support a full operational shift.

Why this remains useful after the close

The 2026 cycle is complete, but the page remains useful as a concrete reference for teams planning work in wildfire logistics, ground robotics, and government prize competitions:

• The published requirements show the level of operational evidence expected for steep-terrain logistics rather than a concept-only pitch.
• The phase structure demonstrates how an initial video and presentation can lead to finalist deliverables and a field demonstration.
• The challenge connects fire suppression, DoD training, autonomous systems, and crew safety in one specific use case.
• The host lists possible follow-on mechanisms such as Other Transaction Agreements (OTAs) and Cooperative Research and Development Agreements (CRADAs), but those possibilities are not a promise of funding or a new solicitation.

There is no announced successor round on the official page. Teams should therefore use the requirements and completed timeline for benchmarking, not treat this archived listing as an open call.

Who this is strongest for

The completed cycle was strongest for:

1. Early-stage robotics teams with a tested mobile platform.
2. Groups combining autonomy/software capability with rugged hardware integration.
3. Research teams with wildfire domain understanding but enough engineering depth to produce a field-credible response.
4. Universities or labs that can support fast prototyping and video-based demonstration.
5. SMEs in sensing, payload handling, control, or unmanned systems.

The opportunity is intentionally broad in team composition but narrow in execution expectation. It does not require that every participant be a DoD contractor, but it does require credible proof of concept. For teams coming from pure software backgrounds, a meaningful route is to partner with mechanical or systems integration collaborators.

Eligibility and compliance constraints

The official rules set specific participation criteria for the completed cycle. They are useful for understanding who could have entered, but they do not reopen the application period:

• Participants can submit as individuals or teams.
• Participants may come from industry, academia, state/local government, or non-profit entities.
• Every individual participant must be at least 18 and a citizen of the United States or a U.S. ally.
• Federal employees and support-service contractors are generally excluded, with very limited exceptions.
• Federal funds cannot be used to support participation.

There were also legal and operational obligations in the terms framework:

• Participants must own or have rights to submitted content.
• Submissions must not violate third-party rights.
• Final scores and judging outcomes are binding, and disputes are typically not part of the competition process once adjudication happens.
• Because submissions can become federal records, FOIA considerations apply to submitted materials.
• Data rights and use expectations should be reviewed before submission.

The safest interpretation for teams is: if any team member is unsure about disclosure, sponsorship, export controls, internal IP ownership, or government record exposure, resolve this before finalizing demo materials.

How the completed application process worked

Applications are no longer being accepted. The official host page marks the application period closed and does not provide a current portal or successor deadline. For historical context, its phase timeline was:

• March 16, 2026: prize challenge release and application portal opening on USA.gov and the Tech Grove website.
• March 24, 2026 at 10:00 AM EDT: virtual information session.
• March 26, 2026: recording and additional materials made available through the challenge website platform.
• May 12, 2026 at 11:59 PM EDT: initial submission deadline for solution prototypes, required documents, and sample output.
• May 25, 2026 at 11:59 PM EDT: technical evaluation and selection of up to 10 semi-finalists.
• May 28, 2026: finalist notification and Demo Day submission instructions.
• June 12, 2026 at 11:59 PM Eastern Time: finalist deliverables due.
• June 24, 2026: USFS-led field demonstration and winner selection at the Blue Ridge Ranger District, Chattahoochee National Forest, Georgia, or a nearby alternative depending on weather.

The initial submission package required a link to a final video demonstration of the front and back end of the solution. The video had to be hosted on YouTube or another viewable link rather than supplied as a downloadable MP4. The presentation had to explain and justify the solution, summarize its capabilities and functions, show the percentage of technical requirements satisfied, identify possible barriers to implementation by SERDP, discuss potential expansions, and recommend next steps and further development needs.

The second phase asked selected finalists for a final video and final pitch presentation using the same core structure. The host page says those materials were submitted through the designated process provided to finalists by email. Because the cycle is closed, this page should not direct readers to invent a replacement portal or reuse an expired submission route.

What judges evaluate

Judging emphasis is visible in the structure of the challenge and technical requirements.

1. Operational functionality
   • Logistical payload handling (water, hose packs, pumps, tools, batteries, medical kits).
   • Minimum heavy-load behavior (800 lb payload floor in the published requirements).
   • Mobility on 25–35 degree slopes.
2. Safety and reliability
   • Stable behavior near active suppression operations.
   • Real-time awareness and hazard awareness.
   • Fail-safe behavior and remote override.
3. Rapid deployability
   • Setup by a two-person crew.
   • Minimal configuration complexity.
   • Planning factor for a 12–14 hour shift, or 6–8 hours with a credible hot-swap or recharge strategy.
4. Control and data
   • Teleoperation + semi/autonomous modes.
   • Replanning and communication-loss handling.
   • Interoperability with field coordination platforms.
5. Durability and environment readiness
   • Heat, smoke, ash, debris tolerance.
   • Repeatable operation over logs, slope, and uneven ground.
6. Fit with firefighter workflows
   • Minimal extra training requirement.
   • Real operational value rather than lab-only performance.

From experience reviewing similar federal challenge pages, teams often lose points by describing what a system can do in theory without anchoring every claim to operationally constrained behavior. The highest-quality teams provide explicit evidence snippets: photos from test runs, telemetry logs, failure-mode handling strategy, and limitations.

Common mistakes and how to avoid them

1. Submitting concept-only proposals

• Error: treating the challenge like an ideation pitch.
• Fix: submit proof-oriented content with clear demos and requirement mapping.

2. Ignoring payload and terrain constraints

• Error: promising generic off-road mobility only.
• Fix: explicitly prove operation with meaningful payload, slope range, and route complexity.

3. Missing “human-in-the-loop” controls

• Error: overemphasizing autonomy and under-specifying override and safety behavior.
• Fix: include remote override behavior and safe-mode response.

4. Weak implementation path

• Error: only stating technical novelty.
• Fix: include deployment plan, integration path, and barriers to SERDP/NAWCTSD adoption.

5. Submitting non-compliant files

• Error: using non-URL media or nonstandard formats.
• Fix: provide streaming-compatible links for video and straightforward presentation artifacts.

6. Underestimating terms and legal clauses

• Error: treating eligibility as just applicant profile.
• Fix: account for federal participation clauses, representation requirements, and data use rights.

Preparation lessons from the completed cycle

A practical preparation plan for a challenge with these requirements would have three workstreams:

• Technical core: finalize one use-case scenario and test route.

  • Choose one primary mission profile: logistics resupply, CASEVAC-lite payload movement, line support, or hose/pump movement.
  • Generate stable baseline data for one mission profile rather than fragmented demos across multiple profiles.

• Evidence and communication core:

  • Prepare a concise video with setup, operation, limitations, and control mode behavior.
  • Provide a matrix showing each technical requirement (terrain, payload, deployment time, safety logic) and your fulfillment level.
  • Include risk register with mitigation (communication drop, thermal proximity, retrieval).

• Review and compliance core:

  • Confirm all team members meet eligibility, especially citizenship and federal participation restrictions.
  • Remove any federally funded support from the project budget if applicable.
  • Validate no prohibited third-party IP conflict exists in software/model assets.

Teams usually do best when they submit a short, coherent narrative rather than too many technical branches.

Frequently asked questions

Is this a grant or a prize?

It is a prize challenge. Funding is awarded as competition cash prizes, not a broad research grant.

Can I use federal funds in my development?

The eligibility statement says participants may not use federal funds to support participation.

Can state or local actors participate?

Yes, the listed eligible categories include state/local government participants, as well as industry, academia, and non-profits.

Is this still open?

No. The official host page says “Application Period Closed.” The initial submission deadline was May 12, 2026, finalist deliverables were due June 12, 2026, and Demo Day and winner selection were scheduled for June 24, 2026. The host page does not announce a next round.

Are teams required to win in one step?

No. The challenge is phased. Initial submissions are judged first; finalists can continue into Demo Day.

Is there any chance of follow-on collaboration after prize award?

The host page explicitly notes opportunities for exposure and potential follow-on mechanisms such as OTA/CRADA pathways.

Risk considerations for teams studying the completed cycle

This was a high-velocity competition. The opportunity was compelling but operationally demanding.

• If your team cannot field a stable field demo quickly, focus on a narrow mission slice instead of overbuilding.
• If your system needs perfect autonomy across all conditions, scale expectations downward: include clear fallback and teleoperation behavior.
• If your team lacks public safety and firefighter workflow familiarity, partner with domain experts early.
• If your legal/IP boundaries are unclear, pause before submission and fix ownership terms first.

The central failure pattern in fast challenges is often not technical quality, but submission execution. A good robot with weak packaging is often scored below a more modest but clearly demonstrated system.

Official links and next steps

• Official host and rules page: https://centralfloridatechgrove.org/autonomous-ground-vehicles-prize-challenge/
• Challenge format: prize competition; the application period is closed and the host page does not announce a successor round.

For teams that already have a workable ground-vehicle concept, this challenge is strongest as a historical validation event. Its requirements remain a useful benchmark for payload capacity, slope mobility, deployment, safety, communications, and shift endurance, but readers should not interpret this archived page as an active funding opportunity.