Friday, September 30, 2016

Unmanned Aerial Systems in the National Aerospace System


The integration of the unmanned aerial systems (UAS) into the National Aerospace System (NAS) brings out the subject of maintaining operational safety. Several important topics pertaining to the safe UAS operations have been discussed in recent years. They include establishing regulatory standards for UAS, communication link security, operator training and currency, vehicle maintenance requirements, and privacy concerns. This paper will focus on the UAS traffic separation requirements in the NAS. This issue is directly connected to UAS operational safety, since potential air traffic collision may result in a loss of life of manned aircraft occupants and persons on the ground.
Air traffic separation considerations
The main difference between the UAS and manned aircraft is the absence of a human pilot onboard of UAS. Traditionally, the pilot at the controls of a manned aircraft is in charge to see-and-avoid the nearby air traffic when operating in the visual meteorological conditions (Federal Aviation Administration [FAA], 2013). When flying in instrument conditions, air traffic control (ATC) provides traffic separation to all manned aircraft under their control. Pilots also rely on traffic collision avoidance technology that is available in the cockpit (Ramasami & Sabatini, 2015). For line-of-sight UAS operations, the operator on the ground has the authority to see and avoid other air traffic. However, visual traffic detection may be complicated at night and in adverse weather conditions. When operating a UAS beyond-line-of-sight, the vehicle controller is responsible for avoiding other traffic by relying on visual information and other available technology. However, the UAS operator’s situational awareness may be limited due to the restricted field of view, control signal latency, and lack of visual cues (Lam, Boschloo, Mulder, & Paassen, 2009). These limiting factors may negatively affect the UAS pilot’s ability to see and avoid other traffic. Therefore, UAS separation from other aircraft should be based on sense-and-avoid (SAA) technology installed on board the vehicle. Additional traffic separation can be provided by ATC, which can issue traffic advisories and alerts. Instead of communicating with the UAS itself, ATC would provide this information to the operator located at the ground control station (GCS). The disadvantage of this method is the possible delay in the communications and delayed collision avoidance execution due to signal latency.
Sense-and-avoid considerations for different UAS groups
The UAS operational altitudes, speeds, and sizes vary considerably depending on the UAS group. Therefore, the SAA technology selection should be based on the specific characteristics of the UAS. There is no one-size-fits-all SAA system currently available to fulfill the SAA requirements for all groups of the UAS (Gageik, Benz, & Montenegro, 2015). For instance, the Traffic Alert and Collision Avoidance System (TCAS), which is presently widely employed in manned aircraft could potentially be used in UAS. However, the large size and excessive weight of current TCAS equipment may prohibit its usage on some lighter UAS. Some of the smaller UAS may also be difficult to detect visually by a manned aircraft pilot due to their size. For example, a pilot of a manned aircraft travelling at 300 knots may not have enough time to see, react and avoid a small UAS. Pilots who routinely scan and locate full sized aircraft may have a difficult time locating small UAS and this may result in mid-air collision.
Consideration should also be given to different airframe designs of the UAS. For example, lighter than air UAS may lack maneuverability when compared to fixed-wing aircraft and may be unable to execute the evasive maneuver in a timely manner. However, their large size makes them more visible and their slower speeds decreases their closure rate with conflicting traffic.  
 Current sense-and-avoid technology
The current technology employed by manned aircraft includes both the ground-based traffic detection and separation and the airborne traffic detection and avoidance technologies.  ATC employs radars to monitor and manage aircraft traffic. Current ATC radars feature clutter reduction technology to include only primary traffic detection. Due to their small size some UAS may not be displayed on the radar screen. Therefore, modifications to radar processing may be required to allow UAS detection by the ATC (Lacher, Zetlin, Maroney, Markin, & Ludwig, 2010). Another option is to design the UAS to be easier to detect both visually and on radar. This is just the opposite of military UAS that need to be stealthy and hard to detect. Commercial UAS operation in the NAS should be designed to be easily seen and detected on radar. Day glow reflective paints schemes for visual detection and the use of sharp angles and highly reflective materials for radar detection will make the job of detection much easier for both pilot and controllers.  
A Ground Based Sense and Avoid (GBSAA) capability especially developed by the U.S. Army for UAS. The GBSAA is designed for traffic separation in the busy airspace segments, such as terminal areas. However, ground based sense-and avoid has limitations and needs to be supplemented with airborne sense-and-avoid technology (Department of Defense [DoD], 2016). For example, ground based SAA is susceptible to signal latency and may not be usable during lost link scenarios.
The airborne sense-and-avoid technologies includes both cooperative and non-cooperative sensors. Cooperative sensors obtain radio signals from another aircraft to determine its position and altitude. Cooperative sensors include: transponders, Automatic Dependent Surveillance – Broadcast (ADS-B), Automatic Dependent Surveillance – Contract (ADS-C) (Ramasami & Sabatini, 2015). TCAS is also a cooperative technology employed in manned aircraft, which is based on the aircraft's transponder equipment. It provides the pilot with traffic information, automated traffic alerts, and smart conflict resolution advisories. The disadvantage of cooperative sensors for SAA is that cooperative technology will only function if all participating traffic is equipped with transponders (Lacher et al., 2010). ADS-B and ADS-C is based on the satellite surveillance. This technology does not require ground based interrogation by a radar. Currently, cooperative sensors are not required in all classes of airspace. (Delves & Angelov, 2012). Figure 1 depicts UAS SAA system.

