Monday, June 13, 2016

UAS in medical application advantages and challenges


Research paper 6.4

Jingwen Cai

Due June 5th, 2016.


Imagine public use of UAS for the medical emergency service when your family member has heart attack or broken bone, you may not expect a big red fire truck with a white ambulance showing up at your door at all. Instead, a UAS may show up at your patio or backyard to take your bio send the information to the doctor in emergency room, or let you load the patient inside the UAS and flight him/her to hospital.

There are three platforms capable of performing the medical emergency service.  

The rotorcraft UAS platform is vertical take-off and landing, which has advantage of landing in the residential area, either at the drive way, the backyard, or the roof of the apartment or office building.  It doesn’t require the run way or big open field for landing or take off. This will help to deliver the fresh donor human organ between hospitals, pick up the patient and send to the emergency room without delay due to the traffic.

The fixed wing UAS platform has advantage of long distance travel, and transport higher payload. For example, if one hospital needs some equipment that is only available in another facility, then a fixed wing UAS can be assigned to transport this heavy equipment. It not only can help to transport the medical supplies to remote area, but also to dangerous area where manned aircraft is too risky.  The UAS may drop off the supplies in the dangerous without being detected because it is smaller, quieter than manned aircraft.

The min UAS platform is unique to the unmanned aircraft.  The mini UAS can be sent to high contagious area to take bio and sample from the patients and do instant analysis for blood samples if microchip payload is added. The UAS will not breath the virus filled air and still have the job done.

The benefits associated with performing the medical care response for the UAS mission are: cost effective, shorten response time, flexible in location and time, applicable to remote or dangerous areas.

The Challenges associated with performance the particular UAS mission are not limited on how to operate a UAS, or where to get a permit. It is the long time to have many UAS platforms certificated, because UAS platforms must comply with safety standards for technology, such as DO-178 B and C for flight-critical software, as well as DO-254 for hardware, explains RTI (UAO staff, 2016).

Two legal or ethical challenges to the medical emergency missions are people’s concern of safety, and unintended trespass. The safety concern is due to accident from design, communication, reliability, and operation mistakes.  Who will be responsible for UAS accidents where the owner or the operator is not at the crash scene? The space boundary and trespass is a drag of war because of the UAS intrusion and ambiguous airspace definition.  How many feet above your backyard is your space? How many feet from your parked car in the drive way is your airspace that neighbor’s UAS service can’t go in? (Duno, 2015).



Reference:


Emergency Medical. Retrieved on June 3rd, 2016 from http://www.uas-core.com/#!emergency-medical/xdefv

Duno, D. 2015. Unmanned Aircraft in the National Airspace: Critical Issues, Technology, and the Law

UAO staff. March 2016. Upcoming Webinar: ‘Solving Avionics Safety Certification Challenges in UAS Platforms’. Retrieved on June 3rd, 2016, from upcoming-webinar-solving-avionics-safety-certification-challenges-in-uas-platforms





UAS Separation from UAS


Jingwen Cai

ERAU ASCI 530 Research Assignment




The monitoring and maintaining of the separation of the unmanned aerial systems from the NAS is through the current FAA regulations and heavily rely on modern technologies.  The FAA notice N JO 7210.873 provides information and interim guidance on air traffic policies and prescribes procedures for the planning, coordination, and services involving the operation of unmanned aircraft systems (UAS) in the national airspace system (NAS).

The separation of the UAS requires a letter of agreement (LOA) if there is conflict, and each UAS must apply for a certificate of waiver or authorization (COA) before a specific UA’s activity is authorized. The FAA will review the UAS basic information, such as method of air traffic control (ATC) communications, surveillance capability, system monitoring/recording capability, flight plan, and reports of past incidents or accidents. 

The UAS shall have the sense-and-avoid method that provides an equivalent level of safety comparable to see-and-avoid requirements for manned aircraft. Technologies used to meet this requirement includes, but not limited to, radar observations, forward-or side-looking cameras, electronic detection systems, visual observation from ground sites, monitoring by patrol or chase aircraft, or a combination there of. 

