WHS-PRO-018 Remotely Piloted Aircraft Procedure

1 Intent

The purpose of this procedure is to document and communicate how James Cook University (JCU) manages authorised operations of Remotely Piloted Aircraft (RPA) so that all operations are carried out safely and comply with all applicable rules, laws and regulations.

2 Scope

This Procedure applies to all JCU RPA Operations.

The Procedure applies to all JCU staff and students (including higher degree by research candidates) involved in JCU RPA Operations.

Any JCU RPA Operation, regardless of its purpose, and regardless of the type, size or weight of the RPA used, must be authorised in accordance with this Procedure.

3 Abbreviations

4 Definitions

Table of Contents

1       Duty, Obligations and Responsibilities

1.1         JCU

1.2         JCU staff and students

1.3         Dean, Research

1.4         Chief Pilot

1.5         Chief Maintenance Controller

1.6         Remote Pilots – Remote Pilot Operators (<2kgs RPA in non-exempt areas) and Remote Pilot-in-Command (<2kgs RPA in exempt areas and >2kg RPA)

1.7         Maintenance Personnel

1.8         Non-Controlling Observer

2       Types of Operations

2.1         What are Standard Operating Conditions (SOC)?

2.2  JCU Operation Types

2.3         Operation Type 1

2.3.1      Approval process to Undertake JCU RPA Operation

2.3.2      Licencing and Training Requirements

2.3.3      JCU Pilot Register and Insurance Policy

2.3.4      Notification to CASA

2.3.5      RPA requirements

2.3.6      Mission Plan and Field Trip Module

2.3.7      Where can I fly?

2.3.8      On Site Requirements

2.3.9      Post Flight Requirements

2.4         Operation Type 2

2.4.1      Approval process to Undertake JCU RPA Operation

2.4.2      Licencing and Training Requirements – Remote Pilot-in-Command

2.4.3      JCU Pilot Register and Insurance Policy

2.4.4      Chief Pilot Role

2.4.5      On Site Requirements

2.4.6      Post Flight Requirements

2.5         RPA Requirements

2.5.1      Approved JCU RPA’s

2.5.2  Maintenance of RPA's

2.6         Insurance

2.7         Drug and Alcohol Management

2.8         Incident Reporting

2.9         Field Trips

2.10       Non-JCU Remote Pilot Operators and Remote Pilot-In-Command

2.11       RPA Operations conducted on / over JCU Property

2.12       RPAs not owned by JCU

2.13       Personal Information

Procedure

1 Duty, Obligations and Responsibilities

To protect the safety of the operator and other people, JCU RPA’s must only be operated in accordance with this procedure.  Education and training of JCU staff and students in the operation of RPAs can reduce the risks associated with these activities. Each person involved in RPA activities has a responsibility to ensure the health and safety of themselves and others.

1.1 JCU

JCU has a duty to ensure:

• the health and safety of workers and others during all JCU RPA Operations; and
• that all JCU RPA Operations being conducted comply with all applicable rules, laws and regulations.

1.2 JCU staff and students

JCU staff and students must comply with this Procedure before commencing a JCU RPA Operation.

Visitors to JCU are not authorised to fly RPAs on JCU Premises and/or for a JCU Purpose unless specifically employed by JCU to do so, such as in the case of contractors.

1.3 Dean, Research

The Dean, Research has a JCU-wide oversight of JCU RPA Operations. More specifically, he/she is responsible for the following:

• Providing the necessary resources so that all RPA operations can be carried out safely and in compliance with applicable legislation;
• Maintaining the JCU RPA Register to ensure currency of all RPAs listed thereon;
• Maintaining the JCU Pilot Register to ensure currency of licenses for all qualified Remote Pilots-In-Command thereon;
• Ensuring all RPAs are listed in the JCU data base and noted on JCU’s aviation insurance policy;
• Ensuring all Remote Pilot Operators and Remote Pilots-In-Command are listed on JCU’s aviation insurance policy.
• Ensuring all RPAs are maintained to required standards.

1.4 Chief Pilot

As a business, JCU must operate under a Remote Operator Certificate (ReOC) to fly RPA’s.  A Chief Pilot is nominated under a ReOC, and must be a suitably qualified and experienced RPA operator. They are responsible for ensuring JCU RPA Operations are conducted in compliance with the Civil Aviation Act 1988 (Cth) and the Civil Aviation Safety Regulation (CASR). JCU may operate with an external business to utilise their ReOC providing the company holding the Remote Operator’s Certificate can manage the activity and all conditions of the Operations Manual are followed.