Figure 1. SAA system diagram for UAS. Adapted from “MIDCAS sense-and-avoid” by MIDCAS, 2011. Copyright 2011 by MIDCAS.

Non-cooperative sensors passively acquire target information or actively emit energy to perceive the surrounding traffic. The non-cooperative SAA sensors will function even if other aircraft are not carrying similar equipment. Non-cooperative sensors include millimeter wave radar, electro-optical/ infrared, thermal, and acoustic sensors (Lacher, Maroney, & Zeitlin, 2007). Different sensors has their own advantages and limitations (Ramasami & Sabatini, 2015). A full description of these sensors go beyond the scope of this paper. Some researchers offer a sensor fusion approach for UAS SAA in order to satisfy collision avoidance requirements. Figure 2 depicts sensor data fusion schematic.

Figure 2. Sensor data fusion for SAA technologies and system process. Adapted from “A unified approach to cooperative and non-cooperative sense-and-avoid,” by S. Ramasamy, S., & R. Sabatini, 2015. Copyright 2015 by S. Ramasamy, S., & R. Sabatini.

This is just a brief description of available SAA technology. As we can see, there are a variety of SAA methods employed in manned aircraft. It is possible to use some of these traffic avoidance methods for UAS. The author would recommend employing ground based surveillance together with airborne sensors for UAS to ensure proper traffic separation in the NAS. However, due to size, weight, and power limitations of different UAS groups, there is no one universal airborne sensor available for SAA. Therefore, it is important to select appropriate sensor based on the unique characteristics and operational parameters of the UAS.  For added safety an automated collision avoidance and evasive maneuver execution will be necessary to make the SAA protocols effective. Automated traffic avoidance execution will be especially useful in case of loss of link. Similar to car that will apply the brakes themselves when no input from the driver is detected. A last line of defense avoidance maneuver should be incorporated.    
With fast technological progress, it is likely, that SAA capabilities will increase rapidly. Smaller, and more capable sensors together with ground and satellite based traffic separation methods will enable safe UAS operations in the NAS.


References
Department of Defense. (2016). Airborne based Sense and Avoid (ABSAA) sensor for tracking non-cooperative aircraft for RQ-7 Shadow and larger UAS. Retrieved from https://www.sbir.gov/sbirsearch/detail/870673
Lam, T., Boschloo, H. W., Mulder, M., & Paassen, M. V. (2009, November). Artificial force field for haptic feedback in UAV teleoperation. IEEE transactions on systems, man, and cybernetics, 39, 1316-1331. Retrieved from http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=5263033&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D5263033
MIDCAS. (2011). http://www.midcas.org/News/News/Midcas-Flight-tests-press-release,i196.html

Sunday, September 18, 2016

Weeding out a solution


The design process is complex and requires extensive planning. The entire project can be compromised if problems are not found early in the design stage. It is important to identify possible issues within the project early in the design process to minimize risk of project failure and to avoid unnecessary costs and delays. A systems engineer’s responsibility is to manage the entire project. He will define derivative requirements based on customer needs and specifications. He will solve conflicts arising between the design teams and select the appropriate solutions. He will be responsible for the final product approval, launch, and support. It is a tremendous task, which can only be accomplished with careful planning, constant monitoring, and critical decision making.

The system engineer will have to take the role of mediator to solve conflicts between the two design teams. Sometimes the solution will require both teams to modify their systems in order to achieve a functioning end product (Loewen, 2013).

The current scenario describes the situation when an UAS system was built overweight. A major contributing factor to this issue is that the guidance, navigation, control and payload delivery system were all purchased from an outside vendor. This resulted in both systems going over their allotted weight budgets. This resulted in the inability of the UAS to carry a sufficient weight to spray a certain amount of fertilizer over the specified area without cutting into the fuel margin.

The customer is already expecting the UAS to meet certain performance requirements. Therefore, changing the system’s spraying capacity or range will potentially result in the customer cancelling its order and the entire project may be compromised. Therefore, we need to decide how we can change the UAS to accommodate the customers’ requirements and still be within the weight budget.

What are your considerations?