UAs are required to be equipped with standard aircraft anti-collision or navigation lights following in 14 CFR, section 23.1401, and an altitude encoding transponder that meet the specification of 14 CFR, section 91.215.  The transponder must  be set to operate on a code assigned by ATC. In the event of lost link, the UA must squawk code 7600.

Direct two-way radio communication with ATC and the UA pilot is required at all times. This will ensure the monitoring and maintaining of the UA flying in the NAS at all time.  

For the difference airspaces, UAS is not allowed to operate in class B at this time, but all other airspaces.

For different sizes of the UAS, the requirement is a little different. The UAS manufacturer goes through a 3 to 5 year process to obtain a type certificate, which enables the issuance of a standard airworthiness certificate according to FAA requirement.  The pilots of small UAS is also required to pass an initial aeronautical knowledge test and obtain an unmanned aircraft operator certificate with a small UAS rating.

In 2012, Congress passed the FAA Modernization and Reform Act of 2012 (Public Law 112-95). In section 333 of Public Law 112-95, Congress also directed the Secretary to determine whether “certain unmanned aircraft systems may operate safely in the national airspace system.”

FAA encourages to develop and integrate UAS enabling technologies within the NAS infrastructure. UASs aren’t a part of NextGen, but NextGen technology such as NVS will play a role in their safe integration in to the NAS. NVS, which takes advantage of modern router-based communications, will enable FAA to route, monitor and share information among facilities across the country. System Wide Information Management (SWIM) is the data-sharing backbone of NextGen, which distributes the weather and flight planning information to the NAS. The Flight information exchange model (FIXM) is developed to serve as a global standard for sharing data about flights. ERAM is the next generation computer system for en route centers, which control high-altitude traffic. Data Comm is for delivering message via digital format. 

In summary, the roadmap for UAS merging into the NAS is planned and quickly getting updated with new technology innovations.





Reference:

N JO 7210.873. July 11, 2014. Unmanned Aircraft operations in the national airspace systems (NAS). Retrieved on May 29, 2016 from http://www.faa.gov/documentLibrary/media/Notice/N_JO_7210.873_Unmanned_Aircraft_Operations.pdf

Unmanned Aircraft Systems, Federal Aviation Administration. https://www.faa.gov/uas/

Billing Code 4910-13-P DEPARTMENT OF TRANSPORTATION Federal Aviation Administration 14 CFR Parts 21, 43, 45, 47, 61, 91, 101, 107, and 183 [Docket No.: FAA-2015-0150; Notice No. 15-01] RIN 2120–AJ60 Operation and Certification of Small Unmanned Aircraft Systems. Retrieved on May 29, 2016 from https://www.faa.gov/regulations_policies/rulemaking/recently_published/media/2120-AJ60_NPRM_2-15-2015_joint_signature.pdf

NextGen. FAA. Retrieved on May 29. 2016 from http://www.faa.gov/nextgen/media/NextGenUpdate2014.pdf


UAS comprehensive plan, JPDO. The secretary of Transportation. Nov 6, 2013.Retrieved on May 29, 2016  from http://www.faa.gov/about/office_org/headquarters_offices/agi/reports/media/UAS_Comprehensive_Plan.pdf


ASCI 530 – Unmanned Systems

Module 7 – Systems Development and Test & Evaluation (T&E)

Activity 7.4 – Assignment: Request for Proposal – RFP

Jingwen Cai





RobinRobin, is a fire drone, or a UAS that is designed for natural disaster such as wild fire is proposed in this paper. This will include overview of design considerations, decisions for derived request including transportability, cost, air vehicle frame, control and command, pay load and data-link. Test requirement and verification schedule is also included.

