RFI HAPS_HALE.docx

UxS Operations Center Request for Information (RFI)

High Altitude Long Endurance (HALE) / High Altitude Pseudo Satellite (HAPS)

1.0 Introduction & Purpose The National Oceanic and Atmospheric Administration (NOAA) Uncrewed Systems Operations Center (UxSOC) is issuing this Request for Information (RFI) to identify industry capabilities for deployment on a High Altitude Long Endurance (HALE) and High Altitude Pseudo Satellite (HAPS) uncrewed aircraft system (UAS). The objective is to evaluate how these stratospheric platforms can address NOAA’s observational user needs across multiple observation domains and missions. This UAS platform is capable of achieving long duration missions (+30 days) with multiple scientific payloads.

2.0 Core Platform Requirements Prospective platforms must demonstrate capabilities to operate safely and persistently in the stratosphere while accommodating dynamic payload suites.

· Operating Altitude: The platform must be capable of sustained flight above active weather systems and commercial airspace, with a minimum operational floor of 40,000 feet. Vendors are requested to specify their platform's maximum certified altitude ceiling and nominal cruising altitude. The ability to perform vertical profiling (controlled altitude descents and ascents) for in-situ atmospheric point sampling is highly desired.

· Endurance: Missions require continuous, persistent flight ranging from 30 to 60 days, with an ultimate target of 3 to 4 months of uninterrupted operation.

· Geographic & Latitudinal Reach: Platforms must be capable of deployment across diverse geographic zones, including the tropics, mid-latitudes (15–60° N), extreme high latitudes (above 70° N), and broad oceanic basins (Atlantic, Pacific, and Caribbean).

· Telemetry & Command: Real-time telemetry is critical for instant, secure access to data during flight. The system must support command uplinks to monitor instrument performance and adjust remote operational parameters during long-duration deployments.

3.0 Data Collection Domains, Payload SWaP, and Gap Alignment NOAA intends to integrate specialized scientific payloads to address critical observational gaps. Vendors should detail their platform's ability to support the following Size, Weight, and Power (SWaP) constraints aligned with specific agency gaps:

Power: 20 – 35 W (Continuous) / 50 – 75 W (Peak).

Overcomes coarse satellite imagery and low-altitude weather constraints to reliably detect marine mammals.

Dimensions: 50 cm max linear.

Power: 10 – 100 W.

Resolves satellite vertical microphysical resolution limits to track wildfire emissions, volcanic plumes, and stratospheric baseline burdens.

Power: 10 – 15 W (Continuous) / 40 – 60 W (Peak).

Fills critical upper-air sampling voids in vast remote oceanic regions where surface stations cannot exist. Improves hurricane and atmospheric river track forecasts.

Power: 130 – 190 W (Continuous) / 275 – 350 W (Peak).

Evaluates and fulfills requirements for surface and oceanic wind speed, wind direction currently limited by scatterometer and satellite SAR temporal latency.

Power: 10 – 18 W (Continuous) / 25 – 40 W (Peak).

Serves as a flexible airborne "Gap Filler" to mitigate risks associated with commercial spacecraft Radio Occultation (RO).

4.0 Vendor Questionnaire Interested parties are requested to provide detailed responses to the following operational and technical questions:

1. Platform SWaP-C Integration: Describe your platform's payload capacity. How does payload weight (e.g., scaling from a 10 lb optical suite to a >40 lb SAR package) impact your maximum endurance and altitude ceilings?

2. Power Generation in High Latitudes: Given that some missions require operations above 70° N latitude, how does your platform's power architecture (e.g., solar arrays, battery density) maintain sustained operations during winter months with minimal solar exposure?

3. In-Situ Vertical Profiling: Do your flight control systems and airframes support intentional, controlled altitude changes (vertical profiling) for atmospheric point sampling without compromising mission safety or endurance?

4. Service Model: Describe your capability to operate under a "Data-as-a-Service" model. Does your firm provide end-to-end mission execution (platform, pilot/operator, telemetry routing), and what is the typical lead time for payload integration and deployment?

5. Cost Structure: Please describe your Data-as-a-Service (DaaS) cost model for HAPS/HALE data, including pricing structure (e.g., per flight hour/day, area, product,etc.), what is included (processing, delivery, storage, retention, value-added products), fixed vs. variable costs, any minimum commitments or volume discounts, additional fees. Provide, if possible, a cost range for flight information for 30-90 day long flights.

Disclaimer: This RFI is not a Request for Quotes or Proposals. No contract shall be awarded from responses to this RFI. Specific details related to NOAA’s needs are subject to change.

image1.png