AMC1 UAS.SPEC.050(1)(g) Responsibilities of the UAS operator

• ED Decision 2019/021/R found in: Unmanned Aircraft Systems (2019/947 and 2019/945) Part-UAS (Jul 2024)

AMC1 UAS.SPEC.050(1)(g) Responsibilities of the UAS operator ED Decision 2019/021/R LOGGING OF FLIGHT ACTIVITIES AND RECORD-KEEPING (a) An acceptable means to log and record the flight activities is to use a logbook, which may be electronic. (b) The information to be recorded should be indicated in the declaration or in the operational authorisation, which may include the following: (1) the identification of the UAS (manufacturer, model/variant (e.g. serial number); NOTE: if the UAS is not subject to registration, the identification of the UAS may be done using the serial number of the UAS. (2) the date, time, and location of the take-off and landing; (3) the duration of each flight; (4) the total number of flight hours/cycles; (5) in the case of a remotely piloted operation, the name of the remote pilot responsible for the flight; (6) the activity performed (add the reference to the STS or the authorisation number, as applicable); (7) any significant incident or accident[[101]](#_ftn102) that occurred during the operation; (8) a completed pre-flight inspection; (9) any defects and rectifications; (10) any repairs and changes to the UAS configuration; and (11) the information required to comply with [UAS.SPEC.100](#_DxCrossRefBm1106656791). (c) Records should be stored for 2 years in a manner that ensures their protection from unauthorised access, damage, alteration, and theft. (d) The logbook can be generated in one of the following formats: electronic or paper. If the paper format is used, it should contain, in a single volume, all the pages needed to log the holder’s flight time. When one volume is completed, a new one will be started based on the cumulative data from the previous one. --- [[101]](#_ftnref102) As defined by Regulation (EU) No 376/2014. ##### AMC1 UAS.SPEC.050(1)(g)  Responsibilities of the UAS operator *ED Decision 2019/021/R* **LOGGING OF FLIGHT ACTIVITIES AND RECORD-KEEPING** (a) An acceptable means to log and record the flight activities is to use a logbook, which may be electronic. (b) The information to be recorded should be indicated in the declaration or in the operational authorisation, which may include the following: (1) the identification of the UAS (manufacturer, model/variant (e.g. serial number); NOTE: if the UAS is not subject to registration, the identification of the UAS may be done using the serial number of the UAS. (2) the date, time, and location of the take-off and landing; (3) the duration of each flight; (4) the total number of flight hours/cycles; (5) in the case of a remotely piloted operation, the name of the remote pilot responsible for the flight; (6) the activity performed (add the reference to the STS or the authorisation number, as applicable); (7) any significant incident or accident[[168]](#_ftn169) that occurred during the operation; (8) a completed pre-flight inspection; (9) any defects and rectifications; (10) any repairs and changes to the UAS configuration; and (11) the information required to comply with [UAS.SPEC.100](#_DxCrossRefBm1295819111). (c) Records should be stored for 2 years in a manner that ensures their protection from unauthorised access, damage, alteration, and theft. (d) The logbook can be generated in one of the following formats: electronic or paper. If the paper format is used, it should contain, in a single volume, all the pages needed to log the holder’s flight time. When one volume is completed, a new one will be started based on the cumulative data from the previous one. --- [[168]](#_ftnref169) As defined by Regulation (EU) No 376/2014.