UAS  development has sequential phases listed below. Some overlap and splashback may exists between phases. Formal review and approval by the user and management is at the end of the most phases before the beginning of the next phases to ensure it meet the requirement and avoid the risk. This is called “passport” at some design company because without the passport, the project can’t be forwarded to the next phase.

Table 1, RobinRobin UAS project flows based on the “selecting a development approach”, 2005.


Project Phases
Time
Principles
1
Initial Investigation
3 months
Focus on market research and user’s requirement
2
Requirement Definition
1 month
Clear objectives and agreement with stakeholders
3
System Design
2 month
Focused on developing  engineering specification
4
Coding, testing, DFMEA
4 month
Small scale mock-ups, ground testing, inflight testing,
5
Implementation
4 month
Based on the prototype, then large scale with learnings
6
Operation & Support
2 years
Real time support, training and technical transfer



From the initial investigation, RobinRobin UAS will fulfill some basic requirements as outlined below:

·         Day and night operations

·         High temperature tolerance

·         Various altitude operation

·         Hover at a certain spot for a certain time to do surveillance and putting off fire

·         Real time surveillance and feedback for fire and ground situation to ground station

·         Large capacity to carry and spray chemicals to extinguish fires



Translate these requirement into technical language, we can list these into system design requirement

·         Radius of action is defined as the maximum distance that the RobinRobin can travel away from the base with payload and return to base after the mission without refueling. Users asked for 5 miles because it is a safe distance for the ground operation from a wild fire zone.

·         The endurance at the radius of action is largely based on the payload and fuel amount.

·         Payload and aircraft frame shall be able to provide information on the location of the fire edge, the intensity and location of hotspots

·         Can “see” through the smokes.

·         Communication shall be compactable to those helicopters, air-tankers, ground station.  It shall send the fire and ground situation to the manned aircraft and commanders.



The low level requirement for RobinRobin is listed as below:

·         Cost

o   The budget cap is $20,000 each for hardware only, not including the training, maintenance, and operation cost.

o   Off shelf component shall be the first choice to reduce the cost

o   The cost for pilot license, flight plan approval cost, and other FAA required permit doesn’t included here.



·         Aircraft Vehicle

o   Shall be capable of flight up to 500 feet altitude above ground level (AGL)

o   Shall be capable of flight two hours without refueling

o   Shall be capable of covering an operational radius of 5 miles

o   Shall be deployable and on station in less than 10 minutes

o   Shall provide capture of telemetry, including altitude, magnetic heading, latitude position, longitude position and orientation

o   Shall be capable for Vertical launching and landing

o   Shall have Power plant that do not have risks of fuel burning or leaking at the fire zone

o   Shall have the material on the outside surface with heat resistant coating every where

o   Shall be capable to carry the payload of five kilograms



·         Control and command

o   Shall provide wireless radio or satellite communication with ground station

o   Shall have the capability to detect and avoid other manned aircraft

o   Shall have capacity to be operated at line of sight in case the radio signal or satellite communication doesn’t work in remote regions



·         Payload

o   Electronic sensor that can “see” through smoke to detect people or animal on the ground

o   hot spot and provide GPS coordinate of the hot spot

o   Shall be capable of carrying and spraying a small amount of fire distinguisher that is enough to kill the fire with 10 feet diameter to save lives if other airplanes are not available.

o   All payload shall have fire protection coating



·         Datalink

o   Shall use power provided by air vehicle element

o   Shall be capable of communicate with the ground station with the range of five miles.

o   Shall be capable to send real time pictures of hot spots and their GPS coordinates to the ground control station

o   Shall have



o  


·         Transportability

o   The entire system shall be transportable in a hardened case with the size fit in a regular van or large four wheel drive truck

o   The total weight including the payload shall be less than 100 lb, assuming two people can carry and move the case.  



Testing:

·         Reliability

o   Each subsystem shall be tested separately.

o   Although Bell 407 is a mature helicopter with more than 1, 400 airframes produced and over 4 million flight hours, the modified and minimized version of Bell 407 shall be treated as a new platform that need both ground test and in-flight test.

