Purpose of this change

This proposal is for a Temporary change to the notified airspace design, for which a scaled airspace change process applies and a change level is not applicable. The detailed process requirements are published in Part 1a of CAP 1616.

The overall objective of Project Arrow is to enable safe, automated BVLOS flights of multiple unmanned aircraft within the coverage area in Reading in Non-Segregated Airspace.

Recognising that the specific functions that need to be tested, and that within this there are specific detect and avoid’ capabilities of the solution, we, therefore, propose the following objectives:

• To verify the efficacy of our chosen surveillance/aircraft detection systems and visual systems to deliver a recognised air picture for the entire area of coverage;

• Proving that the GuardianUTM system has the capability to safely act as an offboard automated deconfliction service using the data


• The recognition of the Arrow Drone Zone and Arrow Tower concepts as approved for automated, BVLOS operations for vehicles that are appropriately connected and comply with our operating specifications and procedures.

• To trial the technology under VLOS, EVLOS, BVLOS Segregated and BVLOS non-segregated Airspace in that order.

Altitude Angel has been working with the Innovation Sandbox for the last 14months, working on the requirements to prove and certify a new type of Detect and Avoid Technology (DAA) that will be used under Future Flight Project Xcelerate

The DAA, once certified, will enable BVLOS Operations in uncontrolled airspace without the requirement for closed airspace and support a more integrated approach moving forwards.

For us to prove this technology, we require airspace that will allow manned and unmanned to be operational while under BVLOS operations and allow the DAA technology to identify and track both types of aircraft.

Operations will be undertaken at 400ft AGL for flights, and we anticipate that the policy team will request the airspace to be surface to 1000ft. We would be comfortable with 800ft. Thus reducing the impact on local GA

The time of operations will be daylight hours only for the moment. Period of 6 Months

As part of this project, we will also be undertaking public perception engagement, noise impact studies etc.

CAA response to Step 1

Documents for this proposal (7 documents)

Stakeholder Engagement Evidence Report

Step 1 - Engagement Evidence

Date added: 06 August 2021 16:24


Step 1 - Engagement Evidence

Date added: 05 August 2021 13:02

Stakeholder Engagement Letter V4

Step 1 - Engagement Evidence

Date added: 08 July 2021 14:05

Presentation From Assessment Meeting V2

Step 1 - Assessment Meeting Minutes

Date added: 02 July 2021 15:25

Updated Statement Of Need Redacted

Step 1 - Statement of Need

Date added: 29 June 2021 16:03


Step 1 - Assessment Meeting Minutes

Date added: 28 June 2021 14:21

Statement of Need Redacted

Step 1 - Statement of Need

Date added: 24 June 2021 13:42


Potentially Affected Area

This is the area which may be affected by this airspace change depending on its development. This area may change as the proposal is developed.

Step 1 : Assess Requirement

This step has been started

During the Assess Requirement Step, the change sponsor prepares a Statement of Need setting out what airspace issue it is seeking to address. Having reviewed the Statement of Need, the CAA meets with the change sponsor to agree whether an airspace change is a relevant option to consider, and to have a first discussion about the appropriate scale of the airspace change process.

Back to previous page