Friday, May 20, 2016

UAS in the National Airspace System

As aviation has grown throughout history the issue of separating aircraft from each other has been a long standing mission of the Federal Aviation Administration (FAA).  The National Airspace System (NAS) has seen tremendous growth as the evolution of aircraft and passenger demand has driven the amount of aircraft co-existing in the skies.  Most model aircraft and hobbyist have remained in specially designated areas as part of the regulations set forth by the FAA.  However, the rapid development of various types of Unmanned Aerial Systems (UAS) has seen in unprecedented amount of incursions into the airspace specifically reserved and managed by the FAA.  These incursions represent a severe hazard to air traffic currently operating within the rules and regulations specified by the FAA.  The FAA is now attempting to regulate and integrate these new types of aircraft into the NAS.  Expanding UAS research and training objectives and the resulting increase in demand for NAS access is driving the need for additional FAA policies and procedures to authorize and manage UAS operations in a safe and effective manner (Federal Aviation Administration, 2012).  The FAA has currently developed a Certificate of Waiver or Authorization (COA) for UAS use within the NAS as an interim solution.  UAS that are granted NAS access today are limited by the restrictions of each COA or special airworthiness certificate, which often impose constraints on timeframe (daylight only), weather (visual meteorological conditions only), flying over populated areas, and other operational factors (Federal Aviation Association, 2012).  While imposing this COA allows flights of UAS within the NAS it does not allow for aircraft, manned and unmanned, to co-exist and operate in the same environment.  The FAA must block off and prevent other aircraft from flying into areas where UAS are operating in order to manage them effectively.  This creates a tremendous amount of workload and inconvenience for the FAA.
Numerous manufacturers are developing and experimenting various ways for aircraft to communicate to each other for the purposes of deconfliction, both manually (pilot initiated) or automated.  Most aircraft today use Identification Friend or Foe (IFF) combined with a Traffic Collision Avoidance System (TCAS) as a means of both communicating to ground control and providing location awareness to other aircraft.  However, not all aircraft are equipped with this equipment.  That being said, there is strict guidance and enforcement on the areas in which these aircraft can operate.  Because each pilot carries a certificate that is subject to revocation many pilots operate in a professional manner that respects the rules and regulations set forth by the FAA.  In relation to UAS, specifically Groups 1 -3, the IFF required equipment is too large, cumbersome, and requires a power source that is beyond their ability to operate.  Most Group 4 – 5, and some Group 3 UAS are equipped with IFF but it is not required in most cases due to the lack of current guidance and regulation.  With the advent of Automated Dependent Surveillance-Broadcast (ADS-B) and its adoption by the FAA and other civil aviation authorities around the world, aircraft will begin broadcasting their state vector to Air Traffic Control (ATC) and other ADS-B equipped aircraft independent of transponder interrogators (Strain, R., DeGarmo, M., and Moody, C., 2007).  However, the limited payload and power generation capabilities of small UAS make it impractical for them to equip with existing ADS-B units, not to mention the transponder-based system available today (Strain, R., DeGarmo, M., and Moody, C., 2007).  However, most manufacturers have realized that ADS-B doesn’t necessarily need to be installed directly on the aircraft and can instead be placed mostly inside the Ground Control Station (GCS).  This allows the aircraft to only transmit position and status to the GCS which will in turn communicate via ADS-B to the other players.  While this is one of many potential solutions it negates the operations of aircraft that have no means of communication (i.e. dirigibles, crop dusters, experimental, and some simple VFR aircraft).  Additionally, the various types, capabilities, sizes, and flight profiles of different types or groups of UAS make it incredibly difficult to define a standard profile requirement for their operations.   
              This is an ongoing issue among the integration of UAS in the NAS and the FAA has yet to fully grasp an effective means of managing this issue.  As technology continues to evolve at a rapid pace, solutions to these issues will become easier to navigate as bright young minds tackle these problems with fresh perspective and new technology. 


REFERENCES
Federal Aviation Administration (2012, September).  Integration of Unmanned Aircraft Systems into the National Airspace System; Concept of Operations v. 2.0.  Retrieved from http://www.suasnews.com/wp-content/uploads/2012/10/FAA-UAS-Conops-Version-2-0-1.pdf
Strain, R., DeGarmo, M., and Moody, C. (2007).  A Lightweight, Low-Cost ADS-B System for UAS

Friday, May 6, 2016

Weeding Out a Solution

A UAS is to be designed for precision crop-dusting. In the middle of the design process, the system is found to be overweight.

