FO Infusion Archetypes: How Flight-Tested Technologies Actually Transfer¶

Last updated: 2026-04-07 (Session 46)
Evidence base: 430 projects triaged (100% coverage) across Sessions 1–46

Overview¶

After investigating all 430 FO projects across 30 sessions, 16 distinct archetypes have emerged for how FO-tested technologies transfer downstream. These are not taxonomy categories — they are causal mechanisms. Two projects in the same archetype will have similar downstream success rates; two projects in different archetypes may have similar surface characteristics but very different trajectories.

Base rate summary (56 industry-led completed): ~25–33% have confirmed positive downstream outcomes. For academia/FFRDC, the base rate is different — fewer commercial outcomes but a higher rate of mission infusion and publication impact.

The 16 Archetypes¶

1. Middle-Step Bridge¶

Definition: FO provides a critical validation step between funded lab work (often SBIR) and a NASA mission application. The technology was already proven in lab; it needed one in-flight test to justify mission inclusion.

Mechanism: Lab TRL 4 → FO flight → TRL 6 → mission inclusion proposal → mission contract

Examples: - Controlled Dynamics / CDI [91391] (TRL 6→9): VIP vibration isolation between SBIR lab work and DSOC/Psyche mission instruments - Made in Space / AMF [91394] (TRL 4→9): FDM printing between SBIR work and ISS AMF deployment - NASA NDL / Psionic [91351]: FO validated altitude/velocity lidar; licensed to Psionic; flew IM-1

Success rate: High (~80%). If the lab work is solid and a mission application exists, FO typically provides the needed validation.

Warning sign: When there is no identified mission application at the start of FO, the bridge has no destination.

2. Government Tech → Commercial License → Mission¶

Definition: A NASA center or FFRDC develops technology, uses FO to validate it, licenses to a commercial company, which then deploys it on a mission.

Mechanism: NASA center R&D → FO TRL maturation → license/spinoff → commercial company deploys on paid mission

Examples: - NASA LaRC NDL → Psionic → IM-1: NDL validated at TRL 6 via FO 2013–2019; licensed to Psionic; flew on IM-1 February 2024 — saved the mission when primary rangefinder failed - JPL G-FOLD/FOALS → Mars 2020 [12272, 91418]: G-FOLD + TRN/LVS validated on Masten Xombie 2013–2014; incorporated into Perseverance LVS; landed within 5m of target February 2021

Success rate: Very high when the technology reaches TRL 6+. The critical factors are: (a) NASA mission exists that needs the capability, and (b) the technology is distinctive (not substitutable with commercial alternatives).

Best-in-class note: NDL is the strongest causal FO argument in the portfolio (saved IM-1). G-FOLD/FOALS is the highest-impact planetary mission infusion (Mars 2020).

3. Validation Service (Large Mature Company)¶

Definition: A mature company with an existing product uses FO to validate one specific component or configuration, then deploys that component in their existing commercial product line or mission.

Mechanism: Company already has TRL 7+ system → FO validates specific subsystem → subsystem incorporated into flight product

Examples: - SpaceX Dragon V2 PMD [94146]: SpaceX tested propellant management device; Crew Dragon went on to 12+ crewed ISS missions - World View Enterprises [89368]: Balloon altitude control validated; Stratollite became commercial product - Teledyne Energy / HEPS [106653]: Hydrogen fuel cell flew on New Shepard; Artemis power path confirmed - Airborne Systems [91422]: FO extended JPADS to 50,000 ft; Orion parachute provider ($13.57M NASA LaRC)

Success rate: High (~85%). Companies this mature don't fail to deploy; FO's role is enabling a specific product extension, not creating a company. The outcome is real but FO's causal contribution is smaller (the company would likely have found another path).

Revenue model: Company's revenue comes from the existing product/contract base; FO enables one extension of that base.

4. Startup Formation / Scale-Up¶

Definition: FO funds the core technical validation that allows a new company to form or scale, leading to follow-on commercial contracts or acquisition.

Mechanism: Early-stage company + core technology → FO validation → company credibility → commercial contracts or acquisition

