Posted on

Adelaide Airport Consultative Committee

Federally-leased airports (excluding Mt. Isa and Tennant Creek) have established Community Aviation Consultation Groups (CACGs), which provide an effective avenue for local community engagement on airport planning and operations, including aircraft noise. The Department for Infrastructure, Transport, Regional Development and Communications provides guidelines for CACGs.

Non federally-leased airports may also choose to establish CACGs or community forums.

CACG membership depends on the characteristics of the airport and any local issues of community concern however, generally includes:

  • airport management
  • aircraft operators
  • community organisations or representatives
  • representatives from state, territory or local government bodies
  • local tourism and business groups.

Airservices does not formally belong to CACGs, but is invited to attend to provide relevant information and assist in discussions. We engage with CACGs on flight path and airspace changes, as well as technical reviews, such as noise monitoring and noise abatement procedures.

Find out more information on the Adelaide Airport Community Aviation Consultation Group webpage.

Posted on

Perth and Jandakot Airport Community Consultation

Federally-leased airports (excluding Mt. Isa and Tennant Creek) have established Community Aviation Consultation Groups (CACGs), which provide an effective avenue for local community engagement on airport planning and operations, including aircraft noise. The Department for Infrastructure, Transport, Regional Development and Communications provides guidelines for CACGs.

Non federally-leased airports may also choose to establish CACGs or community forums.

CACG membership depends on the characteristics of the airport and any local issues of community concern however, generally includes:

  • airport management
  • aircraft operators
  • community organisations or representatives
  • representatives from state, territory or local government bodies
  • local tourism and business groups.

Airservices does not formally belong to CACGs, but is invited to attend to provide relevant information and assist in discussions. We engage with CACGs on flight path and airspace changes, as well as technical reviews, such as noise monitoring and noise abatement procedures.

Find out more information on the Perth Airport Community Forum or Jandakot Airport Community Aviation Consultation Group.

Posted on

The Perth Noise and Flight Path Monitoring System (NFPMS)

We collect noise and operational data from six noise monitors (Environmental Monitoring Unit, EMU) around Perth Airport. Noise monitors are listed below according to their location.

Access monthly data on our Perth noise monitoring reports page.

CANNINGTON (EMU 1)

Captures arrivals to Perth Runway 03 and departures from Perth Runway 21.

EMU 1 and EMU 2 are overflown by similar aircraft. However, EMU 2 is located closer to, and aligned with, Runway 03/21, which results in it recording higher noise levels.

QUEENS PARK (EMU 2)

Captures arrivals to Perth Runway 03 and departures from Perth Runway 21.

Along with EMU 5 (Guildford), EMU 2 records the highest noise levels of all the noise monitors in Perth – these two noise monitors are closest to the end of the runways.

GREENMOUNT (EMU 4)

Captures arrivals to Perth Runway 24 and departures from Perth Runway 06.

The seasonal variation in the use of Runway 06/24 is reflected in the values recorded at this monitor.

GUILDFORD (EMU 5)

Captures arrivals to Perth Runway 21 and departures from Perth Runway 03.

Together with EMU 2, EMU 5 records the highest levels of all the noise monitors in Perth. These two monitors are closest to the end of runways and are overflown by both arrivals and departures.

BEECHBORO (EMU 37)

Captures departures from Perth Runway 03.

Noise levels at EMU 37 are lower than at other noise monitors due to it being further from the end of a runway. This noise monitor is set only to capture those departures from Runway 03 that turn to the west.

LATHLAIN (EMU 40)

Captures arrivals to Perth Runway 06 and departures from Perth Runway 24.

The noise levels at EMU 40 are generally low, due to it being aligned with the cross-runway (06-24) at Perth Airport which is used much less than the main runway.

Learn more about monitoring aircraft noise on the Airservices website.

Posted on

The Cairns Noise and Flight Path Monitoring System (NFPMS)

noise and operational data from three noise monitors (Environmental Monitoring Unit, EMU) around Cairns Airport at the following locations.

Access monthly data on our Cairns noise monitoring reports page.

HOLLOWAYS BEACH (EMU 2)

EMU 2 captures arrivals to Runway 15 and departures from Runway 33.

The number of aircraft noise events recorded by EMU 2 reflects the pattern of
seasonal use of Runway 15 for arrivals, with more events recorded in the dry
season than the wet season.

CAIRNS NORTH (EMU 3)

Captures arrivals to Runway 33 and departures from Runway 15.

YORKEYS KNOB (EMU 9)

EMU9 captures mainly arrivals to Runway 15 and departures from
Runway 33.

Although it captures many of the same movements as EMU 2 (Holloways
Beach), EMU 9 is further north and therefore aircraft are higher, resulting in
fewer aircraft generating a noise level above 80 decibels.

Learn more about monitoring aircraft noise on the Airservices website.

Posted on

Hobart Airport community aviation consultation group

Federally-leased airports (excluding Mt. Isa and Tennant Creek) have established Community Aviation Consultation Groups (CACGs), which provide an effective avenue for local community engagement on airport planning and operations, including aircraft noise. The Department for Infrastructure, Transport, Regional Development and Communications provides guidelines for CACGs.

Non federally-leased airports may also choose to establish CACGs or community forums.

CACG membership depends on the characteristics of the airport and any local issues of community concern however, generally includes:

  • airport management
  • aircraft operators
  • community organisations or representatives
  • representatives from state, territory or local government bodies
  • local tourism and business groups.