·         Ground test:  5000 hours is required and failure rate is less than 10%

·         In-flight test: 5000 hours is required and failure rate is less than 1%.

·         Environmental test

o   Different altitude to simulate the mountain area or seal level

o   Shall have the capacity to fly in the hot Desert area,

o   Shall have the capacity of stable flying through high wind area

o   Shall have the capacity to fly through dense smoke area with constant communication to the ground station at the same time.  Less than 5% glitches or dropped communication in this test is allowed. 

·         Launching and retrieving rate

o   Shall meet 10 minutes requirement from opening the case to the RobinRobin get airborne.

o   Shall allow only two people to operate the launching and retrieving during the test, without any helpers or tools that is not included in the design



In summary, the RobinRobin is a new affordable fire scout and fire extinguisher that helps experts to detect, control, and extinguish wild fires and save lives.  It has capacity to see through the smoke, provide location of hot spots, and drop chemicals at small area if needed. It is easy to operate and only need two people to operate.  The development phase is 14 months minimum, and with ongoing operation support and large volume production in the coming years.





Saturday, May 7, 2016

UAS system engineer response to conflicts










                                                                                       



Jingwen Cai
System Engineering
ASCI 530 Unmanned Aircraft System Assignment 2
Embry Riddle Aeronautical University



Abstract
This paper is a response to a system’s question in an assignment from the UAS class.  It explains how much knowledge the writer learned as a system engineer and how to apply the knowledge to solve an UAS overweight problem during the design phase. This paper includes the writer’s considerations, priorities and the thought about the future prospects for the “next generation, enhanced” version of the system.









Key word:
System engineering, life cycle process, process flow chart, allocation requirement, verification and validation, integration, trade off study, Vee model.