A Chief Pilot reports to Civil Aviation Safety Authority (CASA) and the Dean, Research as well as other regulatory bodies as required.

The Chief Pilot is also responsible for:

• maintaining a record of qualifications held by each JCU Remote Pilot-In-Command registered with them;
• having control of all related training and operational matters affecting the safety of their registered pilots;
• maintaining a complete and up-to-date reference library of operational documents as required by CASA for the class of operations conducted by JCU;
• all communication between JCU clients and CASA relating to their registered pilots; and
• reviewing and approving applicable flight plans.

1.5 Chief Maintenance Controller

The Chief Maintenance Controller controls RPA maintenance of registered drones on behalf of JCU and is part of the ReOC business.

The Chief Maintenance Controller is also responsible for:

• ensuring personnel performing maintenance on the RPAs are competent by keeping records of personnel permitted to perform maintenance;
• developing, enforcing and monitoring RPAs maintenance standards;
• maintaining a record of RPAs unserviceability, RPAs hours, cycles and other information relevant to the scheduling of maintenance;
• ensuring maintenance activities are conducted in accordance with the procedures specified in the Maintenance Manual;
• liaising with CASA with regard to all maintenance and technical issues relating to their registered pilots;
• following manufacturer's instructions, recommendations and bulletins;
• determining more efficient, safer, economical and time minimising procedures and processes;
• assessing how new payloads interact with the RPA electrically, mechanically and structurally;
• ensuring that all payloads or modifications are attached to the RPA (both passive and active) conform with the RPA’s specification; and
• approving all new payloads and determining if the payload will be approved for the Remote Pilot-in-Command to swap off and on.

1.6 Remote Pilots – Remote Pilot Operators (<2kgs RPA in non-exempt areas) and Remote Pilot-in-Command (<2kgs RPA in exempt areas and >2kg RPA)

A Remote Pilot is a JCU staff member or student authorised to undertake a JCU RPA Operation.  They are the person who manipulates the flight controls of a RPA.  There are two categories, operators those without licences and in-command, those with licences.

All pilots are responsible for:

• the safe flying of the RPA;
• ensuring the RPA under his or her control is operated in accordance with this Procedure;
• ensuring that each flight is conducted according to any law, rule, regulation or conditions required for that flight;
• carry his or her own identification or if applicable CASA issued Remote Pilot License with him or her on operations;
• ensuring logbooks, insurance and data base logs remain up-to-date;
• conducting safe operations from pre-flight, start-up, during flight and after landing until after shutdown and storage of the RPA; and
• completing a risk assessment prior to and during JCU RPA Operations to ensure control mechanisms remain effective throughout the mission.

1.7 Maintenance Personnel

The Maintenance Personnel maintain the RPAs.

Maintenance Personnel are JCU staff and will report to a Chief Maintenance Controller and regulatory bodies when maintaining drones registered with an ReOC. Otherwise maintenance personnel will report to the Dean of Research.

The Maintenance Personnel have the following functions and responsibilities:

• to complete all maintenance in accordance with the manufacturer’s instructions;
• when applicable notify the appropriate ReOC provider Chief Maintenance Controller of all defects found during any maintenance;
• when applicable record and notify the Dean of Research of any and all defects found during any maintenance; and
• follow manufacturer's instructions, recommendations and bulletins.

1.8 Non-Controlling Observer

A Non-Controlling Observer is a JCU staff member that assists and reports to the Remote Pilot-in-Command or Pilot Operator during flight operations.

Non-Controlling Observers have the following functions and responsibilities:

• to not interfere with the flying operation of the Remote Pilot-in-Command or Pilot Operator;
• to assist the Remote Pilot-in-Command or Pilot Operator with any emergency if requested;
• to assist the Remote Pilot-in-Command or Pilot Operator with observations of potential hazards both to the RPA and the general public; and
• maintain knowledge of how to activate the failsafe mechanism of the RPA.

2 Types of Operations

2.1 What are Standard Operating Conditions (SOC)?

The RPA is operated:

• by visual line of sight (VLOS) only - close enough to see, maintain orientation and achieve accurate flight and tracking;
• no higher than 120 m (400 feet) above ground level;
• during daytime only - not after sunset.

The RPA is not operated:

