3.12How to comply with the mandatory data fields requirement?

• GM to Reg. (EU) No 376/2014 and its IRs found in: Occurrence Reporting (376/2014) (Dec 2022)

3.12 How to comply with the mandatory data fields requirement? GM to Reg. (EU) No 376/2014 and its IRs Occurrence databases of organisations subject to Regulation 376/2014 shall contain the mandatory data fields listed in [Annex I](#_DxCrossRefBm2103820746) ([*Article**7*](#_DxCrossRefBm2103820744)*(1)*). <table border="1" cellpadding="0" cellspacing="0"><tr><td valign="top" width="599"><p align="center">Key principle</p><p>The set of common mandatory data fields included in <a href="#_DxCrossRefBm2103820746"><b>Annex I</b></a>.1. is required to be provided includes for each reportable occurrence<a href="#_ftn71"><b><b>[71]</b></b></a>.</p><p>The set of specific mandatory data fields included in <a href="#_DxCrossRefBm2103820746"><b>Annex I</b></a><b>.2 is required to be provided only for certain specific occurrences i.e. occurrences for which that data is relevant.</b></p><p>The objective is to ensure that data necessary to the proper understanding of the occurrence is provided.</p></td></tr></table> <table border="1" cellpadding="0" cellspacing="0"><tr><td valign="top" width="599"><p>Examples:</p><p>Aerodrome-related data fields (Location Indicator and Location on the aerodrome) are required to be provided only if an aerodrome is involved in the occurrence, such as for example a runway excursion.</p><p>Aircraft-related data fields are required to be provided only if one or more aircraft is involved in the occurrence. This may not be relevant for certain occurrences such as for example a failure of navigation service, an unauthorised person left unsupervised on apron or an engine production issue.</p></td></tr></table> <table border="1" cellpadding="0" cellspacing="0"><tr><td valign="top" width="599"><p align="center">Key principle</p><p>Mandatory data fields cannot be left blank when they are relevant to the occurrence. They should always be filled with a value (<a href="#_DxCrossRefBm2103820746"><b>Annex I</b></a>).</p></td></tr></table> If the information of any mandatory attribute is not known, the attribute may be transmitted with the value “Unknown” ([*Annex I*](#_DxCrossRefBm2103820746)). Other attributes may be relevant in specific circumstances (e.g. ‘‘Not applicable’’). The transfer of mandatory data fields should be done in an ECCAIRS/ADREP compatible format ([*Article**7*](#_DxCrossRefBm2103820744)*(4)*) such that it can be uploaded automatically to the ECCAIRS database of the competent authority (see Section [3.10](#_DxCrossRefBm2103820838) on the issue of ECCAIRS/ADREP compatibility). The European Reporting Portal facilitates the completion of mandatory data fields by indicating the attributes to be provided. Regulation 376/2014 foresees the possibility to amend the list of mandatory data fields based on experience. The Commission, with the support of EASA, will regularly review the completeness and relevance of the mandatory data fields list and may propose changes to it. --- [[71]](#_ftnref71) See definition of reportable occurrence in Section [3.7](https://dxweb.easa.europa.eu/dx4/Topics/gm_regulation376-2014_032.docx).i.