Remotely Piloted Air Systems – Current and Future UK Use
Total Page:16
File Type:pdf, Size:1020Kb
House of Commons Defence Committee Remote Control: Remotely Piloted Air Systems – current and future UK use Tenth Report of Session 2013–14 Volume II Written evidence Ordered by the House of Commons to be published 11 March 2014 Published on 25 March 2014 by authority of the House of Commons London: The Stationery Office Limited The Defence Committee The Defence Committee is appointed by the House of Commons to examine the expenditure, administration, and policy of the Ministry of Defence and its associated public bodies. Current membership Rt Hon James Arbuthnot MP (Conservative, North East Hampshire) (Chair) Mr Julian Brazier MP (Conservative, Canterbury) Mr James Gray MP (Conservative, North Wiltshire) Rt Hon Jeffrey M. Donaldson MP (Democratic Unionist, Lagan Valley) Mr Dai Havard MP (Labour, Merthyr Tydfil and Rhymney) Adam Holloway MP (Conservative, Gravesham) Mrs Madeleine Moon MP (Labour, Bridgend) Sir Bob Russell MP (Liberal Democrat, Colchester) Bob Stewart MP (Conservative, Beckenham) Ms Gisela Stuart MP (Labour, Birmingham, Edgbaston) Derek Twigg MP (Labour, Halton) John Woodcock MP (Labour/Co-op, Barrow and Furness) The following Members were also members of the Committee during this inquiry. Thomas Docherty MP (Labour, Dunfermline and West Fife) Penny Mordaunt MP (Conservative, Portsmouth North) Sandra Osborne MP (Labour, Ayr, Carrick and Cumnock) Powers The Committee is one of the departmental select committees, the powers of which are set out in House of Commons Standing Orders, principally in SO No 152. These are available on the internet via www.parliament.uk. Publications The Reports and evidence of the Committee are published by The Stationery Office by Order of the House. All publications of the Committee (including press notices) are on the internet at www.parliament.uk/parliament.uk/defcom. The Reports of the Committee, the formal minutes relating to that report, oral evidence taken and some or all written evidence are available in a printed volume. Additional written evidence may be published on the internet only. Committee staff The current staff of the Committee are James Rhys (Clerk), Dougie Wands (Second Clerk), Karen Jackson (Audit Adviser), Ian Thomson (Committee Specialist), Christine Randall (Senior Committee Assistant), Rowena Macdonald and Carolyn Bowes (Committee Assistants). Contacts All correspondence should be addressed to the Clerk of the Defence Committee, House of Commons, London SW1A 0AA. The telephone number for general enquiries is 020 7219 5745; the Committee’s email address is [email protected]. Media inquiries should be addressed to Alex Paterson on 020 7219 1589. List of written evidence (published in Volume II on the Committee’s website www.parliament.uk/defcom) 1 Ministry of Defence Ev w1 2 Royal United Services Institute (RUSI) Ev w11 3 The Baptist Union of Great Britain, The Methodist Church and The United Reform Church Ev w14 4 Thales UK Ev w20 5 ADS Ev w24 6 James Earle on behalf of the Association of Military Court Advocates Ev w26 7 Bureau of Investigative Journalism Ev w31 8 Network for Social Change Ev w37 9 Northrop Grumman Corporation (NGC) Ev w40 10 Dr David Goldberg Ev w46 11 Drone Wars UK Ev w50 12 Royal Aeronautical Society Ev w51 13 Defence Synergia Ev w56 14 Research Councils UK (RCUK) Ev w60 15 All Party Parliamentary Group on drones Ev w70 16 Public Interest Lawyers on behalf of Peacerights Ev w79 17 General Atomics Aeronautical Systems, Inc. (GA-ASI) and General Atomics Aeronautical Systems United Kingdom Ltd (GA-UK) Ev w99 18 Stefan Wolff, Professor of International Security, University of Birmingham Ev w107 19 MBDA UK Ltd Ev w117 20 Reprieve Ev w117 21 Professor Nicholas Wheeler, Institute for Conflict, Co-operation and Security, University of Birmingham Ev w124 Defence Committee: Evidence Ev w1 Written evidence Written evidence from the Ministry of Defence 1. Introduction 1.1 This memorandum provides written evidence for the House of Commons Defence Committee’s Inquiry into Remotely Piloted Air Systems—current and future use. 1.2 Drawing on the Ministry of Defence’s (MOD) experience of owning and operating these systems, it will examine: — Nomenclature—defining associated terms. — Current use and Dispersal—explaining what the MOD uses these systems for and where? — Lessons on their use from Afghanistan. — Tomorrow’s Potential—detailing MOD plans for their development. — Constraints—commenting on constraints imposed by Airspace Regulation and the environment. — Legal and Ethical issues. 2. Nomenclature—Defining what is meant by the Terms Remotely Piloted Air Systems (RPAS), Unmanned Aircraft Systems (UAS) and Associated Terms 2.1 The origins of unmanned aircraft can be traced back to the First World War. But the last decade has seen extraordinary development and rapid progress in unmanned aircraft technology and capability. Much of the original terminology has, as a result, become outdated and manufacturers and operators have created a new descriptive language for the aircraft, their capabilities and consequent issues. As systems have matured, there is also an increasing requirement for standardised terminology. 2.2 To help avoid confusion and prevent misunderstanding, in 2010 and 2011, the MOD produced Joint Doctrine Note (JDN) JDN 3/10—Unmanned Aircraft Systems (UAS): Terminology, Definitions & Classification and JDN 2/11—The UK Approach to UAS. These documents outline the standard UK military terminology and classification to be used when describing UAS within UK Defence and when working with NATO and other international partners. UK based academia and industry are encouraged to adopt the standard to improve interoperability. Both JDNs are in the public domain and can be accessed through the Defence section of www.gov.uk. 2.3 The term Unmanned Aerial Vehicle (UAV) had previously been used extensively in the UK. But it is no longer aligned with NATO thinking and, in the interests of interoperability, UAV should now be considered a legacy term. A recent NATO Joint Unmanned Aerial Vehicle Panel was tasked to re-examine unmanned aircraft related terminology from first principles and to make recommendations on the way ahead; JDNs 2/11 & 3/10 largely reflect the outcome of that discussion and subsequent recommendations. 2.4 The following are terms defined in JDNs 2/11 & 3/10: 2.5 Unmanned Aircraft (UA) An Unmanned Aircraft (sometimes abbreviated to UA) is defined as an aircraft that does not carry a human operator… 2.6 Unmanned Aircraft System (UAS) An Unmanned Aircraft System (UAS) is defined as a system, whose components include the unmanned aircraft and all equipment, network and personnel necessary to control the unmanned aircraft. 2.7 UAS is the generic term that defines the totality of the components of an unmanned aircraft, together with the other necessary components including all equipment, networks and personnel. The MOD operate a range of UAS principally for surveillance and reconnaissance purposes. 2.8 Although UAS is the preferred term in a military environment, there are occasions when such a generic term is unhelpful. The term “unmanned” can cause confusion or uncertainty over the actual level of human control and has led to safety, ethical and legal concerns being raised, particularly with regard to the employment of weapons and flight in non-segregated airspace. These concerns can be addressed in part by using terminology that better describes the level of human control of such aircraft as being equivalent to that of piloted aircraft; the pilot is simply physically remote from the aircraft itself. Consequently, the MOD believes it is more appropriate to use the term Remotely Piloted Aircraft (RPA) to describe such aircraft, and Remotely Piloted Air(craft) System (RPAS) to describe the entirety of that which it takes to deliver the overall capability. 2.9 Remotely Piloted Aircraft A Remotely Piloted Aircraft is defined as an aircraft that, whilst it does not carry a human operator, is flown remotely by a pilot, is normally recoverable, and can carry a lethal or non-lethal payload. Ev w2 Defence Committee: Evidence 2.10 Remotely Piloted Air(craft) System (RPAS) A Remotely Piloted Air(craft) System is the sum of the components required to deliver the overall capability and includes the Pilot, Sensor Operators (if applicable), RPA, Ground Control Station, associated manpower and support systems, Satellite Communication links and Data Links. 2.11 RPAS is thus a specific class of UAS. It is appropriate to use the term RPAS to emphasise the reality that a trained professional pilot is in control of the system. Of note, the critical legislative aviation authorities, the International Civil Aviation Organisation (ICAO) and the European Aviation Safety Agency use the term RPAS. 2.12 Unmanned Combat Aircraft System (UCAS): UCAS is a proposed class of UAS with offensive and defensive capabilities on a par with current manned systems to allow them to operate in contested airspace when necessary. Such a capability does not yet exist. 2.13 Automation and Autonomy. There is often a misconception that UAS are autonomous systems. This is not true as there is always a human involved in the decision making process. Industry and academia often discuss automation and autonomy interchangeably, referring to technology research for all types of UAS. There are no universally agreed definitions. But the MOD defines autonomy as a machine’s ability to understand higher level intent, being capable of deciding a course of action without depending on human oversight and control. Automation refers to a system that is programmed to logically follow a pre-defined set of rules with predictable outcomes, such as an automatic landing system. Improving capability can include automating part of a process to make the remote Pilot or operator’s job easier. But current UK policy is that the operation of weapon systems will always be under human control. No planned offensive systems are to have the capability to prosecute targets without involving a human.