Unmanned aircraft are unusually well matched to the SBIR and STTR programs, for one blunt reason: the federal government is both the largest research funder and, for many drone companies, the first serious customer. That changes how a proposal should be written.
Which agencies fund UAS work
Defense components dominate. The services run open topics as well as narrowly specified ones, and their interest spans airframes, autonomy, counter-UAS, communications in contested environments, and logistics delivery. NASA funds aeronautics research and airspace integration. The Department of Homeland Security funds inspection, border and first-responder applications. The Department of Transportation funds airspace and infrastructure work, and USDA funds agricultural sensing and application.
What they reward is not the same. Defense reviewers want a named operational problem and an end user who has asked for this. NSF wants the underlying science to be novel. A civil-agency reviewer wants a deployment story inside existing rules. Sorting this out early is the point of choosing the right agency.
What counts as technical risk in this field
Integrating a commercial flight controller, a commercial airframe and an off-the-shelf camera is systems engineering, and it does not win awards. The credible risks in drone work sit in a few places: navigation without satellite positioning, detect-and-avoid performance in cluttered or degraded conditions, autonomy that holds up when the link drops, endurance from a new power system, and payload precision under vibration and airflow that no ground rig reproduces.
State the metric. Position error in meters under jamming, detection probability at a stated range and target size, endurance in minutes at a stated payload mass — with the current state of the art next to it, and the threshold at which you would call the project a failure. Reviewers who fly things are unmoved by adjectives. Test planning is a large part of the credibility here; our piece on building a flight test plan covers what a defensible plan contains.
The FAA is the hurdle that shapes the schedule
Almost every commercially interesting drone concept runs into airspace rules before it runs into physics. Flight beyond visual line of sight, flight over people, and night operations each carry their own requirements, and the approval path is a schedule item measured in months. A proposal that assumes routine BVLOS operations without saying how it will get there reads as naive.
Build the compliance work into the project rather than bolting it on. Remote ID is a manufacturing obligation, not a software afterthought. If your Phase II demonstration needs a waiver or a test-site arrangement, name it in the plan and give it a realistic duration, because reviewers who work in this domain will check.
From award to product
The honest path runs from a Phase I feasibility study to a Phase II flight-demonstrated prototype, then to either a government program of record or a commercial fleet operator — and production is its own project, not a continuation. Export control is worth checking early, because capable aircraft can become dual-use. The engineering underneath all of it is spread across our drone development library.
Projects House designs and builds UAS hardware for teams working through funded research programs. Tell us what you are flying via our contact form.