For Technology Readiness Level (TRL) work, a near-space balloon flight at 80,000–100,000 ft can satisfy a TRL 6 "relevant environment" demonstration for most space hardware, and in narrow cases supports TRL 7 — when the stratosphere genuinely is the operational environment. It does not reach TRL 8 or 9; that requires orbit. For an SBIR Phase II principal investigator (PI), a prime program manager (PM), or a component manufacturer building flight heritage, the value is a documented relevant-environment demonstration an assessor can sign against — not a model.
Short answer: a near-space balloon flight at 80,000–100,000 ft can satisfy the TRL 6 "relevant environment" demonstration for most space hardware, and in narrower cases supports a TRL 7 claim. It does not, by itself, get you to TRL 8 or 9 — that requires orbit. The longer answer is the one your program review actually cares about, because the difference between "we modeled it" and "we flew it" is the difference between a defensible readiness claim and a finding.
This is the question we hear most from the engineers, SBIR Phase II PIs, prime PMs, and component manufacturers preparing for a milestone gate, a Phase III transition, or a flight-heritage datasheet. Here is how the readiness levels actually map to a stratospheric flight, in the language your assessment will use — including, plainly, what the flight does not do.
What TRL 6 and TRL 7 require
The two levels turn on one word: environment.
The DoD Technology Readiness Assessment (TRA) Guidebook (February 2025) is explicit. A relevant environment is "a set of stressing conditions, representative of the full spectrum of intended operational employments" (DoD TRA Guidebook, Feb 2025, p. 20). TRL 6 requires your critical technology element (CTE) to be "embedded or installed in a representative model or prototype" and demonstrated in that relevant environment. The progression to TRL 7 "involves a shift in the scale of the demonstration" — the same prototype, now installed in a prototype of the planned system, demonstrated in an operational environment (DoD TRA Guidebook, Feb 2025).
NASA's TRL 6 boundary is the same: a "system/sub-system model or prototype demonstration in a relevant environment (ground or space)." Note the parenthetical — NASA explicitly allows a ground relevant environment to support TRL 6. NASA's TRL 7, however, is space-specific for space systems: a "system prototype demonstration in a space environment" (NASA TRL Definitions; NASA SCaN renders TRL 7 as "demonstrated in a space environment"). That distinction matters: NASA does not bless a non-space TRL 7 for orbit-bound space hardware. DoD's generic "operational environment" wording is broader, and it is the reading under which a stratosphere-operating system can earn TRL 7 — not NASA's space-specific one.
Two consequences are worth pinning down before you cite a number in a review.
First, the gate is real for the programs that hit it. The TRA Guidebook ties the TRL 6 relevant-environment demonstration to Milestone B for major defense acquisition programs (DoD TRA Guidebook, Feb 2025). And NASA's own best-practices guidance states that "a TRL of 6 (technology demonstrated in a relevant environment) or higher is required for a technology to be integrated into a flight system" (NASA TRA Best Practices Guide, p. 4). TRL 6 is the threshold for integrating a technology into an operational flight system — not a wall that bars all flight. Technology-demonstration missions deliberately fly lower-TRL items to mature them; the point is the integration-into-a-flight-system gate, and that is the gate this argument is about.
Second, a relevant environment is "the specific subset of the operational environment" that stresses the at-risk parts of your design (NASA TRA Best Practices Guide, p. 8). You do not have to reproduce all of low Earth orbit (LEO). You have to reproduce the subset that breaks your hardware.
Why thermal-vacuum is necessary but not sufficient
A thermal-vacuum (TVAC) chamber is a required tool. Every serious space-hardware qualification campaign runs one, and a chamber does some things a balloon cannot: it reproduces true hard vacuum (~10⁻⁵–10⁻⁶ Torr), and it delivers controlled, repeatable hot-and-cold cycling to a defined spec. That is real qualification value, and a balloon flight does not retire it.
What a chamber does not do is apply the stressing set simultaneously, in flight, on the integrated system. It stresses parameters in isolation on a bench. A near-space balloon platform delivers, at once and through a real flight profile:
- Low pressure into the corona/Paschen regime — roughly 1.1 kPa (≈8 Torr) at 100,000 ft, and ≈2.9 kPa (≈22 Torr) at 80,000 ft. This is the band where corona onset, Paschen-minimum arcing, and partial-pressure breakdown threaten high-voltage and radio-frequency (RF) hardware — a failure mode a hard-vacuum chamber soak can step over on its way down to vacuum. This is not orbital hard vacuum: at ~8 Torr the stratosphere is roughly seven orders of magnitude higher pressure than low Earth orbit (~10⁻⁶ Torr), so it does not reproduce outgassing, cold-welding, or multipaction behavior and does not replace TVAC vacuum-level or outgassing/total-mass-loss screening (U.S. Standard Atmosphere 1976).
- A flight-realistic cold case (−60°C to −70°C) on the integrated structure, in real time — complementary to, not a replacement for, the commanded hot/cold cycling of a TVAC campaign. It is one largely uncontrolled cold soak with residual convective coupling, not a hot case and not a defined cycle count (−60°C to −70°C is StratoStar's flight-measured cold case; the standard-atmosphere model runs warmer in this band, so the measured figure is the colder, payload-real value).
- A real, in-flight ionizing-radiation field — galactic cosmic rays plus secondary atmospheric neutrons, peaking near the Pfotzer maximum (~20 km). Over a 2–6 hour flight this is a negligible total ionizing dose, and the field is secondary-neutron-dominated — it contains essentially none of the trapped-proton/electron flux or the heavy-ion/solar-particle spectrum that drive total-ionizing-dose (TID) and single-event-effect (SEE) qualification for orbit. It can be a genuine data point for screening single-event-upset and latch-up behavior in a real flight field (cf. JEDEC JESD89 atmospheric-neutron context), but it is not a substitute for beam-line/cyclotron TID/SEE qualification, which remains a separate ground campaign.
- Real RF propagation — the one a chamber cannot fake. An anechoic chamber has no real ground-station geometry, no real path loss at distance. For a radio, a transmitter, or a link-budget claim, "tested in a chamber" and "closed the link from 100,000 ft" are not the same evidence. The balloon validates real path loss and link-budget closure at real slant range — not orbital Doppler dynamics; a wind-drifting or near-stationary balloon does not reproduce the ~7.5 km/s line-of-sight rates that drive a LEO link's Doppler shift. As a concrete figure: StratoStar's own flight telemetry closes a 915 MHz LoRaWAN link (Semtech SX1262, 24.8 dBm EIRP) at real slant range — a 2023 flight logged 100% packet delivery at up to 342 miles (≈550 km) at spreading factor SF9. A customer payload's radio is characterized in that same real channel: real path loss at altitude, real ground-station geometry, real link-margin data — the propagation a chamber cannot reproduce.
The mechanical reality should be stated just as plainly. Balloon ascent is gentle — roughly 5 m/s, low-g, quasi-static — so a balloon flight does not replace launch-vibration, sine, or random-vibe qualification. The real mechanical events are termination (cutdown) shock and landing impact, not a vibration spectrum. A structures engineer should read that as a complement to a vibration campaign, not a stand-in for one. (In practice the most revealing vibration a payload sees before flight is often the shipping crate: integration teams have found fasteners backing out in transit — a workmanship issue surfaced by real-world handling, exactly the kind a bench rarely catches.)
The standards framing supports the integrated-stress point: at TRL 6, the relevant environment exists to surface design issues when the prototype meets stressing conditions as a system, not as isolated parameters on a bench (DoD TRA Guidebook, Feb 2025). A chamber stresses parameters in isolation; a flight stresses the integrated system under simultaneous loads. For the at-risk subset that a balloon does reproduce, that is the gap a near-space flight closes between a TRL 5 and a TRL 6 case.
High-altitude balloon and aircraft testing has long been treated in readiness-assessment practice as an illustration of relevant-environment demonstration for instruments and subsystems — NASA's own TRL guidance gives "a prototype satellite instrument tested on a high-altitude balloon or an aircraft" as a TRL 6 example (NASA System-Level TRL 6 Examples), and peer-reviewed work documents the path directly — a 180 GHz satellite radiometer matured on high-altitude balloon flights (CubeSounder, arXiv 2602.23338). Balloon flight test is not a workaround; for the right hardware and the right at-risk subset, it is a recognized path.
What balloon flight does not do
Engineers trust vendors who name limits, so here they are, without hedging. A near-space balloon flight does not replace your TVAC thermal-cycling campaign (no controlled hot case, no commanded cycle count, no true hard vacuum). It does not replace launch-vibration, sine, or random-vibe qualification (the flight's mechanical events are termination shock and landing, not a vibration spectrum). And it does not provide beam-line or cyclotron radiation qualification (the stratospheric dose is negligible and the field is the wrong spectrum for orbital TID/SEE). What it does deliver is the integrated, simultaneous, in-flight stress — and the RF and low-pressure realism — that a bench cannot.
So: TRL 6, or TRL 7?
Here is the honest division, because your assessor will draw it whether or not you do.
TRL 6 — the strong, defensible case. Your component or subsystem prototype, flown at altitude in the stressing environment subset that matters to it. A radio that closes a real link at real slant range. A sensor that holds calibration through a real flight cold case. A board that survives the corona/Paschen low-pressure regime. This is a clean relevant-environment demonstration, and it is the demonstration the TRA Guidebook ties to Milestone B.
TRL 7 — the narrower case. TRL 7 requires the prototype installed in a prototype of the planned system, in an operational environment (DoD TRA Guidebook, Feb 2025). For hardware whose operational environment is the stratosphere — atmospheric instruments, high-altitude sensing payloads, communications relays meant to operate at altitude — a sustained near-space float (3–6 hours in the operational band) can legitimately support TRL 7, because you are flying in the operational band, not an analog of it. For hardware destined for orbit, the stratosphere is a relevant environment for the subset it reproduces, not the operational one. Claim TRL 6, document it cleanly, and let the orbital demonstration carry the TRL 8–9 argument later. Never claim TRL 8–9 from a balloon.
The discipline that wins reviews is this: claim the level your evidence supports, and bring the evidence. A documented flight — telemetry, thermal and pressure logs, link data, photographs of the hardware at altitude — is evidence an assessor can sign against. "We simulated it" is not.
What the program needs from the flight
A TRL claim is only as good as its documentation, and the deliverable means something different to each buyer at the gate.
For the prime PM, the deliverable that survives a program review is the structured one: telemetry plots, the temperature and pressure profile through the full flight, link-budget data where RF is at risk, imagery of the payload at altitude, and an engineering report written to the readiness-level framing your assessment uses — mapped, where possible, to the DoD TRA evidence structure. That package — not the flight itself — is what moves the program forward.
For the SBIR Phase II PI, a relevant-environment demonstration is a Phase II deliverable that underwrites the Phase III transition. Flight evidence at TRL 6 is exactly the kind of milestone result that strengthens a commercialization plan and a sole-source justification for the Phase III follow-on. The flight buys evidence your funding reality can be built on.
For the component manufacturer, the documented flight is the heritage data package — datasheet-grade, flight-heritage evidence that attaches to a radio, sensor, or avionics datasheet and to the next proposal. Treat the flight as one event inside your qualification campaign, not a one-off: a qual or protoflight article flown in a real environment, with a report a customer can cite.
It also has to come back on a schedule the review can plan around. A relevant-environment demonstration that arrives after the gate is not a demonstration; it is a slip. The value of a published flight date is that the milestone can be planned against it.
The bottom line
A near-space balloon flight is a recognized way to demonstrate space hardware in a relevant environment, which is the TRL 6 threshold the TRA Guidebook ties to Milestone B and the threshold NASA names for integrating a technology into a flight system. For stratosphere-operating hardware, a sustained float can support TRL 7. It does not replace orbit for TRL 8–9, and it does not replace your TVAC, vibration, or beam-line radiation campaigns — and you should not claim it does. Claim what you flew, document it to the framework, and walk into the review with data instead of a model.
That is the whole argument for real flight test. Real Flight Test. Real Data.
StratoStar Systems flies space hardware and stratospheric UAS payloads on a published Flight Test Calendar — firm-fixed price, 99%+ recovery, hardware returned within 72 hours, with a structured engineering report built for your readiness review. The flight qualification service (FQS) flies 2–6 lb to 80,000–100,000 ft for a TRL 6 relevant-environment demonstration; the integrated flight service (IFS) flies up to 20 lb on a 60,000–80,000 ft sustained float (3–6 hours) for stratosphere-operating hardware making the narrower TRL 7 case. Request a flight test.
Sources
- DoD, Technology Readiness Assessment Guidebook (February 2025): https://www.cto.mil/wp-content/uploads/2025/03/TRA-Guide-Feb2025.v2-Cleared.pdf
- NASA, Technology Readiness Level Definitions: https://www.nasa.gov/wp-content/uploads/2017/12/458490main_trl_definitions.pdf
- NASA, Technology Readiness Assessment Best Practices Guide (SP-20205003605): https://ntrs.nasa.gov/api/citations/20205003605/downloads/%20SP-20205003605%20TRA%20BP%20Guide%20FINAL.pdf
- NASA, Technology Readiness Levels (SCaN program overview): https://www.nasa.gov/directorates/somd/space-communications-navigation-program/technology-readiness-levels/
- NASA, System-Level TRL 6 Examples: https://soma.larc.nasa.gov/simplex/pdf_files/TRL_Examples.pdf
- CubeSounder: Low SWaP-C 180 GHz Radiometer for Atmospheric Sensing Tested on High Altitude Balloons, arXiv 2602.23338: https://arxiv.org/pdf/2602.23338
- U.S. Standard Atmosphere, 1976 (NTRS 19770009539): https://ntrs.nasa.gov/citations/19770009539
- StratoStar first-party flight telemetry (2023 LightTracker flight; Semtech SX1262 LoRaWAN, 24.8 dBm EIRP; 342 mi range at 100% packet delivery, SF9)
Hero image: NASA/JPL-Caltech.