What NASA’s Public R&D Data Reveals About Itself
20,152 projects across 77 programs — but one program dominates
Which programs can you actually trust for technology readiness data?
STRG: 98.7% coverage — only 1.3% of projects missing TRL
MCO: 99.2% — newest program, best data discipline
FO: 93.8% — flight test focus drives TRL rigor
SBIR/STTR: 33.3% missing — ~4,085 projects with no TRL
GCD: 16.5% recorded as TRL-0 (NASA scale starts at 1)
GCD effective coverage: ~55% when TRL-0 excluded
What happened after the project ended? In most cases, TechPort doesn’t know.
174 SBIR projects at TRL 8-9 get “Closed Out” with no Transitioned/Infused record. Mature tech exits invisible.
Companies sell into commercial markets. No NASA “infusion” event triggers a record. Success = invisibility.
Projects complete at TRL 4-5 with zero terminal outcome. No Closed Out, no Transition. They simply vanish from view.
What does success look like when the system can’t see it?
TechPort’s own descriptions say commercial transition is happening — but the outcome fields record nothing.
Freedom Photonics is not an outlier — it’s the pattern. TechPort’s project descriptions and documents describe commercial transitions that the outcome fields never record. The database’s left hand doesn’t know what its right hand wrote.
The pipeline isn’t failing — it’s designed to end here
SBIR Phase II contracts are designed to end at TRL 5-6. Advancing to TRL 7+ requires a flight mission or NASA center integration — a different funding mechanism entirely.
Power technology (TX03): only 3.8% advance to TRL 8. Novel power architectures complete Phase II prototypes but find no missions to validate on. The power desert.
NIAC archives everything. GCD archives almost nothing.
Every completed NIAC project has Phase I/II reports (1-6 items each). This is where the technology substance lives.
FO projects from 2015-2020 have docs (15%). Post-2021 projects: zero documents in batch. Policy change or pipeline delay.
Who tracks what happened, and who doesn’t?
38 of 327 NIAC projects show Transitioned_To. Best per-project rate of any program. 5 projects (1.5%) show mission Infused_To.
Zero Transitioned/Infused for 430 projects. 95% of completed FO has no outcome at all. Yet FO tech landed on the Moon 3 times.
Specific examples found by an autonomous agent reading 20,000 projects
GCD project 183893: named “_TEST_REV A”, zero-day duration, no TRL, no contacts. Has 633 external views. Publicly visible.
Project 113005: VisSidus listed as “Daytona Beach, Hawaii.” Daytona Beach is in Florida.
PPR nuclear pulse rocket (158619): classified as “Solar Thermal Propulsion” by both human AND ML. Undetected across 3 projects over 10 years.
Project 155247 (FAME): description contains appended text from a completely different technology (SEADS, project 155248). Copy-paste error across project records.
NIAC project 13725 (PuFF nuclear propulsion) linked to FO project 91348 (ChargerSat-2 boiling experiment). Same university affiliation, completely unrelated tech.
35% of projects have no destination set. But 29.7% are empty strings (“”) and 5.2% are null — two different bugs in the same field. Downstream users get confused.
These aren’t cherry-picked. An autonomous agent found them in routine exploration.
AI agents are reading this data at scale
This briefing was produced by an autonomous AI agent that read 20,152 TechPort projects over 100 research sessions.
That agent found valuable patterns — but it also found gaps, errors, and missing stories. As AI systems increasingly consume public R&D databases to inform policy, investment, and technology scouting, the quality of that data determines the quality of those decisions.
The story being told about your program’s impact depends on what’s in TechPort. If outcomes aren’t recorded, they don’t exist to the outside world.
TechPort is ~80% complete for administrative tracking but 30-50% incomplete for impact and outcome tracking. Trust varies dramatically by program.
Cross-reference TechPort with USASpending, SBIR.gov, and public sources. The real impact story requires connecting dots across multiple databases.
↓ Scroll · ↑↓ Arrow keys · Space
click anywhere to begin