Examples: - Ventions LLC → Astra Space [94198]: FO funded electric pump-fed propulsion; Astra was formed around this tech, reached orbit 2022 - Solstar Space Company [91329]: Wi-Fi on suborbital platforms validated; Lunar Gateway HALO Wi-Fi contract - Tyvak → Terran Orbital → Lockheed [94197, 106591]: Micro-avionics platform; Lockheed Martin acquired Terran Orbital October 2024 ($48.7M+)

Success rate: Moderate (~50%). The technology needs to be genuinely defensible and the company needs business development capability. When it works, returns are large (acquisition, major contracts). When it doesn't, the company stagnates at pre-revenue.

5. Sequential FFRDC Investment → Mission¶

Definition: An FFRDC or non-profit R&D institution runs multiple sequential FO projects over many years, building up a technology capability that ultimately lands on a NASA or commercial mission.

Mechanism: FFRDC FO project 1 → TRL N → FFRDC FO project 2 → TRL N+2 → mission inclusion

Examples: - Draper GENIE → TRN → DMEN → CP-12 [12186, 106585, 106613]: 14-year arc; $56.93M CP-12 CLPS contract - JHU/APL VACNT → RAVAN CubeSat [91344]: FO flight → TRL 7 → RAVAN CubeSat launched 2016 - Space Environment Technologies ARMAS [89360, 106715]: Two FO projects → ARMAS FM11 on IM-2 Athena → Moon March 2025

Success rate: High (~70%) when the institution has a specific mission application in view. The risk is diffusion across too many FO projects without a mission to pull them forward.

Note: Draper is unusual — it is the CP-12 prime contractor, not just a technology developer. This blurs the FFRDC/industry distinction in a way that no other FO institution has achieved.

6. FFRDC Data Gap Closure¶

Definition: An FFRDC uses FO to measure a specific physical phenomenon in the space environment that cannot be replicated in ground labs, producing data that closes a documented gap for a future NASA mission.

Mechanism: Physics question without reduced-gravity data → FO flight → data acquired → analysis/publication → mission design requirement closed

Examples: - The Aerospace Corporation / cryogenic pressurization [106642]: 19 parabolic flight cases for helium subsurface pressurization → npj Microgravity (Nature) July 2025; Artemis propellant management data gap closed - Mudawar Thermal Systems / cryogenic pool boiling [184140]: 1-month FO → STTR Phase III $366.6K 7 months later - JHU/APL VACNT / RAVAN [91344]: In-space environment test of VACNT absorbers → RAVAN CubeSat - JPL G-FOLD [12272]: Can real-time divert guidance work on a free-flying vehicle? → Mars 2020 LVS - Sandia Balloon Aeroseismometer [106697]: Can balloon-borne infrasound sensors determine signal direction? → JASA 2022 + GRL 2023 "Floatilla" + Nature Comms Earth & Env 2025 (subsurface inversion from balloon data). Venus seismology application: if Venus balloon mission flies, this FO data is foundational. Cross-institutional team: Sandia + JPL + SwRI.

Success rate: Very high (~90%) for generating knowledge output. Commercial revenue: zero (FFRDC constraint). Mission relevance: high when the data gap is genuinely on the critical path.

Speed of return: Unusually fast — Mudawar Phase III took 7 months; Giner Phase III took 3 months. When NASA program managers are waiting for a specific data point to justify next-phase funding, FO data triggers rapid award.

7. Acquisition Target¶

Definition: FO validates a technology that makes a company an attractive acquisition target. The acquirer (large prime or strategic investor) purchases the company after the FO validation provides proof of performance.

Mechanism: Company + FO-validated technology → acquisition offer → exit