Two subsystems – 1) Guidance, Navigation & Control [flying correctly] and 2) Payload delivery [spraying correctly] have attempted to save costs by purchasing off-the-shelf hardware, rather than a custom design, resulting in both going over their originally allotted weight budgets. Each team has suggested that the OTHER team reduce weight to compensate.

The UAS will not be able to carry sufficient weight to spread the specified (Marketing has already talked this up to customers) amount of fertilizer over the specified area without cutting into the fuel margin. The safety engineers are uncomfortable with the idea of changing the fuel margin at all.
Write a response describing how you, as the Systems Engineer, would go about resolving this issue. Use your imagination, and try to capture what you would really do. Take into account and express in your writing the things you’ve learned so far in this module: What are your considerations? What are your priorities? What do you think about the future prospects for the “next generation, enhanced” version of the system as a result of your approach?

While it is important that the vehicle both fly correctly and spray correctly there needs to be a solution to the overweight dilemma.  Reducing the weight of unmanned aerial vehicles (UAVs) pays large dividends in their ability to carry more fuel, support more advanced payloads (radar, imaging, sensors, navigation and guidance, uplinks and downlinks), achieve longer flight times, and operate from shorter runways (Oliver, 2012).  Both teams have decided on using off-the-shelf (OTS) hardware which has resulted in an overweight situation.  The fixed factors are the fuel and the amount of fertilizer.  Therefore, the only manageable means of navigating this situation is to design custom lighter options for guidance, navigation & control, payload control, increase propeller lift capability, increase motor size, or utilize a lighter design structure for the entire craft.

In most design projects it comes down to two very important factors; time and money.  Therefore, I will begin this project by mandating that each team compile a report that specifies the time and money required to design a custom solution instead of the OTS version.  By forcing the teams to figure out a solution within the design parameters, it will encourage creativity and possibly flush out new ideas or theories that can lead to breakthrough solutions.  The best case scenario is that one or both teams find an easy solution to the weight problem by either slightly modifying the OTS version or designing a new version that is within cost, time, and weight parameters.   Reducing the weight of the electronics, and especially the power-supply subsystem, is a major area for potential improvement (Oliver, 2012).     

Meanwhile, I will consult the propulsion department and have that department begin an evaluation to determine if a different type of propeller is capable of carrying the weight with no negative fallout in regards to the fuel or time aloft considerations.  If the propulsion department cannot produce a better lifting mechanism I will suggest investigating a larger power source.  However, I will stress that the power source must not use any more fuel than what is currently allotted per the original design specifications.  

Lastly, consulting with the structure design engineers may result in some ideas that will result in a lower overall weight to the vehicle.  I will encourage they investigate other materials that may be more durable and lower weight.  However, the cost consideration along with ability to procure material will need to be considered as part of the overall project goals and objectives. 

Ultimately, both teams have failed to fully analyze the problem and create a solution within their parameters which is unacceptable for the success of the project.  They need to go back to the drawing board and come up with custom intelligent designs that meet the demands of the project, thus keeping the project on track.  However, if neither team is able to accomplish a better solution than the OTS, I have consulted with other departments that might be able to offer a solution to the overweight problem. 

REFERENCES

Oliver, S. (2012, August). Take A Multifaceted Power Approach To Reduce Your UAV’s Weight:  Electronic Design.  Retrieved from http://electronicdesign.com/power/take-multifaceted-power-approach-reduce-your-uav-s-weight

Thursday, April 28, 2016

History of UAS

Unmanned Aerial System (UAS) design has developed tremendously as the evolution of technology has allowed for more capability and reliability.  However, while most early Department of Defense (DOD) publications will refer to the three “D”’s of UAS operations (Dull, Dangerous, Dirty), it is interesting to note that the fourth “D”, known as “deep” or “denied” has long since been part of the DOD operational considerations (OPCONS).  The ability to fly above other countries and survey vital parts of their infrastructure is an important part of national defense.  The AQM 91, designed in the 1960’s, and the current day RQ-4, share that mission of high altitude UAS surveillance. 