The primary focus in the systems engineering process are the project requirements. The entire project is focused on transforming the requirements into final product. The main idea is to fulfill these requirements within the constraints: limited resources, limited time, limited weight, etc. (Department of Defense [DoD], 2001). The requirement-based design is an approach which can be used to maintain “quality control” of the project and ensure that design team efforts match what the UAS must accomplish (Loewen, 2013). For this particular project it is important to consider the following:

1. We cannot cut fuel margin, since it will compromise the safety of the system and also reduce its range. Although, it may be possible to modify the power system to be more fuel efficient in order to provide longer endurance with the same fuel amount. However, this may result in significant increase in project cost and time required to complete the process.

2. We can custom design the payload delivery system and/or navigation, control, and guidance system. However, this option will also result in extra costs and time delays. However, certain modification may allow a decrease in size and weight of each system and, therefore, decrease overall gross weight of the UAS.

One solution is to modify the payload delivery (spraying) system by installing a pressurized fluid reservoir instead of electric motor driven pump. The pressurized spraying system will eliminate the need and weight of the motor, the pump and its wiring and hardware. This modification will also lower the overall power requirements for the UAS and save fuel. The reservoir would be filled and then pre-charged with compressed air to deliver the spray under pressure. Another solution is to modify the navigation, control, and guidance system by placing some required navigation and guidance subsystems in the ground control station (GCS) instead directly on the vehicle. It will also save weight and free up the extra space onboard.

3. We could find a different vendor for these system. It is possible to replace the control/navigation and guidance system with lighter off-the-shelf equipment. However, the availability may not be certain. Another concern is the safety and quality of the off-the-shelf products. Before making a commitment to purchase a system from the outside vendors, it imperative to review and verify its safety and quality characteristics.

4. We could increase a size of the UAS platform itself, this would allow it to house the existing systems.

5. We could incorporate lighter composite materials to help reduce the overall weight of the UAS.

6. We could compensate for weight increase by reducing the weight of other systems? For example, if we eliminate any redundant equipment, the UAS weight will be decreased. However, it is important to maintain certain level of redundancy to maintain operational safety.

What are your priorities?

First of all, we have to keep in mind the customer requirements. The entire project should be focused on creating a UAS, which will be able to carry out the customer specified mission. Another priority is to achieve the finished product within budget and with the time constraints. A quick time- to-market is another important consideration. Delays in production may hinder project success and allow competition to step in. Quality of the product is another priority. The product should be designed to be easily supported after release and throughout its lifecycle. It should be easy to maintain and, and if necessary, upgrade.  Of course safety should also be a major priority. Although, some may believe that since the system is unmanned, the levels of safety are not as important as with manned systems. However, it is imperative to keep in mind the safety aspect for UAS, considering that the vehicle may overfly populated areas and could easily become a hazard to personnel on the ground.

The systems engineer deals with solving conflicts between the design teams. The phase-gate approach can be used in systems development. This includes a periodic review of each system. The design team cannot continue past a certain point in the design process unless the corresponding review has been satisfactory completed. The review can be formal or informal (peer) review. Projects executed in a phase gate model have three main fundamentals: deliverables, criteria and outputs (Innotas, n.d.). Another important aspect to consider is traceability throughout the entire project. Traceability will ensure that each team is accountable for its design and this will allow the designers to trace their steps back to mistakes (Loewen, 2013). 

There are several steps in managing conflict: 

1. Explore the reasons for the conflict.

2. Find an alternate resolution for the disagreement.

3. Choose the most appropriate solution. 

4. Implement the solution.

5. Evaluate the solution (Rainey, n.d.).

This steps can be applied to any conflict. In this particular case, the system engineer will have to serve as the “mediator” between teams and recommend the best resolution.

 What do you think about the future prospects for the “next generation, enhanced” version of the system as a result of your approach?

It is important to keep in mind future missions for designed UAS. Maybe the customer requirements will change and an even larger spaying capacity will be required. It is also possible that a customer will add additional payload systems into the UAS, such as sensor and cameras for crop evaluation and monitoring. In this case, increasing size of the vehicle may be advantageous at this stage to allow for a larger payload capability in the future. Incorporating a modular design could be beneficial for future applications as well. It will allow the incorporation of “next generation” payloads without redesigning the UAS.


References




Sunday, September 11, 2016

History of Unmanned Aerial Systems


Unmanned aerial systems came a long way since they were first introduced. The first UAS were merely small remotely controlled vehicles, which were simple, carried minimal payloads, and were often disposed of after completing their missions. Modern UAS incorporate sophisticated designs, use advanced navigation equipment, employ the latest technologies for control, command, and communications. They carry advanced modular payloads, have onboard data processing capabilities, and disseminate data directly to the users. They can stay aloft for extended periods of time and feature stealthy signatures. However, all of these technological advancements were acquired through the lengthy process of research, trials, and mistakes encountered during the early stages of UAS development. For the purpose for this research, the author has selected two UAS platforms, designed for similar missions of military reconnaissance. First vehicle- the SD-1 falconer represents an early UAS design. The second UAS, the Spy’Ranger is an example of a contemporary UAS design. 