• any closer than 30 m from people not associated with the flight (i.e. any person who is not charged with duties essential to the safe operation of a remotely piloted aircraft);
• in a prohibited area or restricted area;
• in a restricted area that is classified as RA3;
• over populous areas;
• within 5.5 km (3 NM) of a controlled aerodrome - one with an operating control tower;
• in the area of a public safety operation without the approval of a person in charge of the operation;

Only 1 RPA flown per pilot at any one time.

For clarification on any of these points refer to CASA advisory circular AC101-10 Remotely piloted aircraft systems- operation of excluded RPA (other than model aircraft).

2.2 JCU Operation Types

Operation Type 1:

<2kg RPA operated under SOC

a)  Licence not required – classed as a Remote Pilot Operator

b)  Must be listed on JCU Pilot Register

c)  Must be listed on JCU Remotely Piloted Aircraft System Insurance Policy

d)  Must notify CASA five business days before first operation

e)  Must maintain aircraft records

f)  Must prepare a mission plan and include it in the Riskware Field Trip Module

g)  Must follow on site and post flight requirements

Operation Type 2:

<2kg RPA not under SOC OR >2kgs RPA

a)  Licence required – classed as Remote Pilot-in-Command

b)  Must be listed on JCU Pilot Register

c)  Must be listed on JCU Remotely Piloted Aircraft System Insurance Policy

d)  Report to the JCU nominated Chief Pilot and follow all requirements stipulated by the Chief Pilot

e)  Must prepare a mission plan and include it in the Riskware Field Trip Module

f)  Must follow on site and post flight requirements

2.3   Operation Type 1

This type of operation includes:

• Operating < 2kg RPA under SOC

2.3.1 Approval process to Undertake JCU RPA Operation

JCU staff and students undertaking JCU RPA Operations must ensure they are authorised by the appropriate personnel prior to operation.

JCU staff and students wishing to undertake a JCU RPA Operation should contact the Dean, Research in the first instance with any queries on this Procedure.

2.3.2 Licencing and Training Requirements

When flying RPA’s under 2kg and under standard operating conditions (SOC) Remote Pilot Operators do not require a Remote Pilot Licence.

Remote Pilot Operators must also go through CASA accreditation to show knowledge of the drone safety rules. Go to www.casa.gov.au for more information.

2.3.3 JCU Pilot Register and Insurance Policy

All JCU Remote Pilot Operators must be listed on the JCU Pilot Register and noted on JCU’s Remotely Piloted Aircraft System insurance policy (refer Section 9). The Remote Pilot Operator must contact the RPAS@jcu.edu.au to ensure he or she is listed on the JCU Pilot Register before undertaking a JCU RPA Operation.

2.3.4 Notification to CASA

It is JCU Remote Pilot Operators responsibility to notify CASA five business days before the first operation, using JCU’s ARN number 216007. CASA’s authorisation to fly must be emailed to RPAS@jcu.edu.au. Notifications are specific to each drone and location but are valid for 3 years. If a different drone is flown or a different place is flown from then a new notification will need to be submitted.

2.3.5 RPA requirements

Registration with CASA:

The JCU Remote Pilot Operator must ensure that the RPA is registered with CASA before it can be flown. Go to the Civil Aviation Safety Authority website and find myCASA portal for more information.

Maintenance of RPA:

It is also the responsibly of the JCU Remote Pilot Operator to maintain aircraft records that show: − time-in-service − maintenance history − any defects and abnormalities that affect operations − any incidents or accidents − any other useful information that may affect the safety of future flights with the RPA.

2.3.6 Mission Plan and Field Trip Module

It is the responsibility of the JCU Remote Pilot Operator to prepare a mission plan and include that within Field Trip. Field trip is located within JCUs WHS Riskware software. The plan should include information about the local area and any hazards. It should also contain procedures about planned emergency flight profiles in the event of a lost data link. Depending on system capabilities, these profiles should include either an: − RPA automated transit to a pre-designated recovery area, followed by an automated recovery or − RPA automated transit to a pre-designated recovery area, followed by activation of a flight termination system.

2.3.7 Where can I fly?

It is the responsibility of the JCU Remote Pilot Operator to download the CASA approved Drone safety apps to help decide where flights can take place.

2.3.8 On Site Requirements

When arriving onsite to carry out a JCU RPA Operation, the following shall be conducted by the Remote Pilot Operator:

