Remote Pilots and Remote Pilots when they are in command of an RPAS also have several obligations under Part 101 Manual of Standards.
Firstly and most importantly is to only perform operations where they have been issued an approval from the Chief Remote Pilot.
Section 10.04 (2) An RPA operation must not commence until a copy of the approved RPAS operational release has been provided to the remote pilot of the RPA.
Where an Approved RPAS Operational Release means see the following from Section 10.04(2),
Section 10.04 (4) For subsection (2):
approved RPAS operational release means the RPA operational release approved in writing by the certified RPA operator or the chief remote pilot.
Therefore, if a Remote Pilot chooses to perform an operation without an RPAS Operational Release they could be opening themselves up to penalties. Moving forward it is critical all Remote Pilots have obtained an Approved RPAS Operational Release prior to operations commencing.
For these requirements to workable in the field for operations required to be performed on short notice an efficient electronic mechanism for Remote Pilots in the field to send a request to the Chief Remote Pilot for approval at short notice must be available. Likewise the Chief Remote Pilots will also require a mechanism to review and approval requests efficiently. This can be achieved by writing in electronic systems into your Operations Manuals and Procedures Library.
Remote Pilots also have a requirement to ensure they maintain an accurate log of all operations performed.
Section 10.06 (2) The remote pilot log must also record the following for the remote pilot:
(a) information identifying each RPAS operation, including the type, model and unique identification mark of each RPA that is flown by the remote pilot;
(b) the date, location and duration of each RPA flight;
(c) separate accumulated flight times for operations that are:
(i) at night; or
(ii) within VLOS; or
(iii) within EVLOS; or
(iv) beyond VLOS;
(d) accumulated flight time in simulated operation of the RPAS, including details of the type of RPAS operations simulated.
Apart from the burden of maintain this log, the Remote Pilot will need to retain a copy of their operational records outside of the organisation to ensure they have access to them in case they leave the organisation or if the organisation ceases to operate.
The FlyFreely platform has been designed to address these challenges and many more to make the Remote Pilots job as simple as possible. All Remote Pilots obtain a “Log book for life” on the FlyFreely platform so their history stays with them no matter where they work.
This and other key features relevant to Remote Pilots are detailed in our Part 101 MOS Compliance Guide. Fill in this form to obtain your copy today.