Document Feedback - Review and Comment
Step 1 of 4: Comment on Document
How to make a comment?
1. Use this to open a comment box for your chosen Section, Part, Heading or clause.
2. Type your feedback into the comments box and then click "save comment" button located in the lower-right of the comment box.
3. Do not open more than one comment box at the same time.
4. When you have finished making comments proceed to the next stage by clicking on the "Continue to Step 2" button at the very bottom of this page.
Important Information
During the comment process you are connected to a database. Like internet banking, the session that connects you to the database may time-out due to inactivity. If you do not have JavaScript running you will recieve a message to advise you of the length of time before the time-out. If you have JavaScript enabled, the time-out is lengthy and should not cause difficulty, however you should note the following tips to avoid losing your comments or corrupting your entries:
-
DO NOT jump between web pages/applications while logging comments.
-
DO NOT log comments for more than one document at a time. Complete and submit all comments for one document before commenting on another.
-
DO NOT leave your submission half way through. If you need to take a break, submit your current set of comments. The system will email you a copy of your comments so you can identify where you were up to and add to them later.
-
DO NOT exit from the interface until you have completed all three stages of the submission process.
(1) Operators and pilots of all Remotely Piloted Aircrafts (‘RPAs’), otherwise popularly referred to as ‘drones’ naturally operate within the national aviation system and must ensure flights are safe and compliant with the Civil Aviation Safety Regulations 1988. (2) This Policy applies to all operators of RPA’s on University property and all RPA’s owned by or on loan to the University, including: (3) The University has a number of RPA’s weighing between 500g-16kgs which are primarily used for education, research and marketing purposes. (4) The University is committed to the safety and wellbeing of its staff, students and the broader community, in the context of RPA operations and to ensuring compliance with the Civil Aviation Safety Regulations 1988. (5) Failure to comply with this Policy, or applicable laws and regulations, could result not only in disciplinary action but also enforcement action taken against the University and the pilot, and may be subject to civil and criminal penalties. (6) Any detected or suspected breaches of the Civil Aviation Safety Regulations 1988 or other applicable laws or regulations must be reported in accordance with the Compliance Management Policy. (7) All LTU RPA’s operators must hold a vaild Remote Pilot Licence (RePL) or have an RPA operator accreditation unless the RPA is being flown for fun. (8) All LTU RPA operators must submit evidence of a Remote Pilot License (RePL) or RPA operator accreditation to Infrastructure and Operations via ioservicedesk@latrobe.edu.au before flying a RPA for business purposes. (9) Where a RPA is being flown for fun, the operator must review and understand the CASA drone safety rules before operating the RPA. (10) The University does not a hold a Remotely Piloted Aircraft Operator’s Certificate (ReOC), therefore LTU staff are not permitted to: (11) Permitted RPA operator accreditation activities, where a RPA is less than 25kg include: (12) The RPA operator remains responsible for: (13) All LTU RPA operators must have a risk assessment in place for the use of RPA’s. The risk assessment must consider emergency response procedures such as loss of GPS signal, communication failure, or in-flight malfunction. (14) All RPA’s owned by the University must be registered with CASA using La Trobe’s Aviation Reference Number (ARN). (15) Infrastructure and Operations is responsible for registering and deregistering University owned RPAs with CASA. (16) When a new RPA asset is purchased by the University, information including the make, model, serial number, weight, type of drone and value must be reported to Infrastructure and Operations via ioservicedesk@latrobe.edu.au. (17) If the drone does not have a serial number, Infrastructure and Operations will supply a CASA-assigned registration mark, which must always be legibly displayed on the RPA when operating. (18) When a RPA is lost, damaged beyond repair or decommissioned, Infrastructure and Operations must be notified via ioservicedesk@latrobe.edu.au so the RPA can be deregistered with CASA. (19) Infrastructure and Operations is responsible for ensuring the RPA database is kept up to date with the names of licensed/accredited LTU RPA operators. (20) LTU RPA operators must retain records to demonstrate: (21) LTU RPA Operator’s records may be audited by Infrastructure and Operations to ensure compliance with record keeping requirements. (22) Where the University engages a third party to operate a RPA, the third party must adhere to this Policy. (23) Third party RPA operators remain responsible for compliance with all applicable laws, regulations and insurance arrangements. Engagement and operational terms should be formalised under a contract between the University and the third party. (24) Prior to operating a RPA on University property and to ensure proper visibility and risk management, all third party RPA operators must notify Infrastructure and Operations via ioservicedesk@latrobe.edu.au of their intent to fly and provide the following documentation: (25) While the Civil Aviation Safety Regulations 1988 do not specifically cover privacy obligations, the right to privacy, and protections afforded against surveillance under State or Territory laws (i.e. observation and visual records) must remain a paramount consideration when designing a RPA flight operation. (26) An individual may complain to the University’s Privacy Officer at privacy@latrobe.edu.au about the use of an RPA on University property if they believe it has interfered with their privacy. (27) The Privacy Officer will investigate the complaint as promptly as possible and will advise the Chief Operating Officer or nominee of their findings and recommendations. (28) The Chief Operating Officer or nominee will make a decision on the complaint and advise the complainant in writing of the outcome of the investigation. (29) For the purpose of this Policy and Procedure: (30) This Policy is made under the La Trobe University Act 2009.Remote Pilot Aircraft Policy
Section 1 - Key Information
Top of Page
Policy Type and Approval Body
Administrative – Vice-Chancellor
Accountable Executive – Policy
Chief Operating Officer
Responsible Manager – Policy
Executive Director, Asset Transformation
Review Date
15 November 2027
Section 2 - Purpose
Section 3 - Scope
Top of PageSection 4 - Key Decisions
Top of Page
Key Decisions
Role
Purchase of asset (RPA/Drone)
Head of School/Financial Delegate
Section 5 - Policy Statement
Section 6 - Procedures
Part A - LTU RPAs and Operators
Part B - LTU RPAs Registration and Maintenance
Part C - Third Party RPAs and Operators
Part D - Privacy and Complaints
Section 7 - Definitions
Top of PageSection 8 - Authority and Associated Information