00:00:03.040 --> 00:00:06.640

Airservices Australia is Australia's

air traffic management

00:00:06.640 --> 00:00:09.880

and aviation rescue

firefighting service provider.

00:00:10.360 --> 00:00:13.160

Our primary focus

is ensuring the safety of air

00:00:13.160 --> 00:00:16.160

travel, both in the air and on the ground.

00:00:16.200 --> 00:00:20.240

Aircraft arriving at and leaving Brisbane

use a network of flight

00:00:20.240 --> 00:00:23.920

paths designed to ensure a safe

and efficient flow of traffic.

00:00:24.400 --> 00:00:27.960

These paths were updated in July 2020

to support

00:00:27.960 --> 00:00:31.000

the introduction of the new runway

at Brisbane Airport.

00:00:32.240 --> 00:00:36.600

A year after the opening of the new

runway, Airservices conducted a post

00:00:36.600 --> 00:00:41.520

implementation review to evaluate how

the new airspace design was going.

00:00:42.360 --> 00:00:45.160

The review found that people

were concerned about where

00:00:45.160 --> 00:00:48.960

and how often flights are passing

over the city and suburbs.

00:00:49.480 --> 00:00:51.240

Some community members expected

00:00:51.240 --> 00:00:54.000

more flights to go over

Moreton Bay instead.

00:00:54.360 --> 00:00:56.120

To address these concerns,

00:00:56.120 --> 00:00:58.560

Airservices created the Noise Action

00:00:58.560 --> 00:01:02.200

Plan for Brisbane,

which involves four work packages.

00:01:02.920 --> 00:01:08.640

Package one: Establishing strong,

transparent and representative project governance.

00:01:09.080 --> 00:01:12.360

Package two: To maximize flights

over the water.

00:01:12.800 --> 00:01:15.240

Package three: Reduce the frequency

00:01:15.240 --> 00:01:18.280

and concentration of flights over

communities.

00:01:18.280 --> 00:01:23.120

And package four: To optimize the performance

of the wider Brisbane airspace system.

00:01:24.000 --> 00:01:27.680

Brisbane is served by a large and complex

airspace system.

00:01:28.200 --> 00:01:31.840

The arrival and departure paths

that serve Brisbane interact

00:01:31.840 --> 00:01:36.960

with the wider airspace and the flight

paths to and from other nearby airports.

00:01:37.920 --> 00:01:40.560

Many of the flight

paths are interconnected.

00:01:40.560 --> 00:01:43.560

Making changes

that will share noise in one area

00:01:43.800 --> 00:01:46.680

will often affect traffic flows elsewhere.

00:01:46.680 --> 00:01:49.680

A holistic approach is required.

00:01:49.800 --> 00:01:53.200

Managing these connections

involves making trade-offs

00:01:53.200 --> 00:01:58.840

that may result in benefits for some areas

but not others, or new negative impacts.

00:01:59.720 --> 00:02:01.880

Maintaining high safety standards

00:02:01.880 --> 00:02:04.880

is paramount and will not be traded off.

00:02:04.880 --> 00:02:09.760

Requiring careful planning and

coordination across all proposed changes.

00:02:10.920 --> 00:02:14.520

Using both runways for landing

and taking off at the same time

00:02:14.720 --> 00:02:18.240

is known as independent

parallel runway operations.

00:02:19.040 --> 00:02:23.400

In order for this to be managed safely,

a number of parameters need to be met.

00:02:24.240 --> 00:02:27.600

The flight paths were designed

to meet the international rule

00:02:27.680 --> 00:02:30.680

set for independent

parallel runway operations,

00:02:30.840 --> 00:02:33.840

but some changes have since

been made to these standards

00:02:33.920 --> 00:02:36.920

and adjustments to the

design are required.

00:02:37.440 --> 00:02:40.560

This forms part of the Noise

Action Plan for Brisbane

00:02:40.680 --> 00:02:44.360

Package three deliverables

alongside the options

00:02:44.360 --> 00:02:48.240

which aim to reduce the frequency

and concentration of overflight.

00:02:49.320 --> 00:02:52.240

Our first step in developing noise

sharing options

00:02:52.240 --> 00:02:55.600

was to create a heatmap

from actual flight track data.

00:02:56.160 --> 00:02:58.600

The heat map shows

where the majority of flights

00:02:58.600 --> 00:03:03.720

are passing over the city and suburbs

in the current two runway airspace design.

00:03:04.600 --> 00:03:06.440

It helps compare the impacts with those

00:03:06.440 --> 00:03:09.240

experienced before the new

runway was introduced,

00:03:09.400 --> 00:03:14.040

and can be used to illustrate the expected

outcome of any proposed changes.

00:03:14.760 --> 00:03:18.480

Using the heat map and community

input received during the post

00:03:18.480 --> 00:03:22.680

implementation review, we have

identified sections of airspace

00:03:22.680 --> 00:03:26.760

