N21A-T003 TITLE: Combined Electro-Optics/Infrared and Radar Sensor System for Detect and Avoid of Non-Cooperative Traffic for Small Unmanned Aerial Systems
RT&L FOCUS AREA(S): General Warfighting Requirements
TECHNOLOGY AREA(S): Air Platforms; Electronics
OBJECTIVE: Develop dual-sensor, electro-optics/infrared (EO/IR) and radar, non-cooperative, traffic sensor concepts that will provide sufficient performance and balanced size, weight, power, and cost (SWaP-C) for small unmanned aerial systems (sUAS) where sufficient performance is unachievable by any single-sensor concept.
DESCRIPTION: DAA cooperative sensors that have been developed for manned aircraft, for example, Traffic Collision Avoidance System (TCAS) and Automatic Dependent Surveillance-Broadcast (ADS-B), are nondevelopmental and off the shelf. Detect and avoid (DAA) non-cooperative sensor subsystems, which take the place of a pilotís eyes, are a new construct whose role and employment has not been previously defined. Airborne Collision Avoidance System Xu (ACAS Xu) is a new DAA technology being developed by the Federal Aviation Administration (FAA) that processes inputs from both cooperative and non-cooperative sensors and provides alerts to the UAS operator to Remain Well Clear (RWC), and in the future will provide automatic maneuvers. Radar is the only current sensor actively being procured by the Navy as a non-cooperative DAA sensor with Radio Technical Commission for Aeronautics (RTCA) Do-366 addressing radarís Minimum Operational Performance Standard (MOPS) in the National Air Space (NAS). No other non-cooperative sensor has a MOPS. The radar development and production costs are high and dependent on its assigned role and the associated performance requirements. As such, a complete assessment of SWaP-C must be included in the establishment of safety requirements. EO/IR sensors are a desired alternative due to potentially lower SWaP-C. They are currently being considered for non-cooperative traffic surveillance as a part of RTCA Special Committee 228; however, they have performance challenges in low-visibility conditions and difficulty estimating range and range rate measurements that are essential for projecting Closest Point of Approach (CPA) and Time of CPA (TCPA). There is interest by civilian authorities (e.g. Federal Aviation Administration)and by the Navy for a dual sensor EO/IR and radar non-cooperative traffic sensor that will provide sufficient performance, but with less SWaP-C. A camera alone is not sufficient nor suitable for integration with ACAS Xu due to these shortcomings, and a radar, capable of doing the job, would not fit on board. A lower performing radar, providing suitable range and bearing information, to be combined with an EO/IR sensor, to meet the stringent SWaP-C limitations of sUAS is desired. All airborne hardware should weigh less than 3 lbs (1.36 kg) (Threshold) and 12 oz (340.2 g) (Objective); and consume less than 64 in.≥ (0.00105 m≥) Threshold) and 27 in.≥ (0.000442451 m≥) (Objective) of total space, with a power draw of less than 50 W average (Threshold) and 25 W average (Objective).
Critical evaluation criteria include the ability to provide sufficient tracking range and accuracy in order for an RQ-7 Shadow or RQ-21 Blackjack to avoid midair collisions and near midair collisions with other aircraft such as a Lancair Evolution, Cessna TTx, or Cessna 150. In general, radars provide highly accurate range and range rate information, but their angular resolution is inferior to EO/IR sensors. A dual-sensor system approach for sUAS must operate in lower altitude (<10,000 ft), overland environments, which present challenges for radar systems as slow-speed traffic may not separate well from the clutter and sources of false alarms. Likewise, performance of EO/IR systems suffer their own false-alarm problems, and performance is highly dependent on atmospheric conditions. An effective dual-sensor system must be able to detect and track targets in a range of atmospheric conditions, manage false alarms and clutter effects, and provide high enough accuracy to predict and avoid collisions. Such a system must consider multisensor data fusion approaches, multiband imaging system for all-weather operations, algorithms for mitigating false alarms and enhancing detection, sensor resource management (SRM) and feature-aided target characterization and tracking.
PHASE I: Design, develop, and demonstrate feasibility of dual-sensor detection, tracking, and false-alarm mitigation algorithms for expected operational environments and conditions. The Phase I effort will include prototype plans to be developed under Phase II.
PHASE II: Based on Phase I results, candidate concept(s) will be matured through more detailed, high-fidelity analyses and the development of dual-sensor detection, tracking, and false-alarm mitigation algorithms for expected operational environments and conditions. Examine sensor-integration concepts suitable for candidate sUAS. Assess hardware, software, and firmware impacts to accommodate the dual-sensor system, onboard candidate, sUAS. Identify critical technical challenges, perform necessary analysis, and as required, experimentation to understand the associated risk. The Phase II deliverable must provide a dual-sensor concept of sufficient detail to support the fabrication of a prototype demonstrator system.
PHASE III DUAL USE APPLICATIONS: Complete development, perform final testing, integrate, and transition the final solution to Navy airborne platforms. The dual sensor system is suitable for use on commercial small unmanned aircraft.
KEYWORDS: electro-optics/infrared sensor; radar sensor; airborne detect and avoid; non-cooperative airborne traffic; small unmanned aerial systems; collision avoidance
** TOPIC NOTICE **
The Navy Topic above is an "unofficial" copy from the overall DoD 21.A STTR BAA. Please see the official DoD Topic website at rt.cto.mil/rtl-small-business-resources/sbir-sttr/ for any updates.
The DoD issued its 21.A STTR BAA pre-release on December 8, 2020, which opens to receive proposals on January 14, 2021, and closes February 18, 2021 at 12:00 p.m. ET.
Direct Contact with Topic Authors: During the pre-release period (Dec 8, 2020 to January 13, 2021) 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 January 14, 2021 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, proposers may submit written questions through SITIS (SBIR/STTR Interactive Topic Information System) at www.dodsbirsttr.mil/topics-app/, login and follow instructions. In SITIS, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing. Topic Q&A will close to new questions on February 4, 2021 at 12:00 p.m. ET
Note: Questions should be limited to specific information related to improving the understanding of a particular topicís requirements. Proposing firms may not ask for advice or guidance on solution approach and you may not submit additional material to the topic author. If information provided during an exchange with the topic author is deemed necessary for proposal preparation, that information will be made available to all parties through SITIS. After the pre-release period, questions must be asked through the SITIS on-line system.
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.