N242-083 TITLE: Recovery System for Group 3–5 UAVs for Sea-Based Operations
OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Human-Machine Interfaces; Sustainment; Trusted AI and Autonomy
OBJECTIVE: Develop a novel recovery system for arresting Group 3–5 fixed-wing Unmanned Aerial Vehicles (UAVs) aboard air capable ships that minimizes required deck landing area and footprint on the ship.
DESCRIPTION: The Navy needs to operate fixed-wing UAVs from ships other than aircraft carriers—a capability that, if introduced, would significantly increase lethality, ability to project force, and the range of Intelligence, Surveillance, and Reconnaissance (ISR) [Ref 1]. A key enabler is recovery of UAVs spanning a large recovery envelope, that is, varying in weight, size, and approach velocity. The recovery system should be capable of arresting Group 3–5 [Ref 2] fixed wing UAVs (objective) or UAVs with a weight range of approximately 500–10,000 lb (454–4536 kg) (threshold), wingspan of approximately 15–70 ft (4.5–21.5 m) (threshold), and approach velocity of approximately 50–150 knots (92.6–277.8 kph) (threshold). Rotor-borne flight solutions (e.g., deploying rotors for landing, or tail-sitters) are not within the scope of this SBIR topic.
The Navy is interested in novel approaches to recovery that minimize required deck landing area and footprint on the ship. Respondents are encouraged to consider a total systems approach that includes novel flight control techniques as part of the proposed total concept. For example, solutions may consider putting the aircraft into a stall prior to capture/arrestment to reduce velocity. Solutions are not limited to a particular ship class or installation methodology. Concepts that utilize permanent installation (e.g., recovery equipment embedded within/under the flight deck) are acceptable, as are nonpermanent concepts (e.g., those temporarily attached to the top of the flight deck, above the flight deck, or extending out from the side of the ship). Non-permanent concepts should consider portability, stow-ability, and modularity, and should not impede safe movement of people, aircraft, and other equipment across the flight deck. Potentially relevant air capable ships (ACS) may include the Destroyer (DDG), Expeditionary Sea Base (ESB), Amphibious Transport Dock (also known as Landing Platform Dock [LPD]), or a new ship class or sea-based platform entirely. Relevant flight decks may be approximately 50–200 ft (15.2–61 m) long and 40–100 ft (12.2–30.5 m) wide. Solutions should consider deck dynamics and ship motion, including ship air-wake and related aerodynamics/aeromechanics, wind-over-deck, ship direction of travel, operation in sea state 5, survival in sea state 8 (including ship motion and flexure), and associated trim, list, pitch, roll, and heave requirements.
Given variable ship and aircraft sizes, concepts may be modular or include a family of systems that scale for higher and lower energy vehicles. Designs that follow a system-based approach, where the system is composed of the aircraft and recovery method, are preferred. Although the recovery system should be capable of arresting a range of UAVs, concepts that include a new, clean-sheet aircraft that integrates with a new recovery methodology are acceptable to promote compatibility between future UAVs and future UAV Aircraft Launch and Recovery Equipment (ALRE). In addition, solutions that provide the recovery system with initial conditions (UAV weight, velocity, approach vector) of the arrestment as the aircraft approaches, are allowable and encouraged. Strategies for collecting/sharing this information (e.g., avionics, communication between aircraft/recovery system, sensors aboard ship, etc.) are within the scope of this SBIR topic.
UAVs utilizing the recovery system may be low cost and attritable (i.e., affordable mass), potentially enabling higher risk acceptance than carrier-based, manned ALRE. Increasing automation is also desirable to minimize additional manning requirements. Solutions should take into account time for recovery and boarding rate as they will impact energy absorption and thermal/cooling requirements. A sortie rate of 25 arrestments per day per recovery system (objective) or 15 arrestments per day per recovery system (threshold) is acceptable. Military standards should be referenced for environmental factors (MIL-STD-810H [Ref 3]), electromagnetic interference (MIL-STD-461G [Ref 4]), shock (MIL-DTL-901E [Grade A] [Ref 5]), and vibration (MIL-STD-167-1A [Type 1] [Ref 6]) since the recovery system must be rugged to be viable.
In the interest of promoting ALRE that is common to multiple aircraft and multiple ships, the Navy recommends a holistic/systematic approach. In other words, although design of a launch system is not within the scope of this SBIR topic, the need for launch and recovery systems to both fit and work together on a single ship should not be ignored. Concepts should also consider pre-launch and post-recovery storage of UAVs and ALRE. Solutions that use shared equipment for launch and recovery and modular/scalable concepts will reduce overall ALRE weight, deck space, and volume. There are also potential impacts to topside weight, ship storage tradeoffs, power, and cooling water requirements driven by congruous versus incongruous designs.
PHASE I: Develop a conceptual design and provide proof-of-concept analysis in a computer simulated environment. Analysis should include both recovery system functionality and flight control dynamics. Specifically address areas of technical risk such as aircraft/recovery system interfaces and absorption of aircraft kinetic energy. The Phase I effort will include prototype plans to be developed under Phase II.
PHASE II: Provide more detailed design and digital analysis of all components, potentially including, but not necessarily limited to, mechanical, electrical/power, controls, thermal, and communications subsystems. Deliver a subscale prototype of the recovery system with adequate representation of the geometries and functioning major subsystems. Demonstrate that the prototype is capable of recovering a subscale UAV, or representative vehicle in terms of scaled size, weight, and velocity. Report results of the demonstration, including next steps, improvements required, and detailed plans for how to construct a full-scale prototype.
PHASE III DUAL USE APPLICATIONS: Design, develop, and fabricate a full-scale working prototype of the recovery system based on work completed during earlier phases. Determine a safe and effective means of testing the recovery system using aircraft-representative deadload(s) in a land-based test environment and work with relevant stakeholders to coordinate instrumentation, data collection, and metrics of success. Conduct deadload testing to validate and verify performance. If successful, plan and perform initial aircraft testing.
A recovery system (and launch system) for fixed-wing UAVs has secondary applications in the delivery, shipping and receiving, and transportation industries. Autonomous, unmanned aircraft can assist with package delivery, whether over long distances or the last mile. An efficient and effective launch and recovery solution for fixed-wing aircraft enables delivery of retail packages, food, medical equipment, and other cargo at greater speed, range, and endurance. As demonstrated by Zipline in Rwanda, fixed-wing UAVs can provide a useful solution for quickly shipping medical supplies to remote areas. In congested urban environments, replacing gas-powered delivery trucks (e.g., FedEx, UPS, and Amazon) and personally owned vehicles (e.g., DoorDash) with electric UAVs can also reduce traffic congestion and pollution. Although vertical takeoff and landing (VTOL) UAVs present an alternative, they may only be viable for a limited range and present noise pollution challenges.
Expanding launch and recovery technologies to higher UAV weights can increase cargo capacity for deliveries over longer distances. Introducing ALRE allows the aircraft to take off and land over a shorter distance, reducing reliance on airports, which can decrease land area used for runways, and the time and logistics footprint associated with sending packages from a warehouse to an airport. ALRE also does not need to be situated on land or stationary structures, but could be used to launch/recover aircraft off of trucks, cars, tractor trailers, trains, ships, barges, or other aircraft. For example, a larger UAV could be launched from a warehouse; then, while in the air and near a delivery location, it could deploy a high quantity of smaller UAVs for final delivery; those smaller UAVs could be recovered by the larger UAV to return to the original warehouse, or the smaller UAVs could be recovered on land at a location near the delivery location.
Systems that meet safety requirements and have acceptable G-forces at launch and recovery could also be used for transportation of people. There is a long history of launch and recovery of manned aircraft aboard aircraft carriers; however, a system used for mass transportation would need to significantly reduce acceleration and deceleration forces to be acceptable for the general public. Some concepts may be capable of significantly reducing these forces to permit transport of people.
REFERENCES:
KEYWORDS: Recovery; arrestment; unmanned aerial vehicle; UAV; aircraft; attritable; affordable mass
** TOPIC NOTICE ** |
The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoD 24.2 SBIR BAA. Please see the official DoD Topic website at www.defensesbirsttr.mil/SBIR-STTR/Opportunities/#announcements for any updates. The DoD issued its Navy 24.2 SBIR Topics pre-release on April 17, 2024 which opens to receive proposals on May 15, 2024, and closes June 12, 2024 (12:00pm ET). Direct Contact with Topic Authors: During the pre-release period (April 17, through May 14, 2024) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic. Once DoD begins accepting proposals on May 15, 2024 no further direct contact between proposers and topic authors is allowed unless the Topic Author is responding to a question submitted during the Pre-release period. SITIS Q&A System: After the pre-release period, until June 5, 2024, at 12:00 PM ET, proposers may submit written questions through SITIS (SBIR/STTR Interactive Topic Information System) at www.dodsbirsttr.mil/topics-app/ by logging in and following instructions. In SITIS, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing. Topics Search Engine: Visit the DoD Topic Search Tool at www.dodsbirsttr.mil/topics-app/ to find topics by keyword across all DoD Components participating in this BAA.
|
| 04/17/24 | Q. | 1. Which UAV is the focus? Is there a list of relevant UAVs to reference?
2. What electrical power is available shipboard? 3. What type of fuel is available shipboard? |
| A. | 1. The intent is to develop a common recovery system that can be used with UAVs in the weight range provided. Potentially relevant UAVs can be found at the following references: https://en.wikipedia.org/wiki/Unmanned_aerial_vehicles_in_the_United_States_military and https://en.wikipedia.org/wiki/Collaborative_combat_aircraft Not all aircraft listed are relevant as some fall outside of the weight range provided in the topic. These lists should not be considered exhaustive.
2. Please reference MIL-STD-1399-300 PART 1 and MIL-STD-1399-680. Table 2 of each document details electrical power system characteristics. 3. JP-5 is used shipboard. It is used for both aircraft and Support Equipment. |
|
| 5/3/24 | Q. | 1. Can you confirm the scope? Is maintenance, storage, and swapping of weapons, payloads, or other components within scope?
2. Are we limited to operating on ships? 3. Are cranes available on ships? 4. Can you provide more information on sea states? |
| A. | 1. The scope includes the development of the recovery system or arresting gear used to stop the UAV and any associated subsystems required to achieve this. Maintenance, storage, and swapping of components would not be within scope; however, aircraft handling CONOPS (i.e., moving the aircraft after arrestment) would be within scope if the concept requires that the recovery system be cleared prior to arresting the next aircraft.
2. No, the recovery system could be used on land-based sites such as Expeditionary Airfields. Other sea-based platforms are also acceptable. 3. Yes, but they are typically crash cranes for lifting damaged aircraft from the flight deck, not for the purpose of moving or retrieving functional UAVs over the weight range provided. 4. The Navy uses the Douglas sea state chart. Typically, the smaller the ship is or the lighter the ship is, the more it moves. Hull shape and boat headings also play a large role in movement. Overall, the interaction between sea states and ship movement is complex and dependent on a number of factors. |