A general definition of what is a system and what a system engineer does is best explained in Systems Engineering Fundamentals, a book developed by the System Management College from the Department of Defense.  It states that systems engineering is an interdisciplinary engineering management process that evolves and verifies an integrated, life-cycle balanced set of system solutions that satisfy customer needs.
A simplified process flow chart showing the key functions between the system input and out. It shows that the functional analysis and allocation, system balance, and requirement analysis are integrated part of the system management.
Source: System Engineering Fundamentals, p6. Depart of Defense System Management College.
As the System Engineer for a UAS that is designed for precision crop-dusting, we started the life cycle process with conceptual design to understand user requirements, and develop a system concept and validation plan. Then we developed system performance specification, functional specification, “build to” technical manuals, allocated specification, and system validation plan. 
It seems we have capable teams that carried out the detail design at each sub-system, and our design is on schedule and below budget.  However, during the review meeting per the validation plan, we found that two subsystem has a design feature-the weight, over allocated requirement.  
Weight is a key feature for a UAS system because it impact the payload, the wing load, the thrust requirement, the landing and launching systems. So we allocated the total weight into multiple lower level weight requirement for each subsystem.  The allocation requirement is not ambiguous, but clearly written in the flow chart, and in each subsystem’s design expectation package.
If these two over weighted subsystem don’t cut off their excess weight, then either we have to reduce the fertilizer carrying and spraying system, or cut into the fuel margin. Neither of these two choices is in favor of our system’s final performance.
As a system engineer, I am expected not to be bias or in favor of one over the others, and I am also responsible for deliver this design project to meet customer requirement. My consideration is that the voice of the customer is the priority, because they pay the bills for this design and counted on us to deliver. The good news is that I have some tools from my system engineering training to help me to weed out the designs that are not helping us to meet customer need.
First, we have the flow chart and design requirement that have all the subsystems grouped and their allocation specification documented in order to meet the total performance. By checking the weight control parameter, which is key design characteristic labeled on the flow chart, I brought the team together and performed an analysis. I put red color dots on the subsystem that are over weighted-the Guidance, Navigation & Control subsystem, and the Payload delivery subsystem.
One of the tools in the system engineer’s tool box is the “Vee” model. This model highlights the need to define verification plans during requirements development, the need for continuous validation with stakeholders. Our stakeholders are marketing manager, subsystem designer, safety engineer, product assurance and others. We kept asking ourselves if we made what we said we were going to make, or are we giving the customer what they want or need?
So, I bring our marketing manager to the meeting, and she explained that she already talked to customer about the new design and promised that our specific UAS will carry sufficient weight to spread the specified amount of fertilizer over the specified area.  Customer is happy with this idea and looking forward to put more orders if we can deliver.  The marketing manager also mentioned that there are two other competitors that are bidding for this project, but they carry much less fertilizer, which means more trips for the customer to spray the same size of the area, and cost more fuel money and time for the customer.
With that said, I showed the calculation of the weight of the fuel that is required to fly this UAV to the specified area, and had airframe designer, the power plant designer, and launching and retrieving subsystem.  They chose the fixed wing horizontal take off and launching system to have more aerodynamic lift during cruising while using minimum fuels. They also chose the high efficiency power plant to save the fuel.  Instead of 4 piston engine, they chose 2 piston engine to reduce the weight, but use higher Aspect Ratio wing design.  They also chose the carbon fiber composite material for fuselage and wings with hollow honey cone design to reduce the total weight of the airframe without losing the structure strength and pay load capacity.  These designer come out with great ideas showing how much extra effort they put in to modify and improve their subsystem to ensure the weight is within the limit.
Part of the responsibility for a system engineer is to perform trade-off studies pertaining to the best approach in responding to the functional requirements. First, we identify the problem by diving in the over weighted subsystem, and found out that they have attempted to save cost by purchasing off the shelf hardware, rather than a custom design. The GPS system, the guidance and control system from the off the shelf product are for larger airplanes and median altitude and all weather condition, which is not a necessary for the crop dust purpose.
Then we followed the trade-off process to have brain storming to list all the alternatives that the team can think of, and evaluate the wide ranges of the alternatives one by one.  
Zooming into the end user’s point of view, we found out that the environment that the dust crop UAS will be working in is at very low attitude, just a few meters above the crops. This ensures the mist from the spray equally spread out and reach the crops before the mist bumped into each other and become drops. Also this UAS will not be operated in windy days, nor in rainy days, because the rain will wash the fertilizer away from the leaf and stem and flowers.  All these factors helps to reduce the requirement for airframe structure to contour the air turbulence and cold temperature for high altitude. So the airframe subsystem may contribute some of the weight allocations. That is a good news for other subsystems that need more allocation for weight.
The end user of the UAS doesn’t need the low-light-level cameras, or the thermos imagers, because it will be operating in day time with good views from the ground operator. Those images were intended for giving the image back to the control station for analysis, and adjustment of the fly route based on the image. Corp fertilizer will be sprayed within a known boundary and landscape, it doesn’t need an image feedback to determine where to fly to.  If the farmer doesn’t have the geographic data for his crop land yet, he may remove the fertilizer tank and spray system, and put a video camera on the UAV to do surveillance.  Once the data is collected, it can be used for several years as long as the land and area is not changed.  The fertilizer spray mission will only carry the fertilizer and fly through a fixed course year after years on the same land, without a camera on the UAV.  But those cameras are part of the guidance system in the off-shelf product that caused over weight.  The design engineer could remove those cameras to reduce the weight by modify the off the shelf product toward our need. This takes advantage of low price of the off the shelf product, but also help us to reduce the weight in guidance and navigation subsystem.
The guidance system from the off-self product has a GPS and gyroscope build in but the crop dust UAV may not need it. It has known grid of the land scope for which area to be sprayed, so a way-point navigation system is a choice.  Input the instruction to preprogramed chip, to command th4e UAV fly ton a selected bearing at a selected speed and altitude until all way points are visited. This tailored design reduced the total weight of the guidance and control system.
By visiting some spray nozzle suppliers, and compared the weight and performance of more than 20 types of the spraying systems, there is a light weighted high pressure system enlightened the mechanical engineer, who comes out a new spray nozzle that with metal piece only in the nozzle channel and spiral track, but plastic with a hallow structure in the other part of the nozzle to reduce the vibration during the spray. This design reduced the weight of off the shelf spray system because plastic with honey cone design is much lighter.
The final step of the trade-off study is eliminating alternatives which do not appear to meet requirements, or eliminating alternatives with low probability of successful implementation. This step is also called “weeding out” by some text books. I used the quantified the criteria by assign a weighting percentage for each alternative, and asked the team to give their number based on the performance, weight, reliability, producibility, safety, affordability, schedule. Then I multiply their number with my weighting percentage, and get a weighted index for each alternatives we listed. The lower score will be eliminated.
After eliminating a few alternatives by using the weighted criteria index, we selected the most balanced system and resolved the conflicts of the weight allocation among the subsystems. 
My thought about the future prospects for the “next generation, enhanced” version of the system is that reducing the payload for guidance, navigation and control by design an integrated circuit chip that is weighted only 1% of the total payload of the corp dusting UAS, and a more efficient and light weighted spray nozzle that weight only 5% of the total payload. This will allocate majority of the payload to the fuel and fertilizer that benefit the end user of this kind of UAS.  With today’s technology, the circuit design is possible and production of this kind of chip is affordable if the sales volume is large.  I am positive to get more business for this new design because end user will find out that this UAS can spray the fertilizer with longer endurance flight (carrying more fuels) and precision of where and when to spray how much.