• site familiarisation to identify hazards and launch and recovery areas (primary and emergency);
• a safety briefing to all personnel involved and spectating nearby;
• a Pre-Flight Checklist that is specific to the RPA being used (WHS-PRO-Checklist Pre-Flight Checklist for <2kg SOC);
• safely conducting the RPA operations; and
• Post-Flight checklists that is specific to the RPA being used (WHS-PRO-Checklist Post-Flight Checklist for <kg SOC).

For education, outreach, research and training purposes, micro-drones (<100g); operations shall be conducted as per <2kg class. With the exception Micro RPA operations are always categorised as excluded RPA operations.

2.3.9 Post Flight Requirements

On completing a JCU RPA Operation, remote pilots shall log the flights (WHS-PRO-Template CASA Form 1483 – RPA Flying Hours Log Book) and battery use, update aircraft records, report any defects and abnormalities to maintenance personnel and report any other useful information that may affect the safety of future flights with the RPA.

All activities which do not satisfy the above criteria will require a Remote Pilot Licence and fall under the criteria of Remote Pilot-in-Command (Operation Type 2).

2.4 Operation Type 2

This type of operation includes:

• Operating <2kg RPA not under SOC; OR
• Operating >2kgs RPA

2.4.1 Approval process to Undertake JCU RPA Operation

JCU staff and students undertaking JCU RPA Operations must ensure they are authorised by the appropriate personnel prior to operation.

JCU staff and students wishing to undertake a JCU RPA Operation should contact the Dean, Research in the first instance with any queries on this Procedure.

All non excluded (Restricted) Operation Type 2 RPA JCU Operation requests must first be submitted to a Chief pilot. This includes all documentation risk assessments, flight plans and database entries necessary for review and approval.

All Special Operations may require extra time for approval. This is to allow for exemptions to be issued by CASA, ensure appropriate documentation and training is in place, and all updates and maintenance on affected RPAs has been completed (if required).

2.4.2 Licencing and Training Requirements – Remote Pilot-in-Command

For those activities which require a Remote Pilot Licence, the Chief Pilot in conjunction with the Dean, Research authorises the Remote Pilot-in-Command to carry out a JCU RPA Operation.

A Remote Pilot-in-Command will report to a Chief Pilot, the Dean, Research and regulatory bodies as required.

To obtain a (UAV) a Remote Pilot License, JCU staff and students should first contact a ReOC provider. The relevant JCU staff member or student will then be contacted by a Chief Pilot to commence the licensing process.

When flying RPA’s over 2kg or in NON exempt (restricted) areas or under conditions that do not satisfy standard operating conditions a Remote Pilot must satisfy the following requirements:

• hold a current Remote Pilot License issued by CASA or have successfully completed a Remotely Piloted Training Course;
• hold a current AROC or FROL.  If a FROL is held, an appropriate and current medical is also required;
• have a minimum number of hours (usually5 hours) experience (as designated by the ReOC provider) on the type of RPA to be used (under supervision);
• have demonstrated competency in flight to a Chief Pilot, Chief Training Officer or Pilot nominated and authorised by a Chief Pilot; and
• have demonstrated a good sense of safety.

In addition, for Special Operations, the Remote Pilot-in-Command must satisfy the following additional requirements:

• internal training for the type of ‘special’ operation;
• appropriate endorsement on internal license; and
• demonstrated competency in flying RPAs to the satisfaction of the Chief Pilot.

Each Remote Pilots-In-Command will be qualified on a class of RPAs. Any changes will need to be approved and CASA will issue the relevant Remote Pilot License to reflect new RPA types and weights class that may be operated by the Remote Pilot-In-Command. After the CASA updates are confirmed, the Remote Pilot License will be updated.

Upon induction, Remote Pilots-In-Command will receive digital copies of all operations, flight and maintenance manuals and associated documents/software to appropriately plan, execute and log JCU RPA Operations.

To ensure Remote Pilots-In-Command maintain an adequate level of competency in operating an RPA, they will be subject to initial and annual evaluations (knowledge and flight competency) by a Chief Pilot and the Dean, Research.

2.4.3 JCU Pilot Register and Insurance Policy

The Remote Pilot-In-Command must be listed on the JCU Pilot Register and noted on JCU’s Remotely Piloted Aircraft System insurance policy. The Remote Pilot-In-Command must contact the RPAS@jcu.edu.au to ensure he or she is listed on the JCU Pilot Register and noted on JCU’s Remotely Piloted Aircraft System insurance policy before undertaking a JCU RPA Operation.

2.4.4 Chief Pilot Role

