RPA/Drone risk management and control - OHS information sheet

October 2017

The following list of items should be considered for all proposed RPA flights as part of a pre-flight risk assessment. Additional hazards may exist specific to the individual activity and should be identified and evaluated as part of overall risk management of the flight.

Airspace

  • Flights are conducted in accordance with ‘Section 7. – Flight Restrictions’ of the Monash University Remote Piloted Aircraft (RPA)/Drone Safety Management Procedure.

Meteorological Conditions

  • Check Bureau of Meteorology for appropriate RPA flight conditions
  • Flights may only be conducted during daylight – confirm with the Authorising Pilot

Environment

  • Power lines, infrastructure and the general operating environment that could result in an RPA collision

Populous areas

  • Adhere to the Monash University General Operating Condition and CASA regulations

Emergency Procedures

Establishment of emergency procedures that include:

  • RPA collision with infrastructure, plant or people
  • Medical emergencies involving RPA Pilot or flight crew members
  • Technical malfunction, loss of control and communication with RPA
  • Fire (as a result of battery malfunction, faulty electronic RPA   wiring, etc.)
  • Landing of RPA if additional aircraft is observed by Pilot or Flight Crew
  • Other potential emergency scenarios identified during pre-flight planning

Line of Sight

  • RPA operations are not permitted if cloud or fog impairs Pilot Visual Line Of Sight (VLOS)
  • Physical VLOS of RPA must be maintained at all times during flight
  • Deviation of VLOS conditions or the use of First Person View (FPV)
  • Head Wear is subject to flight submission and CASA approval

Weight Class Authorisation

  • Pilots must adhere to the specific license conditions noted on their Remote Pilot License (RePL), including aircraft weight limitations
  • Monash University prohibits any operation of RPA over 25kg

RPA Operability

  • Pilots must ensure RPA functionality is safe for flight, including communication and battery systems
  • RPA maintenance schedules/regimes are demonstrated in flight logs
  • Functional testing of controls and communication must be validated and noted by Pilot before flight

Piloting

  • Flights of multiple RPA controlled by a single Pilot are not permitted
  • Autonomous RPA flights and ‘Swarms’ are not permitted without direct CASA consent – converse with the Authorising Pilots

Training

  • Pilots are registered with the Chief Remote Pilot
  • Pilots adhere to the requirements noted in this Procedure and any RePL requirements

RPA staff Health and Wellbeing

  • Pilot and Flight Crew ergonomics and fatigue considerations
  • Prohibit Pilot or Flight Crew members from RPA activities if they are under the influence of alcohol, drugs or substances that may impair performance related to their duties or responsibilities