Examples: - Made in Space → Redwire [91394, 155254]: ISS AMF (FO validated) → Redwire acquisition 2020; MSTIC FO → NG-20 ISS deployment - Tyvak → Terran Orbital → Lockheed Martin [94197, 106591]: Micro-avionics FO validated → Terran Orbital IPO → Lockheed acquisition October 2024 - Near Space Corporation → Aerostar [12460, 106710]: ADS-B balloon platform FO validated → Aerostar acquisition March 2024 - Masten Space Systems → Astrobotic [94201]: Bankruptcy acquisition ($4.5M) — tech absorbed, company dissolved (negative archetype variant) - TMT → Phantom Space [12187, 93857]: Orbital data center pivot; Phantom Space acquired April 2026 - World View → Ondas Holdings [89368]: Stratollite ISR platform; Ondas acquired April 1, 2026 (~$7.3M cash + 12.8M shares); Palantir AI-ISR collaboration - Nexolve → Applied Aerospace [106590]: LISA-T deployable structures + advanced polymer expertise; Applied Aerospace acquired March 10, 2025; PTD-4 Triumph flew Aug 2024 (partial deployment anomaly); $19M+ NASA tracked

Note: Seven acquisitions is unusually high — the most common exit path for FO-backed companies, ahead of IPO (only NanoRacks/Voyager at $3.8B). Acquisition appears to be the dominant positive exit mechanism. The FO validation creates tangible proof-of-performance that de-risks acquisition due diligence. The acquirers span the spectrum: strategic primes (Lockheed, Boeing/Aurora), roll-up platforms (Redwire, Ondas, Phantom Space), competitors (Astrobotic/Masten), and aerospace specialists (Applied Aerospace, Aerostar).

8. Software Pivot / Adjacent Market¶

Definition: A company develops hardware via FO but finds that the hardware market is smaller/harder than expected; the company pivots to software or adjacent markets, with the FO hardware work building domain credibility.

Mechanism: FO hardware project → TRL proof of concept → hardware market fails to materialize → company pivots to adjacent software/services → success in adjacent market

Examples: - Saber Astronautics / DragEN [12457]: Electrodynamic tether TRL 4→6 in parabolic; hardware never deployed; company became Air Force space operations software leader ($8.7M DoD: Sentinel, WINDU, Space Cockpit) - Vital Space Team [12203]: Non-invasive physio monitoring TRL 4→6; suborbital space tourism market didn't materialize; PI Komatireddy built Motiv Labs / Daytona Health in consumer digital health

Rate: ~10% of FO projects that don't achieve hardware deployment; the pivot requires PI/founder business development capability.

Nuance: In Saber's case, the FO work built spacecraft operations domain knowledge that made the software credible. The hardware work was not wasted — it was a credential.

9. Proof of Concept Only / No Follow-Through¶

Definition: FO validates the technology at TRL 5–7, but no further investment follows. The technology is real but the path to deployment doesn't exist — either market failure, no mission need, or institutional barriers.

Mechanism: FO validation → no NASA mission demand → no commercial demand → technology shelved

Examples: - Orbital Medicine [12196, 71978]: Medical chest drainage TRL 6, $0 downstream; ISS qualification barriers too high; market is NASA-only and NASA doesn't use it - Sierra Nevada ZGMMD [71984]: TRL 9 in parabolic; ISS deployment unconfirmed; no follow-on contracts found - Aurora → Boeing EDLS [91361]: Patent filed, Boeing absorbed Aurora, ISS deployment unconfirmed; Boeing doesn't sell ISS vibration sensors - Blue Origin Landing LiDAR [158500]: TRL 4→4 (stagnation); Blue Moon development continued via internal R&D

Rate: ~35–40% of completed industry projects in this KB. Significantly higher for academia-only projects with no institutional deployment partner.

Key determinant: Whether a specific NASA mission or commercial deployment path exists at FO project start. Without a clear path, validation ends at TRL 6 with no follow-through.

10. Academia → Earth Observation / Science Deployment¶

Definition: University researchers use FO to validate a sensor or measurement system for Earth science applications. The output is data published in peer-reviewed literature and/or a system deployed for operational environmental monitoring.

Mechanism: Academic lab instrument → FO flight → TRL 4→7 → publication and/or operational deployment

Examples: - Harvard wildfire smoke / Keutsch [155261]: Multi-sensor stratospheric system → controlled burn test April 2025 → community warning application - Massachusetts General Hospital NINscan [93962]: Cerebral hemodynamics → TRL 7 → NINscan-SE in Epilepsy Foundation clinical use - IMEC USA Neuropixels [106657, 106660]: Microgravity electrophysiology → npj Microgravity (Nature) 2025 → VGLUT alteration finding - JHU/APL VACNT → RAVAN [91344]: Radiometer absorbers → RAVAN CubeSat