Northrop /Radioplane SD-1/RP-71/MQM-57 Falconer

The Falconer was built in 1955 by Radioplane company, which later became knowns as Northrop (Western museum of flight, n.d.). The Falconer UAS evolved from target drones. This 13 feet long vehicle had a wingspan of 11 feet and weighed 430 pound (Figure 1).

Figure 1. The RP-71 Falconer UAS. Adapted from “Northrop SD-1/MQM-57 Falconer,” by A. Parsch, 2007. Copyright by via Ordway/Wakeford, n.d.



It was capable of speeds up to 185 miles per hour, operating at top altitude of 15000 feet. It was equipped with McCulloch O-100-1 72 horse power piston engine. This UAS had 40- minute mission endurance and range of 100 miles (Parsch, 2007). The Falconer primary mission was battlefield reconnaissance. It was equipped with a still picture camera. An optional TV camera was also available. For night missions, the Falconer used flares to illuminate the survey area.

Flight control was accomplished with an autopilot, which also had a radio-control backup. The Falconer was launched via rocket-assisted takeoff launcher and used a parachute recovery system for landing (RPAV, n.d.). 

The Falconer continued to be used by the military until the mid-1970s. A total of 1500 Falconers were built by Northrop. The next UAS was built to carry out the same missions as the Falconer, however, it uses the latest technological advancements to give the vehicle superior capabilities in military applications.

Spy’Ranger UAS

This mini- UAS was developed by Europe's leading UAS developer- Thales. The Spy’Ranger is a relatively small platform, which weighs only 55 pounds. It is constructed mainly out of carbon-fiber material, which gives the vehicle’s airframe strength and durability (Figure 2).



Figure 2. The Spy’Ranger UAS. Adapted from “Spy’Ranger, the fruit of collaboration between an SME and a prime,” by C. Mackenzie, 2016. Copyright 2016 by N. Gain.



The UAS can be disassembled for transportation and assembled on-site in less than 10 minutes (Mackenzie, 2016). Similar to the Falconer, this UAS was specifically designed to perform reconnaissance missions. This mini-UAS features an electro-optical/ infrared (EO/IR) sensor, housed on the gimbal, which gives a greater view of the survey area and allows the operator to focus the camera and sensor equipment on target during vehicle maneuvering. The Spy’Ranger is also capable of real-time target acquisition with a high-definition imaging sensor and a laser pointer. The Spy’Ranger is able to downlink the collected sensor information in real time, which is critical on the battlefield. The Falconer was lacking this important capibilty. The Spy’Ranger features a range of up to 18- miles and has 2.5-hour endurance (Thales, 2016).

 The vehicle is launched with a lightweight launch system, which is similar to the Falconer UAS. It can be setup in minimal time and can allows take-off in any direction. It only requires a small areas to launch and is capable of  all weather operations. The Spy’Ranger has an electric propulsion system, which gives the vehicle extra stealth capability. The Spy’Ranger can perform precise landings even in constrained areas. With help of specially designed software, the Spy’Ranger can calculate the best approach and landing taking into account wind and obstacle information. It features a landing cushion constructed from a Foam-Kevlar hybrid, which protects the vehicles during landings and helps absorb the shock (Thales, n.d.). The precise landing capability makes it easier to recover upon mission completion. The Falconer, on the other hand, could be difficult to locate after landing. The recovery parachute was greatly affected by the wind and in some cases, the Falconer was damaged while being dragged by the recovery parachute after touch-down or lost completely.

Another feature, which was not use in the early years of UAS is datalink protection. The Spy-Ranger uses a secure encrypted datalink, which prevent jamming and intrusion by an enemy.

As we can see, both of the described UAS were designed for reconnaissance. They feature similar size and weight characteristics. A similar catapult launch systems were used for both platforms. However, the materials used for airframe construction are more advanced in the Spy’Ranger UAS, comparing to the metal airframe of Falconer. New stealth characteristics are also taken into account with the use of an electric propulsion system on the Spy’Ranger. The real-time communication and datalink capability of the Spy’Ranger is crucial for today’s military applications. Datalink security is another priority for modern UAS operations, which was not a consideration in the early UAS designs.

UAS has been operating since World War II in the role of Surveillance and reconnaissance. They provide commanders with critical information on the battlefield. However, as we can see from two of these examples, the UAS technology has evolved significantly since the early years of UAS conception.  


References