AGENDA INTRODUCTION & PERSPECTIVE RPAS ACC. REQUIREMENTS EXTRACTION RPAS MALE HALE ACCOMMODATION RPAS CONTINGENCIES CONCLUSION
PRINCIPLES FOR RPAS ATI RPAS integration without significant impact on other users IMPACT TO OTHER USERS, SAFETY RPAS integration without LEVELS compromise/increase AND RPAS TRANSPARENSY HAVE existing TO BE CAREFULLY ASSESSED aviation safety levels RPAS specifics transparent to ATC and other users
ICAO PRINCIPLES RPA operated with the authorization issued by each State overflown (Agreement) RPA operated over the high CROSS seas BORDER with prior AGREEMENTS, coordination with ATS authority RPAS operated in accordance with conditions specified by: - the State of Registry - the State of the Operator (if different) - the State(s) overflown DUE REGARD COORDINATION, SPECIFIC CONDITIONS AND LICENCE REQUIREMENTS HAVE TO BE CAREFULLY AGREED Licences of remote pilots issued or rendered valid by the licensing authority of the State in which the RPS is located
FIRST ISSUE HARMONIZATION PROCESS MIL (OAT) - CIV (GAT) RULES Airspace assessment Risk assessment Operational procedures Diploclearances / Flight notification Flight planning Transponder No overfly of populated areas LOTS OF PAPER WORKS AND QUESTIONABLE RAPID C2 AIRSPACE ACCESS Pilot license Dynamic flight corridors Airport requirements Incident investigation
N1 Land Immediately LI N2 Land ASAP LASAP N3 Land on suitable airfield - LOSA ASSUMPTIONS: AW: platform airworthy C4ISTAR: no inpact FS: no inpact AEROSPACE MED: no inpact AVIATE NAVIGATE AIRCRAFT RPAS LEVEL INTEGRATE SYSTEM REQUIREMENT EXTRACTION PROCESS R = L x I = f(a, T, V, I) A = Value of the assett; T = probability of the threat; V = vulnerability exploitation (proportional to the advantage for the adversary and inverse to the cost ot its exploitation); I = expected impact and damage extension.
AGENDA INTRODUCTION & PERSPECTIVE RPAS ACC. REQUIREMENTS EXTRACTION RPAS MALE HALE ACCOMMODATION RPAS CONTINGENCIES CONCLUSION
PREVENTION BARRIERS BOW TIE MODEL System Failure MITIGATION BARRIERS POTENTIAL CAUSES Threat Threat Opportunity Opportunity A,N,I 1-2-3 BEFORE Operational Hazard EVENT Navigate AFTER Intelligent Resistance N1 N2 N3 NH Benefit Benefit Harm NB Harm LOSA LASAP LI POTENTIAL OUTCOMES LIKELIHOOD MANAGEMENT PROACTIVE CONTROL (COMPLICATED ENV.) CONSEQUENCE MANAGEMENT REACTIVE CONTROL (COMPLEX ENV.)
RPAS CONTINGENCY COORDINATION MATRIX FLIGHT PHASE OR AIRSPACE N1 LI N2 LASAP N3 LOSA NH NB PP - PT OTMV* PEAK - SUSTAINED EXAMPLES GROUND TAXY N1 RPAS squawk 7700 starts descend and turn LAUNCH N2 slight right or left PT TRANSIT N3 coordinated or as planned TRAINING NH reduce speed speed PT to PH OPERATIONS NR 30 for 1 minute right THEN left RECOVERY GROUND TAXY *OTMV: Occupancy Counts Monitoring Value
ATI FUTURE TECNOLOGICAL EVOLUTION 1. The RPAS shall be able to operate in all types of segregated airspace. (NO DESIGN ISSUE) 2. The RPAS shall be able to operate as IFR in all non-segregated airspaces when and where only cooperative air traffic is allowed and separation from all other traffic is under the responsibility of ATC (Class A to C) (COOPERATIVE CA as safety net) 3. The RPAS shall be able to operate as IFR in all non-segregated airspace when and where only cooperative air traffic is allowed and separation from VFR traffic is not under the responsibility of ATC (Class D) (COOPERATIVE VFR RWC/VFR TRAFFIC SITUATION AWARENESS COOPERATIVE DAA) 4. The RPAS should include provisions to ensure compatibility with the applicable capabilities foreseen in the Single European Sky as defined in the ATM Master Plan. (RPAS certified PBN, RCP, RSP, RNP) 5. The RPAS shall include provisions to be able to operate as IFR in all non-segregated airspace when and where non cooperative air traffic is allowed (Class E to G). (RPAS certified non cooperative DAA)
RPAS ATI SPECIFIC PROCEDURES Command & Control Link loss (C2 Link loss) Degradation of Command & Control Link (NO LOS) Command & Control Link loss combined with external event (Bad weather, Cooperative Traffic, Non-cooperative traffic) Command & Control Link loss combined with internal event with effect on flight plan/predictability (Environmental Control failures, Fuel System Failures, Flight Management Failures) Internal event (loss of thrust) requiring access to non-cooperative airspace (enroute-mission) Loss of thrust during take off and departure No GNSS procedures
RPAS SEGREGATED AIRSPACE SPECIFICITIES RPAS goes out of the corridor intruder (A/C in emergency) enters the corridor or the airspace specific buffer for RPAS corridors and specific separation criteria outside of segregated airspace Specific RPAS categorization and TERPs RPAS DUE REGARD requirements over the high seas: Normally VMC (visual obeserver.) Airborne radar if IMC Ground/Airborne Surveillance (flight plan and ATC approval normally not required) System requirements for sufficient self separation (air risk mitigation) Remark: contingency management
POSSIBLE «OPERATIONAL» WAY AHEAD evolve rules of priority (manned vs RPAS, IFR vs VFR, RPAS in contingency vs manned) evolve airspace classification and rules of the air considering aspect angle, speed, performance and latency in order to determine future ATI procedures RPAS loitering points (low density airspace orbit points near low density population areas) improve collaboration between civilian and state aviation agencies in elaborating contingency procedures develope RP IOAT rules (IT CAM draft study released)
AGENDA INTRODUCTION & PERSPECTIVE RPAS ACC. REQUIREMENTS EXTRACTION RPAS MALE HALE ACCOMMODATION RPAS CONTINGENCIES CONCLUSION
RP OPS INTEGRATION CONCLUSIONS Merge Integration with AW requirements Experimentation Refine Model System Refine liabilities and investigation procedures Refine RP OAT rules Refine SF, OH, IR Refine Safety Objectives Refine RP Flight, Airport and ATM CNS operations Refine System Consequence Management Refine System requirements
RP OPS INTEGRATION CONCLUSIONS NO PLUG AND PLAY, CHEAP OR DEFINITIVE AW&I SOLUTION NO RAPID ACCOMODATION PROCESSES MIL FoM NECESSITIES vs CIV SES INITIATIVE NO LOW HANGING FRUIT