Rate: ~15–20% of completed academia projects. Most academia FO projects produce a single data point for a journal paper (foundational knowledge, not deployment). The ones that reach deployment have either a clear societal application or an institutional mission (like RAVAN at APL).

Revenue: Zero commercial revenue. Impact via scientific knowledge, clinical tools, or environmental monitoring.

Session 13 addition: Montana State RadPC [91411] is a special case of academia FO that crossed into full mission infusion: FO TRL 5→7 → ISS deployment (Dec 2016) → RadSat-g CubeSat (Jul 2018) → Resilient Computing spinoff (~2020) → Firefly Blue Ghost lunar surface (Mar 2025, TRL 9). This is the only confirmed TRL 9 academic FO project in the portfolio. However, the RadPC arc spans multiple programs (FO → ELaNa CubeSats → CLPS), not purely FO. The FO project was the critical early validation bridge. (See msu-radpc.md)

11. Platform Company Extends Product Line¶

Definition: A large, established contractor uses FO to qualify a specific capability extension of an existing product line. FO's role is enabling the company to bid for new contracts requiring the extended capability.

Mechanism: Company has dominant market position in product → FO validates extended-performance version → company wins follow-on contracts with extended specification

Examples: - Airborne Systems / JPADS [91422, 93997]: FO extended JPADS to 50,000 ft; Orion parachute provider ($13.57M); DoD JPADS portfolio $300M+ - Creare LLC / cryo portfolio [155234, 158702]: LAD + freeze-tolerant radiator validated; Creare is established NASA cryo specialist; $60M+ portfolio - Paragon Space Development / COSMIC [155245]: Condensate separator validated; Paragon is ISS BPA incumbent; COSMIC extends franchise to WPA upgrade and Artemis HALO

Rate: ~10% of FO projects. Returns are large in absolute dollar terms (incumbent contracts), but FO's marginal contribution is smaller because the company would likely have won follow-on contracts without FO (just with lower-TRL components).

12. Government Center → Commercial Launch Infrastructure¶

Definition: A NASA center develops a technology required by or enabling commercial launch operators, validates it via FO, and transfers it through formal technology licensing or transfer. The output is not a NASA mission payload but a piece of launch infrastructure that enables the commercial launch industry.

Mechanism: NASA center identifies regulatory/safety gap in commercial launch → FO validates the technology → formal tech transfer (IP licensing + award) → commercial operator adopts as standard system → enables new launch sites or reduces range costs

Examples: - KSC AFTS / Autonomous Flight Termination System [106586]: KSC-developed AFTS validated via FO → KSC Technology Transfer Office award → Rocket Lab adopted for first US Electron launch at LC-2 Wallops (Dec 2020) → enables commercial launches from previously non-FTS-capable sites

Rate: Rare (~1–2% of FO portfolio). Requires: (1) unique NASA center expertise in regulatory domain, (2) commercial market need for the capability, (3) formal IP transfer mechanism.

Key distinction from Archetype 2 (Gov Tech → License → Mission): The output is infrastructure/operations enablement, not a mission payload. The "customer" is a launch operator fulfilling range safety requirements, not a mission integrating a science/engineering system.

Revenue: Not easily tracked via USASpending (AFTS is a cost of range access, not a separately billable service). The economic value is in range access enablement — each Rocket Lab US launch represents ~$7–10M in launch revenue enabled by having a compliant FTS.

13. NASA Center ISS/FO Infrastructure¶

Definition: A NASA center develops a tool specifically for use by the FO program itself or as ISS science infrastructure. The technology's "customer" is the NASA program ecosystem, not an external mission or company.

Mechanism: Internal program need identified → NASA center builds tool → FO validates → becomes operational program tool or ISS capability