that have seen an increase in the frequency

and concentration of flights,

00:03:27.000 --> 00:03:30.800

and examined the potential options

for sharing the impacts.

00:03:32.280 --> 00:03:34.840

In each airspace section, we define

00:03:34.840 --> 00:03:39.080

the broadest range of potential flight

path options that are technically viable.

00:03:39.440 --> 00:03:42.080

Although many may not be desirable.

00:03:42.080 --> 00:03:45.360

By consistently assessing

each of the potential flight paths,

00:03:45.360 --> 00:03:49.720

we can start to compare them

and identify improvement opportunities.

00:03:50.640 --> 00:03:55.920

The performance of each flight path

is evaluated based on overflight contours,

00:03:55.920 --> 00:04:00.280

measuring the total population

over flown out to 25 nautical miles

00:04:00.280 --> 00:04:05.760

from the airport. Population

within 70 decibel and 60 decibel

00:04:05.800 --> 00:04:08.800

single noise event contours.

00:04:08.840 --> 00:04:11.840

Number of track miles

for departures and arrivals,

00:04:12.240 --> 00:04:15.360

and changes to climb or descent gradients.

00:04:16.720 --> 00:04:18.720

Using a database of this performance

00:04:18.720 --> 00:04:22.320

information, we can filter and rank

all the potential flight paths

00:04:22.320 --> 00:04:25.920

to identify the higher

performing options for noise management.

00:04:26.240 --> 00:04:29.880

We then test these flight path

design options against the Airservices

00:04:29.880 --> 00:04:34.040

flight path design principles

and the objective of package three,

00:04:34.040 --> 00:04:37.920

which is to reduce the frequency

and concentration of overflights.

00:04:38.520 --> 00:04:43.320

The options are then presented to industry

and the community to gather feedback.

00:04:44.760 --> 00:04:46.200

We will engage with affected

00:04:46.200 --> 00:04:49.520

communities to gather feedback

on the potential options,

00:04:49.520 --> 00:04:53.840

assess how effectively they reduce the

frequency and concentration of flights,

00:04:54.240 --> 00:04:57.240

and understand the likely

trade-offs of doing so.

00:04:58.360 --> 00:05:02.240

Communities will have the opportunity

to provide feedback on the options,

00:05:02.600 --> 00:05:06.120

influence the development

of the preferred flight path designs,

00:05:06.400 --> 00:05:10.080

and submit additional feedback

to inform the final review stage.

00:05:11.120 --> 00:05:14.760

The goal of the first round of community

Engagement is to collect early feedback

00:05:14.760 --> 00:05:19.160

on a wide range of potential design

options for each section of airspace.

00:05:19.680 --> 00:05:23.360

This helps us to better understand

community views towards key issues

00:05:23.640 --> 00:05:26.400

like aircraft noise

concentration versus noise

00:05:26.400 --> 00:05:30.960

sharing, and gather diverse perspectives

informed by local circumstances.

00:05:31.960 --> 00:05:34.960

Based on insights from community

and industry feedback,

00:05:35.200 --> 00:05:37.920

along with additional data

on the operational

00:05:37.920 --> 00:05:41.040

and environmental impacts

of the potential designs,

00:05:41.160 --> 00:05:44.160

we will refine and update

the flight path options

00:05:44.160 --> 00:05:47.520

focusing on those that best meet

our decision making criteria.

00:05:48.200 --> 00:05:50.200

In the second

round of community engagement,

00:05:50.200 --> 00:05:53.720

we will present more detailed information

about the preferred options.

00:05:54.800 --> 00:05:57.120

The goal of the second round of engagement

00:05:57.120 --> 00:06:00.680

is to collect final views

from the community and industry

00:06:00.800 --> 00:06:05.120

on the preferred options, test

the accuracy and completeness of the data

00:06:05.120 --> 00:06:09.360

and feedback used to make key design

choices, and ensure

00:06:09.360 --> 00:06:13.120

we have identified all opportunities

to optimize the positive

00:06:13.120 --> 00:06:16.120

impacts of a change and mitigate

the negative ones.

00:06:17.080 --> 00:06:20.680

Following the second round of engagement,

we will clearly communicate

00:06:20.680 --> 00:06:25.240

the reasons for the design decisions

we have made, including how trade offs

00:06:25.240 --> 00:06:28.880

were evaluated and the rationale

behind the preferred options.

00:06:29.640 --> 00:06:30.920

Throughout the process,

00:06:30.920 --> 00:06:35.600

we will strive to balance the benefits

and drawbacks across different areas

00:06:35.600 --> 00:06:39.280

with the aim of ensuring

that no single community bears

00:06:39.280 --> 00:06:42.280

a disproportionate

share of the negative impacts.

00:06:43.080 --> 00:06:46.920

This approach ensures that benefits

are balanced across the airspace system,

00:06:47.200 --> 00:06:51.360

and that all affected

communities have a voice in the process.