Reference:
Austin, R. Unmanned Aircraft Systems. Wiley. 6th edition. P128-p.170.
Agriculture UAV crop duster sprayers. Retrieved on May 6th, 2016 from http://www.uavcropdustersprayers.com/
Boeing Company. Trade study process. Module J.  Retrieved on May 6, 2016 from http://soliton.ae.gatech.edu/people/dschrage/TAI/SE-J_Trades_Studies.pdf
Borror, C. The Certified Quality Engineer Handbook. 3rd edition. P.126.
Gilsman, P. Systems Engineering and Safety: Building the Bridge. P 7.
SYSTEMS ENGINEERING FUNDAMENTALS - SUPPLEMENTARY TEXT PREPARED BY THE DEFENSE ACQUISITION UNIVERSITY PRESS FORT BELVOIR, VIRGINIA 22060-5565.  2001. p.3, & p.6. Retrieved on 5/6/2016 from http://ocw.mit.edu/courses/aeronautics-and-astronautics/16-885j-aircraft-systems-engineering-fall-2005/readings/sefguide_01_01.pdf






Sunday, May 1, 2016

History of UAS

History of UAS
The Unmanned Aerial System has been evolved as the technology break through were introduced and military demand persisted. Each subsystem is selected and designed carefully to ensure the overall UAS performance.  Many development milestones from many countries and companies that lead to today’s multiple purpose UAS.  It is estimated that the UAS market cap will be over billions of dollars a year because the technology of the UAS have been developed so fast that high power, low price and simple operation UASs are available for commercial and civilian uses in recent years.  Most of the civilian drones are carrying a camera to transfer images back, while some are carrying chemicals to treat corps.  Military uses UASs that can take images through the cloud via Synthetic Aperture Radar (SAR) systems on long range high altitude UASs for surveillance or reconnaissance missions.
In the 2000s, a good example of the UAS at this time period is Predator B, or ‘Reaper’ which modified from the MALE systems into a HALE system and into Predator C.  It has the payload mass of 1363 kg that can carry a range of research equipment for automation, sense-ad avoid, or internal weapons. In addition, the Predator C has a ceiling of 20,000 meter, maximum speed of 740 km/hr, endurance longer than 18 hour, and stealth capability.
Compare to the early UAVs before 1970, for example, the ‘Ryan Firebee’ (later Teledyne-Ryan). The similarity is that the unmanned air vehicle are equipped with payloads, navigations and communication systems, and need a control station and a launch and recovery method.  They are sent to the DDD situation to complete a specific mission.  The other similarity is that both are built in USA and driven by Military need to send a UAV in DDD environment.
The difference can be listed one by one. 
First, the power plant for the Firebee is jet-propelled while the Predator has Turbo fan engine with 18kN thrust, which is much powerful for increased endurance and ceiling and range.  The turbo fan technology was not mature in early 1950s. But in the future, electrical powered engine, solar powered engine, or rocket engine UAVs might come into the market.
Second, the Firebee carried still cameras for reconnaissance purpose over enemy territory, but the photographs were developed at base after the return of the UAV. In contrast, the Predator uses Synthetic Aperture Radar and a forward-looking infrared  (FLIR)  that can ‘see’ through clouds and works on both day time and night time. This allows the Predator ability to fly at high altitude to avoid detection and ground fire, while taking the images on the ground surface. In the future, the instant video and thermos images could be sent to the internet in real time.  Your ipad or iphone can receive the instant streaming of the data from the UAS.
Third, the Firebee is controlled via direct radio line of sight (LOS) from a ground control station, or a stand-off manned aircraft, while the Predator is equipped with modern GPS that provide accuracy and less payload, and equipped with satellite communication to allow fast and real time broad band two way communication. 
Fourth, the Firebee doesn’t have much automation and computer work, while the Predator has fast computer systems, network centric operations.  In the future, the UAS could be an autonomy system that has its own brains to made decisions during the mission. This might remind readers of some Sci-fi movies or novels with machine taking control over human.  It could be happening but need careful control and risk analysis.
Fifth, the Predator has stealth capability while the Firebee don’t.  Thanks to the material science development and the shape of the airframe design. ‘Invisible’ flying object could be true in the near future.
Sixth, the name of ‘Firebee’ is from the 1950s when this UAS was developed to carry bombs for release onto ground targets. Due to the limitation of the technology at that time, the accuracy of the aiming at the target is low, although it is much more accurate than radio guided missiles built at that time.  The Predator can fire a laser-guided missile from the high altitude and shot at a moving car on the ground.
Seventh, the launching of the ‘Firebee’ is from the pylon of a midair C130 or other airplane, and when it is done, the Firebee will deploy a parachute and flowing in the air or floating on the ocean surface to wait to be picked up either by helicopter in air or a boat on water. The Predator has a take-off and landing length about 2,000ft on a semi-prepared surface.
Looking forward, the new technology such as artificial intelligence, UAV GPS communication (for sense-and avoid purpose), real time video and image transmission via internet, and satellite communication will be more popular in modern UAVs. The market is demanding cheaper and easier to use UAVs with high end technologies, so the designer and manufacture of the UAV will focus on applying the new technologies in to the UAVs.  For example, The DJI phantom, a VTLO UAV has been updating its technology every year with DJI inspire, DJI F550 and more to come.   




Reference:
Predator C Avenger RPA. Retrieved on 5/1/2016 from http://www.ga-asi.com/predator-c-avenger
Austin, R. Unmmaned Aircraft Systems. Wiley Publickation. Chap 28.
Predator RQ-1/ MQ-1/MQ-9 Reaper UAV, United States of America. Retrieved on 5/1/2016 from http://www.airforce-technology.com/projects/predator-uav/
Tarantola, A. Aug 2013. The Ryan Firebee: Grandfather to the Modern UAV.  Retrieved on 5/1/2016 from http://gizmodo.com/the-ryan-firebee-grandfather-to-the-modern-uav-1155938222
3 Drones Stock to Watch in 2016. Retrieved on 5/1/2016 from http://www.fool.com/investing/general/2015/12/21/3-drone-stocks-to-watch-in-2016.aspx