Document ID: chunk:federal_register_of_legislation:F2024C00404:front:0:p59
Version: federal_register_of_legislation:F2024C00404
Segment Type: other
Provision Reference: 
Character Range: 148371–151128

the operation (if any);
(g) if an individual who is not a remote pilot for the operation is assigned duty in relation to the operation — the individual's full name and position as described in the operator's documented practices and procedures;
       Note   The individual's actual duties will, therefore, be found in the operator's documented practices and procedures.
(h) whether the RPA is to be operated within VLOS, or within EVLOS, or beyond VLOS during the operation;
(i) whether or not CASA has issued any instrument of approval, authorisation, direction, instruction, permission or exemption (however described) for the operation, and the full details of the instrument;
       Note   The requirement to record full details of the instrument is met by including a copy of the instrument with the record.
(j) that the relevant RPA is serviceable for the operation.
       (2) An RPA operation must not commence until the RPAS operational release has been approved by a person authorised for the purpose under the operator's documented practices and procedures.
Note   The approved operational release can be provided electronically, for example, through a software program or an email.
       (3) The certified RPA operator must keep the RPA operational release for at least 7 years after the day the operation ends.
       (5) Subsection (1) does not apply if the RPA is operated by an ReOC holder who is the sole remote pilot for the RPA in any operation under the ReOC.
       (6) Paragraphs (1) (g) to (i) do not apply to an RPA whose gross weight is less than 2 kg in a VLOS operation.

10.05 RPAS operational log
       (1) The certified RPA operator must ensure that the remote pilot in command of an RPA flight maintains an operational record (the RPAS operational log) in which the following is recorded as soon as practicable after the remote pilot ceases to operate the RPA:
(a) the nature and purpose of the operation;
(b) information identifying the RPA, including the type, model and unique identification mark;
(c) the remote pilot station for the operation;
(d) the dates and times of the operation;
(e) the places, identified by specific location or global Cartesian coordinates, from which the RPA was:
           (i) launched for the operation; and
           (ii) landed and recovered at the end of the operation;
(f) the name and ARN of the remote pilot in command;
(g) the names, roles, and ARNs, if applicable, of other crew members responsible for the safe operation of the RPA for the operation;
(h) whether the RPA was operated within VLOS, within EVLOS 1, EVLOS 2 or beyond VLOS during the operation;
(j) details of the relevant flight segments and the heights (AGL) at which each segment was flown, clearly indicating if