The use of email ‘Engineering Reports’ to record aircraft technical defects circumvented the requirements of EASA Part M regulation M.A.403 for correctly recording defects in the aircraft technical log and aircraft maintenance records. A review of the ‘Engineering Report’ emails for G-BYCP, over nine months of operation immediately preceding the accident ight, revealed a high number of defects that were not recorded in the aircraft technical log, and for which recti cation actions were not recorded in the aircraft’s technical records. It was clear that the operator was aware of the aircraft’s defect history and that it used the content of the ‘Engineering Report’ emails to coordinate defect recti cation during the scheduled Phase 1 maintenance inspection in June 2015. Where defects were recti ed in this manner, the recti cation interval was well outside MEL allowable time limits.
........the actual the report..
Note the use of words "reports.......circumvented.....requirments of Part M"
And "high number if defects......not recorded"
Bottom line is this was a poorly maintained old aircraft with a long history of defects operated by a company that thought it knew better than the regulations.....or that it could get away without compliance.....( which , but for this accident, or a whistle blower it would have done)