Updated November 2, 2026. Independent procurement analysis by UAVPackage.com. This is not a government solicitation page or an endorsement of any bidder.
The U.S. Navy’s October 30, 2026 TRUAS Increment II Cargo UAS Industry Demonstration is a timely test of what a complete, expeditionary cargo-drone package must deliver: not just payload and range, but fuel logistics, autonomous operations, transportability, cybersecurity, recovery and field support. The Navy is requesting industry applications for a demonstration in Huntsville, Alabama, January 25–February 5, 2027. The response deadline is November 30, 2026, at 11:59 p.m. Eastern. An invitation to demonstrate is not a procurement award, and the Navy may award one or more subsequent prototype agreements—or none. See the official SAM.gov notice, NAWCAD-SN-26-TRUASII and the Naval Aviation Systems Consortium (NASC) project page before acting.
Key dates and procurement status
| Milestone | Date / significance |
|---|---|
| Official special notice published | October 30, 2026; notice NAWCAD-SN-26-TRUASII |
| Technical questions deadline | November 13, 2026 |
| Industry application deadline | November 30, 2026, 11:59 p.m. Eastern |
| Participant selections expected | By December 18, 2026 |
| Flight demonstration | January 25–February 5, 2027, Huntsville, Alabama |
| Potential subsequent agreement | Other Transaction (OT) prototype agreement under 10 U.S.C. § 4022; no award guaranteed |
The agency asks for a 3–5-page technical white paper and a completed questionnaire. The official notice says applicants do not need NASC membership or pay a fee merely to apply or demonstrate. Membership may be required later for an OT agreement. Download the current questionnaire, announcement and evaluation rubric from the NASC project page; do not substitute a third-party summary for those documents. Applications and technical questions use the contact instructions in the official announcement. Dates and requirements can change if the government amends the notice.
What the flight profile is designed to reveal
Reporting on the demonstration announcement describes two core payload-and-range profiles. Each is more demanding than a manufacturer’s brochure range figure because it requires a complete mission with the specified load and a return leg without refueling.
| Reported demonstration profile | What a supplier should document |
|---|---|
| Flight 1: 100 lb cargo carried 40 nautical miles outbound, dropped or delivered, then 40 nautical miles returned empty | All-up takeoff mass, actual route distance, fuel consumed, reserve margin, payload retention/release evidence and full flight log |
| Flight 2: at least 150 lb cargo carried 10 nautical miles outbound, then return empty | Takeoff and landing configuration, fuel margin, payload center of gravity and repeatable delivery procedure |
| At least 50-knot transit speed, at or below 1,000 ft AGL | Evidence of the specified flight envelope under test conditions |
| Launch/recovery without catapult, net or arresting cable | Equipment footprint, field setup time and launch/recovery support requirements |
| Heavy fuel (for example JP-5, JP-8 or diesel) or a qualifying hybrid arrangement | Fuel compatibility, refuel time, energy accounting, safety controls and field consumables |
| Preference for maximum gross takeoff weight up to 350 lb | Actual configuration-specific gross-weight documentation, distinguishing preferences from hard thresholds |
Important: These profiles are summarized from reporting and public descriptions of the announcement, not a completed review of every official attachment. The government’s final application rubric and threshold/objective tables control. An aircraft that meets a single advertised payload figure does not necessarily satisfy the entire demonstration profile. DRONELIFE’s November 2 report and the October 30 notice summary provide useful orientation, but applicants should verify each threshold against the actual files.
A complete cargo UAV package is more than an aircraft
A successful logistics system includes the air vehicle, propulsion, cargo interface, ground equipment, control software, navigation, communications, spares and trained operators. The full system must function as an integrated service in the environment for which it is proposed. For a general starting point, see UAVPackage.com’s complete UAV system RFQ template and commercial drone system readiness checklist.
1. Payload and mission assurance
Request a payload statement by mission profile rather than a maximum-lift claim in isolation. Include the usable cargo volume, attachment and restraint requirements, allowable center-of-gravity envelope, cargo protection, delivery mechanism, return load, and what happens if a delivery cannot be completed. Separate demonstrated performance from simulations, targets and future capabilities. Ask for traceable test logs under representative conditions.
2. Fuel, power and turnaround
A heavy-fuel or hybrid powerplant raises questions that a battery-only drone procurement may not. Determine which fuels are actually qualified, whether field refueling needs special gear, the required fuel quality and storage procedures, expected operator workload, and turnaround after a representative mission. Compare transport burden and maintenance overhead rather than assuming that a fuel-burning airframe automatically has lower operating cost.
3. Autonomy and ground-control workload
The government’s interest in autonomous resupply makes human-system integration central. Demand evidence for preflight checks, mission release, geofencing, lost-link handling, contingency landings, manual intervention policy and flight-record retrieval. Any claim that one supervisor can manage multiple vehicles should be bounded by specific operating conditions, software version and approval basis. Natural-language interfaces and GPS-degraded navigation may be evaluated, but marketing demos are not substitutes for documented operational assurance.
4. Fieldability and support
A practical package also specifies how long setup and postflight recovery take, which tools are needed, how spares are packaged, what fails replaceable in the field, and how software updates are verified. Ask for training hours, staffing model, technical manuals, change-control process and a support commitment. A compact aircraft that relies on a large unpriced ground crew is not a compact logistics solution.
5. Security and regulatory scope
Proposals should identify supply-chain provenance, applicable domestic sourcing restrictions, software-bill-of-materials availability, encrypted command links, vulnerability disclosure process and data-handling arrangements. Do not assume eligibility solely because assembly occurs in the United States. For domestic civilian use, separately assess FAA aircraft and operating authorization, airspace, site approval, communications rules and any applicable Part 135 requirements. A Navy technology demonstration does not by itself confer commercial operating authority. See the site’s FAA/BVLOS regulation guide and FCC connectivity decision analysis.
Twelve questions to include in a cargo-drone supplier RFQ
- Which exact aircraft and software baseline will be demonstrated, and which claims are independently flight-tested?
- What are payload, route, return-leg and fuel-reserve results for the specified 100 lb and 150 lb profiles?
- How do payload mass, cargo dimensions, center of gravity, winds and temperature affect the mission envelope?
- Which fuel types are qualified, and which are merely planned or theoretically compatible?
- What are the deployment footprint, total packed transport mass, setup time, refuel time and crew requirements?
- How are payload loading, retention, release and failed-handoff recovery verified?
- How does the system document mission approval, autonomous behavior, lost-link events and emergency intervention?
- What command-link architecture, spectrum rights and cybersecurity evidence support the operating concept?
- What validation exists for GNSS-degraded operations, and what limitations remain?
- How are airworthiness, safety evidence and relevant regulatory approvals documented for each proposed mission?
- What spares, training, maintenance intervals, repair turnaround and software support are included in the price?
- Which requirements are achieved today, which are objectives, and which depend on a future certification, subcontractor or redesign?
Eight acceptance tests worth requesting
A buyer or evaluation team can use a repeatable evidence package—not just a video highlight reel—to compare suppliers. The following are editorial procurement recommendations, not the Navy’s official scoring rubric.
| Test | Evidence to retain |
|---|---|
| Configuration and payload audit | Aircraft/ground equipment serials, software build, calibrated cargo mass, weight-and-balance report |
| Route and endurance replay | Waypoints or approved route summary, timestamped flight record, fuel/energy consumption, reserve margin |
| Cargo handoff reliability | Delivery-completion record, exception cases, load-condition notes |
| Ground setup and turnaround | Time-stamped procedure, personnel count, equipment manifest, refueling and inspection logs |
| Supervision and contingency exercise | Operator actions, lost-link response, abort and recovery state records |
| Navigation and C2 resilience | Approved test plan, boundary conditions, event logs and documented limitations |
| Maintenance and software audit | Maintenance history, replacement time, version control and update rollback evidence |
| Cost and sustainment validation | Aircraft, ground equipment, spares, training, fuel, insurance, facilities and support cost assumptions |
A vendor-neutral 100-point comparison framework
The following weighted model is UAVPackage.com’s suggested buyer worksheet, not an interpretation of NASC’s application rubric. Score each category only against evidence for the intended mission.
| Evaluation dimension | Suggested weight |
|---|---|
| Payload/range performance and reserve evidence | 25 |
| Autonomous safety, contingencies and logs | 20 |
| Fuel/energy system and turnaround | 15 |
| Field deployment and maintainability | 15 |
| Security, compliance and provenance | 15 |
| Commercial support, training and total ownership cost | 10 |
| Total | 100 |
A supplier should also identify any pass/fail gates before scoring: unproven threshold capabilities, absence of required authorization or applicable sourcing compliance may make a high numerical score irrelevant. Use the government’s actual evaluation rubric for this demonstration and this independent framework only for broader procurement comparison.
Why this matters beyond defense logistics
The announcement signals demand for integrated autonomous cargo systems with verifiable logistics performance. Some of the same questions apply to industrial parts delivery, energy-site resupply, remote healthcare routes and offshore logistics: how a vehicle is loaded, dispatched, tracked, recovered, refueled and maintained. The civil approval regime, safety case, insurance and economics can differ sharply from military applications. Treat cross-market use as an opportunity to evaluate, not an existing certification.
The market already includes materially different approaches. Elroy Air reported an August 18, 2026, $46 million U.S. Army development contract for its hybrid-electric Chaparral, while Near Earth Autonomy announced a distinct Marine Corps MARV-EL logistics-aircraft prototype program in April. For adjacent coverage, see our Elroy Air financing analysis and heavy-cargo drone perception update. These are separate programs; neither announcement establishes that a company will apply for, qualify for, or win the TRUAS Increment II demonstration. This is a useful comparison for organizations mapping the commercial drone-delivery ecosystem rather than treating all cargo UAVs as interchangeable.
What to watch next
The nearest action is the November 13 technical-question cutoff, followed by the November 30 submission deadline. After December 18, verify whether participants have been selected and whether the Navy has changed the event terms. After the January–February demonstration, report tested capabilities, independently verifiable results and any subsequent awards separately. Until an OT agreement is actually announced, label this a demonstration opportunity, not a contract win.
Official and corroborating references
- SAM.gov special notice NAWCAD-SN-26-TRUASII, published October 30, 2026
- NASC project page: documents, application rubric, questionnaire and updates
- Public-text capture of the official announcement (retrieved November 1, 2026)
- DRONELIFE, November 2, 2026: Navy DRPM RAS Seeks Cargo Drones for Marine Corps
Editorial note: No vendor paid for inclusion, and named companies are not represented as entrants. Requirements and dates may change; always use the official notice and attachments for an application.