Airservices does not formally belong to CACGs, but is invited to attend to provide relevant information and assist in discussions. We engage with CACGs on flight path and airspace changes, as well as technical reviews, such as noise monitoring and noise abatement procedures.

Find out more information on the Hobart Airport Community Aviation Consultation Group webpage.

Posted on

Airport community aviation consultation group

Federally-leased airports (excluding Mt. Isa and Tennant Creek) have established Community Aviation Consultation Groups (CACGs), which provide an effective avenue for local community engagement on airport planning and operations, including aircraft noise. The Department for Infrastructure, Transport, Regional Development and Communications provides guidelines for CACGs.

Non federally-leased airports may also choose to establish CACGs or community forums.

CACG membership depends on the characteristics of the airport and any local issues of community concern however, generally includes:

  • airport management
  • aircraft operators
  • community organisations or representatives
  • representatives from state, territory or local government bodies
  • local tourism and business groups.

Airservices does not formally belong to CACGs, but is invited to attend to provide relevant information and assist in discussions. We engage with CACGs on flight path and airspace changes, as well as technical reviews, such as noise monitoring and noise abatement procedures.

Find out more information on the

Melbourne Airport Community Aviation Consultation Group webpage

Essendon Airport Community Aviation Consultation Group webpage

Moorabbin Airport Community Aviation Consultation Group webpage.

Posted on

The Melbourne Noise and Flight Path Monitoring System (NFPMS)

We collect noise and operational data from five noise monitors (Environmental Monitoring Unit, EMU) around Melbourne Airport. Noise monitors are listed below according to their location.

Access monthly data on our Melbourne noise monitoring reports page.

BULLA (EMU 2)

Captures arrivals to Melbourne Runway 16 and departures from Melbourne Runway 34.

Detects more events than the other noise monitor locations due to its proximity to the airport.
The pattern of aircraft noise events recorded reflects the seasonal trends in arrivals to Runway 16, with more events recorded in summer than in winter.

ESSENDON (EMU 4)

Captures arrivals to Melbourne Runway 34 and arrivals to Essendon Runway 35 and departures off Essendon Runway 17.

Seasonal fluctuations in the use of Runway 34 at Melbourne Airport are offset by the opposite fluctuations in the use of Runway 17 at Essendon Airport.

COOLAROO (EMU 6)

Captures arrivals to Melbourne Runway 27.

While the pattern of noise events recorded reflects the seasonal trend for arrivals to Runway 27 the correlation is not precise as there are some parts of the year where for noise abatement purposes, Runway 27 is used more for departures than for arrivals. Departures from Runway 27 do not fly over this monitor.

KEILOR DOWNS (EMU 9)

Captures arrivals to Melbourne Runway 34 and arrivals to Essendon Runway 35 and departures off Essendon Runway 17.

Seasonal fluctuations in the use of Runway 34 at Melbourne Airport are offset by the opposite fluctuations in the use of Runway 17 at Essendon Airport.

KEILOR EAST (EMU 3)

Captures arrivals to Melbourne Runway 34.

The pattern of aircraft noise events reflects the seasonal trend for arrivals to Runway 34, with more events recorded in winter than in summer.

THOMASTOWN (EMU 11)

Captures arrivals to Melbourne Runway 27.

The pattern of aircraft noise events recorded reflects the seasonal trend for arrivals to Runway 27, with more events recorded in winter than in summer. As a result the trend for this monitor mirrors that of Coolaroo monitor.

Learn more about monitoring aircraft noise on the Airservices website.

Posted on

Investigation: Alternative helicopter route to/from airport and reef

In Cairns there is significant helicopter traffic to and from the reef. While helicopters usually track direct between the Cairns Airport helipad and the reef, at times helicopters are tracked over residents to the north of the airport resulting in concerns being raised by residents.

Discussions with air traffic control revealed that due to the helipad’s location to the west of the runway, at times there was conflict with arriving or departing fixed wing aircraft which prevented helicopters tracking directly to or from the helipad.

A possible noise improvement was identified that, where it was not possible to provide direct tracking and where it is operationally feasible, helicopters be instructed by air traffic control to track via the inlets and not over the residential areas. This would mean that track miles would be increased on these occasions. Further discussions with air traffic control will be undertaken.

Posted on

The Adelaide Noise and Flight Path Monitoring System (NFPMS)

We collect noise and operational data from five noise monitors (Environmental Monitoring Unit, EMU) around Adelaide Airport.

Long term noise monitors are listed below according to their location.

Access monthly data on our Adelaide noise monitoring reports page.

BROOKLYN PARK (EMU 1)

Captures arrivals to Runway 23 and departures from Runway 05.

The pattern of noise events reflects the number of departures from Runway 05.

MEDINDIE (EMU 2)

Captures arrivals to Runway 23 and departures from Runway 05.

NETLEY (EMU 3)

Located to the south east of the cross runway.

Due to the low level of use of the cross runway, most of the noise events captured are associated with arrivals to Runway 05.

GLENELG NORTH (EMU 4)

Captures arrivals to Runway 05 and departures from Runway 23.

WEST BEACH (EMU 5)

Located to the north west of the cross runway.

Most of the noise events captured by this noise monitor are associated with departures from Runway 23.

Learn more about monitoring aircraft noise on the Airservices website.