A Chief Pilot will review the flight plan and risk assess the proposed JCU RPA Operation. A Chief Pilot may provide:

• approval for the JCU RPA Operation;
• additional information or identification of risks prior to approval;
• additional required steps to be undertaken prior to, or during the mission; and
• additional requirements on the operation such as, but not limited to:
  • phone calls to controlling authorities;
  • radio broadcasts;
  • flight parameter requirements;
  • flight path requirements; and
  • crew requirements.

For additional information on the approval process, JCU staff and students can go to the CASA web site.

2.4.5 On Site Requirements

When arriving onsite to carry out a JCU RPA Operation, the following shall be conducted by the Remote Pilot-in-Command:

• site familiarisation to identify hazards and launch and recovery areas (primary and emergency);
• a safety briefing to all personnel involved and spectating nearby;
• a Pre-Flight Checklist that is specific to the RPA being used;
• safely conducting the RPA operations; and
• Post-Flight checklists that is specific to the RPA being used.

For education, outreach, research and training purposes, micro-drones (<100g); operations shall be conducted as per <2kg class. With the exception Micro RPA operations are always categorised as excluded RPA operations.

2.4.6 Post Flight Requirements

On completing a JCU RPA Operation, remote pilots shall log the flights (WHS-PRO-Template CASA Form 1483 – RPA Flying Hours Log Book) and battery use, update aircraft records, report any defects and abnormalities to maintenance personnel and report any other useful information that may affect the safety of future flights with the RPA.

2.5 RPA Requirements

2.5.1 Approved JCU RPA’s

All RPA’s used in JCU RPA Operations by JCU staff and students must be:

• owned by JCU;
• noted on JCU’s insurance policy; and
• listed on the JCU RPA Register,

before the JCU RPA Operation can be undertaken.

All RPAs to be used in JCU RPA Operations must be purchased using a purchase requisition and the approved process that is outlined in FMPM 711 – Procurement Procedure.

Non JCU owned RPAs are not to be used for JCU RPA Operations except where contracted for specific tasks.

2.5.2 Maintenance of RPA's

• Those RPAs registered with ReOC providers will follow all maintenance requirements instructed by the ReOC provider and will be maintained by JCU maintenance personnel.
• RPAs not registered with an ReOC provider will be maintained by designated JCU maintenance personnel and will follow the manufacturer’s specifications.
• If a manufacturer does not provide details concerning the scheduling of maintenance, or the information is not relevant, a schedule may be developed based upon similar craft and best practice.
• The maintenance personnel will ensure that where maintenance schedules have been developed for an RPAS, this schedule is recorded. A copy of the schedule should be kept with the RPA as well as an inspection record.
• All components of an RPAS are subject to ongoing ‘on condition’ monitoring through the Pre-flight and Post-flight inspections.
• The Pre-flight and Post–flight inspections are used to identify damage, wear, malfunction or unserviceability, and any defects found during these inspections will be recorded on a Defect and Maintenance Log
• Maintenance personnel will monitor the failure rate of each RPAS. Components must be repaired or replaced where they show signs of unserviceability, abnormality or damage unless the damage is insignificant to the operation of the RPAS (e.g. scratches or cosmetic damage).
• Avionic and control system software is only to be updated after the version has been confirmed as being stable. A post maintenance test flight, in a controlled and safe location, must be completed as part of the maintenance activity whenever a software or firmware update is applied.
• Where an issue arises with new software / firmware version the component is to be rolled back to the previous stable version before the RPAS is used in commercial operations.
• Records of firmware or software updates will be documented in the maintenance log and include details of any test flights and version numbers relevant to the update.
• It is the responsibility of all person(s) involved in the operation of RPAS to report defects as they occur and record the maintenance they have conducted on the RPAS.

2.6 Insurance

All Remote Pilot Operators, Remote Pilots-In-Command must be approved by the insurer and listed on JCU’s Remotely Piloted Aircraft System insurance policy before they can undertake any JCU RPA operation.

All RPAs and associated equipment operated by the Remote Pilot Operator or Remote Pilot-In-Command must be approved by the insurer and listed on JCU’s Remotely Piloted Aircraft System insurance policy before they can be flown.

Pilots and Aircraft information will need to be updated annually, preferably in February, each year.  The previous year’s pilot and aircraft listings will be removed from the insurance cover and will require the Remote Pilot Operator or Remote Pilot-In-Command to contact rpas@jcu.edu.au and insurance@jcu.edu.au to arrange cover. Insurance cover is only in place once confirmation has been received.