Examples: - Ames SFEM / SFEM-2 / SFEM-3 [91425, 93961, 106612]: Suborbital Flight Environment Monitor; TRL 4→9 (operational); characterizes flight environment on sRLV vehicles for FO users; multi-center, multi-version arc - Ames Wet Lab 2 [91358]: ISS molecular biology platform; TRL 5→9 (ISS deployed); gene expression, bacteria detection; PI Macarena Parra; in use by multiple ISS investigations

Rate: ~3–5% of FO portfolio. These projects rarely appear in commercial contract tracking but deliver real program value: they enable other FO payloads to fly safely (SFEM) and enable new ISS science capabilities (Wet Lab 2).

Revenue: $0 in commercial contracts. Value is in program infrastructure and NASA science mission capability. Impact is measured in: (a) FO payloads enabled to fly per year, (b) ISS experiments using the deployed capability.

14. Flight-Qualified Technology Awaiting Mission¶

Definition: Technology reaches TRL 7-8 through FO and post-FO demonstration campaigns. The technology demonstrably works. But the intended downstream application (a specific mission, a commercial market) has not materialized. Not a dead end — the technology is proven — but no infusion confirmed after multiple years at high TRL.

Mechanism: FO validation → TRL 7-8 → additional non-FO demonstration flights → technology "parked" at high TRL → no mission selection → program winds down

Key distinction from dead ends (Archetype 9): Dead ends stagnate at TRL 4-5, often because the technology didn't work. Archetype 14 technologies worked and reached TRL 7-8. They are "flight-qualified but mission-orphaned."

Key distinction from active maturation: Active maturation has a specific named mission or program pulling the technology forward. Archetype 14 lacks that pull despite high TRL.

Examples: - Ames Exo-Brake [91382] (TRL 3→8): FO arc 2015-2020 + 4 post-FO TechEdSat missions (2021-2022); TES-7 proved 87% orbital lifetime reduction from 500 km; controlled sample recovery not demonstrated; no mission infusion; Murbach shifted focus ~2022 - CU Boulder Janus Starshade Sensor [91620] (TRL 4→7): Webster Cash's formation flying sensor for starshade exoplanet missions. Technology works. Starshade now being studied for HWO (Habitable Worlds Observatory, Decadal Survey #1 flagship). If HWO selects starshade architecture (~late 2020s decision), this becomes a 25-30 year maturation arc to the highest-impact science mission possible. If coronagraph is selected, it's mission-orphaned. Longest time-horizon FO technology in the portfolio. - Texas A&M Variable Radiator [91339] (TRL 4→7): vortex phase separator for variable heat rejection; no follow-on mission in TechPort; Advanced Cooling Technologies has licensed the underlying device - Sierra Nevada ZGMMD [71984] (TRL 4→9 in parabolic): highest TRL in parabolic flight; on-orbit ISS deployment unconfirmed