The Teledyne Ryan AQM 91 Firefly or Compass Arrow was specifically built and designed for cross border operations into China in the early 1960’s.   To fulfill the requirements, the Firefly was given an operational altitude of 78,000 feet with a mission endurance time of 4.5 hours and range out to 2,000 miles (Military Factory, 2014).  Teledyne Ryan / Ryan Aeronautical produced the AQM91 "Firefly" as a stealth minded, high altitude, photo reconnaissance Unmanned Aerial System (UAS). Development began in the late 1960s with the design intended for use by the U.S. Central Intelligence Agency (CIA) as well as the United States Air Force (USAF) for secret overflights of Chinese airspace with particular interest given to its growing nuclear sites (Military Factory, 2014).  This initial design used a precision navigation autopilot system that was cutting edge and sophisticated for the 1960’s.  Engineers were able to reduce navigational error to less than 1 percent in operations, but the system proved to be inconsistent and prone to error over time.  By design, the AQM91 was intended for air launching from a host mothership this being a Lockheed DC130E "Hercules" aircraft (a drone controlling variant of the famous transport aircraft) and thusly not fitted with its own launching facility (Military Factory, 2014).  The craft would be recovered utilizing a helicopter and hook recovery system in flight. One can surmise that the majority of the mission was flown autonomously as satellite communications would have been in early developmental stages. A manual override function allowed for ground controllers to assume function as needed (Military Factory, 2014). Its onboard photographic equipment allowed for vast swathes of territory to be photographed from 15 miles up with detail providing clarity down to one foot (Military Factory, 2014).  Real time Full Motion Video (FMV) would also not have been capable in high definition and it is likely that canisters of film were downloaded from the aircraft after recovery, much like the manned U-2 aircraft.

While there are numerous models of UAS that can be compared to the mission of the Firefly it is most easy to relate it to the RQ-4 Global Hawk.  Coincidentally, The Global Hawk was originally designed by unmanned aircraft pioneer Teledyne Ryan Aeronautical, which was bought by Northrop Grumman in 1999 (Rogoway, 2014).  The Global Hawk has seen numerous design revisions to improve upon its initial design.  These are most often referred to as blocks.  The most current design version is Block 40.  The RQ-4A Global Hawk is a high-altitude, long-endurance unmanned aerial reconnaissance system which provides military field commanders with high resolution, near real-time imagery of large geographic areas (Air Force Technology, n.d.).  High-resolution sensors, including visible and infrared electro-optical systems and synthetic aperture radar, will conduct surveillance over an area of 40,000nm² to an altitude of 65,000ft in 24 hours (Air Force Technology, n.d.). The Global Hawk is semi-autonomous, meaning that it still requires occasional commands and cross checking with a team on the ground via a desktop type, and “point to fly here" interface (Rogoway, 2014).  The advent of Global Positioning System along with satellite communications allows for a much more capable and relevant vehicle for today’s operations.  This systems relies on a Ku band satellite data link or a line of sight data link to operate (Rogoway, 2014).  The prime navigation and control system consists of two KN-4072 INS/GPS (inertial navigation system / global positioning system) systems (Air Force Technology, n.d.).  The Global Hawk has a suite of sensors that can be chosen based on mission and aircraft requirements.  Much like the high altitude Firefly, The Global Hawk flies high at a loiter altitude 65,000ft which minimizes exposure to surface-to-air missiles.  The RQ-4 has launch and land capability like normal aircraft and does not require a sophisticated launch and recovery procedure requiring other aircraft support.

While both the Firefly and the Global Hawk both served a vital service in the high altitude “Deep” mission, they are very different due to the advancement of technology.  The initial design of the Firefly was well ahead of itself, but the inability to launch and recover easily made for a troublesome program.  Lack of satellite communications and a GPS made the ability to receive real time FMV impossible, while also creating navigational/control issues.    
    
REFERENCES 

Air Force Technology (n.d.).  RQ-4A/B Global Hawk HALE Reconnaissance UAV, United States of America.  Retrieved from http://www.airforce-technology.com/projects/rq4-global-hawk-uav/
Military Factor (2014).  Ryan AQM-91 Firefly / Compass Arrow Reconnaissance Drone (1968).  Retrieved from http://www.militaryfactory.com/aircraft/detail.asp?aircraft_id=1151
National Museum of the US Air Force (2015, May).  Teledyne-Ryan AQM-91A Compass Arrow.  Retrieved from http://www.nationalmuseum.af.mil/Visit/MuseumExhibits/FactSheets/Display/tabid/509/Article/198027/teledyne-ryan-aqm-91a-compass-arrow.aspx

Rogoway, T. (2014, September).  Why The USAF's Massive $10 Billion Global Hawk UAV Is Worth The Money; Foxtrot Alpha.  Retrieved from http://foxtrotalpha.jalopnik.com/why-the-usafs-massive-10-billion-global-hawk-uav-was-w-1629932000