If a claim is made on JCU’s Remotely Piloted Aircraft System insurance policy as a result of a JCU RPA Operation, an excess may apply.

2.7 Drug and Alcohol Management

Drugs and alcohol testing may occur at any time by CASA or the ReOC Provider in accordance with their safety management systems.

Operators should make themselves familiar with their rights and obligations under the CASA regulations. Information on random drug and alcohol testing can be found on the CASA website under Safety Management.

As a guide, drugs or alcohol should not be consumed 8 hours prior to or during any period of planning or executing JCU RPA Operations.

2.8 Incident Reporting

In the event of any incident, the Remote Pilot Operator, Remote Pilot-in-Command or the Non Controlled Observer are to report the incident by:

Contacting:

• 000 / 112 if anyone is injured;
• local air traffic controllers;
• Chief Pilot and / or Director-Divisional Operations and the Dean, Research; and
• any additional parties identified during the Pre-Flight Risk Assessment.

And:

• documenting and photographing all aspects of the incident immediately and report the incident;
• assisting with an investigation of the incident if required and ensuring processes and documentation is amended to incorporate recommendations as a result; and
• following the additional requirements outlined in the WHS-PRO-005 Incident and Hazard Management Procedure.

2.9 Field Trips

Any JCU RPA Operation approved for the purpose of study or research by JCU staff or students may be considered a field trip.  All flight plans must be recorded in the RiskWare Field Trip Module. JCU field trips are to be managed in accordance with WHS-PRO-015 Field Trip Procedure in addition to this Procedure.

2.10 Non-JCU Remote Pilot Operators and Remote Pilot-In-Command

Non-JCU Remote Pilot Operators/Remote Pilots-In-Command must not operate on behalf of JCU or operate as, Remote Pilot Operators/Remote Pilot-in-Command any JCU owned RPA’s without the prior written approval from the Dean, Research and the Chief Pilot.

Permission and approval to fly over JCU Premises must be sought by emailing rpas@jcu.edu.au.

2.11 RPA Operations conducted on / over JCU Property

JCU RPA’s operated on / over JCU Premises are treated as type 2 operations (refer to section 2.4). RPA operations on / over JCU Premises must have prior written approval from the Dean, Research and the Chief Pilot.

Permission and approval to fly over JCU Premises must be sought by emailing rpas@jcu.edu.au.

2.12 RPAs not owned by JCU

RPAs that are not owned by JCU must not be used over JCU Premises and/or by JCU staff/student/volunteers conducting JCU work / research / study.

Where Contractors are engaged for specific JCU RPA tasks, copies of CASA licences, ReOC certificates, insurances, safety plans and CASA approvals will be sent to JCU insurance for approval.

2.13 Personal Information

JCU staff and students should note that their Personal Information may be supplied to a ReOC provider as part of the approval process contained in this Procedure and will be done so in accordance with JCU’s Information Privacy Policy and relevant legislation.

JCU staff and students should be aware that Personal Information of third parties may be collected while undertaking JCU RPA Operations, for example, taking photographs of individuals. If JCU staff and students are concerned about the use of any video footage or photographs taken as a result of carrying out a JCU RPA Operation, they should contact the Dean, Research in the first instance for further advice prior to use of any such footage or photograph.

Related policy instruments

FMPM 711 – Procurement Procedure

WHS-PRO-005 Incident and Hazard Management Procedure

WHS-PRO-015 Field Trip Procedure

JCU RPA Register

JCU Pilot Register

Advisory Circular AC 101-10 Remotely piloted aircraft systems – operation of excluded RPA (other than model aircraft)

CASA

Air Services Australia

Australian Defence Force

Work Health and Safety Act 2011 (Qld)

Work Health and Safety Regulation 2011 (Qld)

The Civil Aviation Act 1988 (Cth)

The Civil Aviation Safety Regulation 1988 (Cth)

Schedules/Appendices

WHS-PRO-CHK-018a  Pre-Flight Checklist for <2kg SOC

WHS-PRO-CHK-018b Post-Flight Checklist for <2kg SOC

WHS-PRO-FORM-018c CASA Form 1483 – RPA Flying Hours Log Book

WHS-PRO-CHK-018d Planning Checklist for use of Remote Piloted Aircraft

Administration

NOTE:  Printed copies of this procedure are uncontrolled, and currency can only be assured at the time of printing.

Approval Details

Revision History