Rate: ~3–5% of completed FO projects with TRL gain ≥3. May be more common in academia (where there's no company owning the commercialization path).

Why it happens: 1. The technology solves a problem that doesn't have a confirmed mission home 2. The demonstrator is too small/cheap to attract mission-level investment 3. The PI moves on to other work; institutional momentum stops 4. The gap between "faster re-entry" and "recovered sample" (Exo-Brake) or "variable heat rejection in lab" and "variable heat rejection on a mission" is larger than the FO investment can bridge

Diagnostic question for prevention: At TRL 8, is there a mission that has committed to using this technology? If not, the probability of eventual infusion falls sharply with each passing year.

15. VC Portfolio Dynamics (Early-Stage Company Incubation)¶

Definition: FO provides minimal investment ($100K–$500K) to early-stage launch or space companies. The outcomes follow venture capital portfolio dynamics: most fail, a few succeed spectacularly, and FO's contribution is test infrastructure access + NASA credibility signal rather than decisive technology validation.

Mechanism: Early-stage company → FO provides test stand access (SSC, MSFC, AFRC) + NASA credibility → company raises VC funding → outcome determined by VC market dynamics, not by FO technology validation

Examples: - Relativity Space [94203]: FO ~$115K for SSC engine testing → company raised $1.3B+ VC → Terran 1 reached space Mar 2023 → $4.2B+ valuation - Ventions → Astra Space [94198]: FO electric pump testing → Astra reached orbit 2022 → went public via SPAC → collapsed to ~$30M market cap → delisted - Vector Launch [94194]: FO engine testing at SSC → raised $100M+ VC → bankrupt 2019 → assets acquired by Phantom Space (Feb 2025) - Generation Orbit [94191]: FO engine testing → became SpaceWorks subsidiary → AFRL X-60A $35.2M contract → X-60A dead (no flights since 2022) - Dynetics [94195]: FO H2O2/kerosene engine → Leidos acquisition ($1.65B) — but SLV program shelved; acquisition was for defense capabilities - HRL Laboratories [94200]: FO AM rocket engine → TRL 4→6 → no visible commercial product

Success rate: ~14% (1/7 actively building launch vehicles — Relativity). But: 3/7 had >$1B exits or valuations (Relativity, Astra peak, Dynetics/Leidos). VC-style portfolio math.

Key insight: FO's actual value for these companies was test infrastructure access (SSC, MSFC, AFRC Gulfstream III) + NASA credibility signal for investors. FO investment ($100K–$500K per company) was trivial compared to VC funding ($100M+ per company). FO was a catalyst, not a cause.

Key distinction from Archetype 4 (Startup Formation/Scale-Up): In Archetype 4, FO validates the core technology that defines the company's value proposition (Made in Space's 3D printing, Tyvak's avionics). In Archetype 15, FO provides infrastructure access — the company's technology would have been validated somewhere else without FO (just slower or more expensively). The outcomes are driven by VC market dynamics, not by FO technology validation.

Revenue model: FO is a minor line item in massive VC-funded development programs. Returns are measured in company valuations and exits, not in follow-on NASA contracts.

16. Deep Academic Partnership (Long-Duration Research Ecosystem)¶

Definition: A university research group uses FO as its primary reduced-gravity test infrastructure over many years (10+), running multiple sequential and parallel FO projects that feed a broader academic research program. The FO projects are not independent technology maturation efforts — they are nodes in a sustained research ecosystem that produces publications, trains students, advances fundamental knowledge, and in the best cases, generates scientific firsts.

Mechanism: Senior PI establishes research relationship with FO → multiple sequential FO projects over 10+ years → FO provides recurring access to reduced-gravity test environment → output is publications, ISS experiments, student training, and scientific breakthroughs

Key distinction from Archetype 10 (Academia → Earth/Science): Archetype 10 is a single project with a deployment outcome. Archetype 16 is a sustained institutional relationship — the PI treats FO as research infrastructure rather than a one-time validation. The output is a body of work, not a single instrument deployment.

Key distinction from Archetype 5 (Sequential FFRDC → Mission): FFRDC sequential projects converge on a specific mission (Draper → CP-12). Deep Academic Partnerships produce knowledge and training, not mission hardware. The "customer" is the scientific community, not a mission.

Examples: - UF Ferl/Paul Space Plants Lab [12182, 106695, 106579]: The exemplar. 3 FO projects over 15 years (2011–2026), embedded in a 25+ year space plant biology program. 11 orbital + 5+ suborbital experiments total. PI flew to space himself (Blue Origin NS-25, Aug 2024) — first NASA-funded university PI to conduct his own experiment. Landmark paper: first plants grown in Apollo lunar regolith (Communications Biology 2022). NSS Space Pioneer Award 2025. ~4,900 citations (Paul's Google Scholar). No commercial product. The downstream impact is measured in scientific infrastructure. - Purdue Collicott Slosh Dynamics: 15 FO projects over 14 years (2013–2027). Most prolific PI in the FO portfolio. Propellant slosh dynamics data feeds spacecraft designers across NASA and industry. PI flew own experiment on Virgin Galactic Galactic 07 (Jun 2024). Collicott teaches AAE 418 (zero-g fluid dynamics) at Purdue using FO data. - UCF Colwell/Dove Regolith Cluster: 13 FO projects over 14 years (2012–2026). 5 researchers. Pivoted from asteroid regolith to lunar surface operations for Artemis. NanoRocks ISS experiment. Q-PACE CubeSat (lost on orbit). Colwell appointed UCF Dean of Sciences (Mar 2026).

Rate: ~3–5% of FO projects by count, but these groups represent a much larger share of FO's total flight hours and recurring investment. Three groups (Ferl/Paul, Collicott, Colwell/Dove) account for ~31 FO projects combined — 7% of the portfolio.

Revenue: $0 commercial. Impact measured in: publications, ISS experiment deployments, student training (PhD students on each project), scientific firsts, and in two cases, the PI themselves flying to space with their own experiments.

Why it matters for FO evaluation: These partnerships represent FO's role as national research infrastructure — akin to a telescope or particle accelerator. The value is not technology transfer but sustained access to a unique test environment. Any FO program evaluation that focuses only on commercial outcomes will miss this entire category of impact, which accounts for ~7% of all FO projects and includes some of FO's most scientifically significant contributions.

Archetype Distribution (430 projects, 100% coverage)¶

Note: Distribution updated through Session 46 (100% portfolio coverage). All 430 FO projects triaged.

Archetype	Count	%	Avg downstream $
1. Middle-Step Bridge	8	2%	~$15M
2. Gov Tech → License → Mission	3	<1%	>$2.5B (Mars 2020 dominant)
3. Validation Service (large co.)	9	2%	~$30M
4. Startup Formation/Scale-Up	5	1%	~$50M
5. Sequential FFRDC → Mission	6	1%	~$60M
6. FFRDC Data Gap Closure	7	2%	~$1M (Phase III)
7. Acquisition Target	7	2%	~$80M (acq value, skewed by Terran $450M)
8. Software Pivot	2	<1%	~$8M
9. Proof of Concept Only	25	6%	$0
10. Academia → Earth/Science Deployment	6	1%	$0 (non-commercial)
11. Platform Extends Product Line	4	1%	~$100M (portfolio)
12. Gov Center → Launch Infrastructure	1	<1%	— (regulatory enablement)
13. NASA Center ISS/FO Infrastructure	3	<1%	$0 (NASA internal value)
14. Flight-Qualified Tech Awaiting Mission	4	<1%	$0 (TRL proven, no adoption)
15. VC Portfolio Dynamics	7	2%	~$1B (skewed by Relativity)
16. Deep Academic Partnership	~31	7%	$0 (scientific infrastructure)
Academia: open-source/educational	~5	1%	$0 (community value)
Academia: active maturation (ISS pipeline)	~10	2%	—
Research maturation (NASA Centers + Academia)	~95	22%	$0 (data/publications)
Dead ends / TRL stagnation	~80	19%	$0
Active / too early to assess	~51	12%	—
Canceled	~22	5%	—
Total	430	~100%

Important caveat: Archetypes are assigned based on the primary downstream mechanism. Many projects have secondary characteristics (e.g., a middle-step bridge company is also acquired). Double-counting is avoided.

The Three Conditions for Downstream Success¶

Across all archetypes, three conditions predict positive downstream outcomes:

Condition 1: Pull, not push¶

Technology advances because a mission, program, or market is pulling it forward — not because the FO program is pushing it. The best FO projects have a named downstream need (a mission, a company customer, a follow-on program) before the flight test. The worst have only a generic "NASA needs this someday."

Diagnostic question: Who is waiting for this data? If no one specific can be named, the probability of downstream deployment drops sharply.

Condition 2: Institutional accountability¶

Someone with authority (a program manager, a mission PI, a company CEO) is committed to incorporating the FO result. Institutional accountability means: when the flight data arrives, a human being will act on it. Draper needed DMEN for CP-12; Psionic needed NDL for its commercial offering; Giner needed the separator data for Phase III. In each case, someone was waiting.

Diagnostic question: Who has made a commitment contingent on the FO result?

Condition 3: The gap is irreplaceable¶

The FO test provides data that genuinely cannot be acquired any other way. If the technology can be validated in a ground chamber, there's no reason to fly it. If it requires microgravity, real free-flight dynamics, or space-environment exposure, the FO flight is irreplaceable.

Diagnostic question: What can this flight test show that no ground test can show? If the answer is "nothing specific," the project is likely to generate a data point but not a deployment.

What FO Does NOT Do¶

Based on 430 investigated projects:

FO does not create markets. No FO project created a market that didn't exist before. The best outcomes come when FO accelerates entry into a market that already exists or is clearly forming (e.g., CLPS, Artemis, DoD space logistics).
FO does not rescue failed technologies. Zero TRL gain projects (DTM Technologies, HNU Photonics, Busek 1U CubeSat) uniformly have no downstream outcomes. If the physics doesn't work on the flight, nothing follows.
FO does not substitute for a commercialization team. Companies that go on to acquire contracts or be acquired have business development capability (Made in Space, Tyvak, NSC). Companies that don't (Orbital Medicine, HeetShield pre-revenue) remain at TRL 6 indefinitely regardless of how well the flight went.
FO does not guarantee infusion, even at TRL 9. Sierra Nevada ZGMMD reached TRL 9 in parabolic testing — the highest possible TRL gain — and on-orbit deployment remains unconfirmed. TRL is a necessary but not sufficient condition.
FO does not produce commercial outcomes for health/medical projects targeting astronaut-only markets. Zero downstream contracts for Orbital Medicine, Vital Space Team, or Mayo Clinic ATOM beyond the immediate FO-funded period. The market is too small and regulatory barriers too high.

The NDL Principle¶

The Flight Opportunities program's strongest justification in this KB is not the average return — it's the tail case. NDL/Psionic is the demonstration that one FO project can make the difference between a mission succeeding and failing. When Odysseus's primary laser rangefinder failed at 10 km altitude, NDL (FO-validated TRL 6, later commercialized by Psionic) provided 100% valid altitude/velocity data that saved IM-1.

The implication: even if 35% of FO projects produce zero downstream impact, the ~5% that become genuinely mission-critical (G-FOLD on Perseverance, NDL on IM-1, Draper DMEN on CP-12) justify the program's existence on expected value grounds. The expected value of a Moon landing > the cost of many null FO projects.

This is the correct framing for FO program evaluation: not "what is the average return per project" but "what is the distribution of returns, and what is the expected value of the tail?"

P3 Base Rate vs. P1/P2¶

After Session 10, with 4 academia/FFRDC projects investigated in P3 sampling:

Industry-led completed (56 projects): ~25–33% positive downstream outcomes

FFRDC/Non-profit (P3 sample, 4 projects): - JPL G-FOLD/FOALS: Confirmed Mars 2020 mission infusion (the highest-value outcome in the portfolio) - Draper GENIE/TRN/DMEN: Confirmed CP-12 CLPS contract ($57M) - JHU/APL VACNT: Confirmed RAVAN CubeSat mission infusion - Harvard wildfire: Active near-operational deployment

P3 result: 4/4 positive outcomes (100%) in initial sample — but this is selection bias. The 4 projects were chosen for maximum information density. The true P3 base rate across all 25+ FFRDC projects is likely 40–60% (higher than industry, because FFRDC projects are typically attached to a specific mission from the start). Full P3 sampling in Session 11 confirmed: JPL 5/18 confirmed mission infusion (~28%), JHU/APL 2/10 confirmed (~20%). FFRDC overall: ~25-30%.

Session 13 — Academia base rate (first 20 projects sampled): - Confirmed mission infusion: 1 (RadPC → Firefly Blue Ghost, TRL 9) — 5% - Active ISS/commercial pipeline: 2 (SpaceCAL via LLNL/Space Tango; A-LiST TechLeap $500K) — 10% - Open-source technology spread: 1 (HDD wheels → Cornell ISS CubeSat) — 5% - Productive research (publications, ISS follow-on): 4 (COLLIDE/NanoRocks, FEMTA, FLEX biological imaging, COLLIDE Q-PACE dead end) — 20% - No downstream found: ~12 — 60%

Academia base rate (first 20): ~20% positive downstream; ~5% mission infusion; 60% research/no-follow-on

This is meaningfully lower than industry (25-33% positive) but higher than NASA Center fundamentals research (~10-15%). The differentiator for academia success: PI must either (a) have ISS/mission connection from the start (RadPC → NanoRacks deployer access), or (b) enter a competition structure that provides a clear next step (TechLeap Prize).