SAFA Ramp Inspections - Code7700

More documents

Recommendations

Info

SAFA Ramp InspectionsGuidance materialClass 3d (Immediate operating ban)When class 3d action is imposed it is usually in addition to a Class 3a, 3b or 3c action.Therefore, the further follow-up for the SAFA programme is considered to be covered bythe follow-up of those actions. However, when class 3d action is taken, Member Statesshould be mindful of their obligations under Regulation (EC) No 2111/2005.6.3 Monthly reportArticle 2.4 of the Commission Regulation (EC) No 768/2006 requires the Agency to: advise the European Commission and the Member States on immediate actions orfollow-up policy, report potential safety problems, and propose coordinated actions to the European Commission and the Member States whennecessary on safety grounds and ensure co-ordination at the technical level of suchactions.For that reason, the Agency needs to be informed on follow-up actions taken by the MemberStates. Therefore, Member States are required by paragraph 6.4 of the Annex to CommissionDirective 2008/49/EC to make available to the Agency a monthly report on the status offollow-up actions taken pursuant to ramp inspections.In order to standardise the format of the data of such report, Member States are requested touse the template as shown in appendix 6.As of version 2.0 of the centralised SAFA Database, the follow-up of inspections can be doneelectronically. Member States which make full use of these functionalities of the Database areconsidered to meet the requirement to send a monthly report since they provide all theinformation in “real time”.6.3.1 Monthly report form instructionsThe report will contain an overview of all the correspondence related to follow-up actions, sentout or received by the Member States during the previous calendar month. The report shall besent in a spreadsheet format (i.e. Microsoft® Excel) to the Agency (SAFA CoordinationSection) by Email (safa@easa.europa.eu) within two weeks. The monthly reports should besent aggregated (i.e. the monthly report for April will include also the reports for January,February and March).With the introduction of the new database on 21 September 2011, the new follow-upfunctionality became available. When fully using this functionality, States are considered tomeet the requirement to send the monthly report to EASA.Once authorities and operators have registered to the database and are consequently usingthe follow-up feature, all required data will be stored by and can be retrieved from thedatabase. However, since not all authorities and operators have obtained access we are still ina transition phase; nevertheless, information such as:a. date of notificationb. means of notificationc. follow-up information (by creating entries specifying/quoting the actionsproposed/taken by the operator and/or its authority)can be entered manually in the Database instead of entering this into the monthly report.At this stage, for all reports entered until 21 September 2011, as well as for replies topreviously sent communications, you should either:• update the monthly report and continue to send it to us until all inspections have beenclosed; orSAFA Coordination Section Page 28 of 217© European Aviation Safety Agency, 2012 V 2.0
SAFA Ramp InspectionsGuidance material• transfer the above mentioned data on inspections with open findings to the databasefollow-up module which renders the monthly report obsolete.Since providing the information “real time” via the SAFA Database is considered to meet therequirement to send a monthly report, there is no need to send any subsequent monthlyreport anymore as soon as the open inspections have been transferred to the database, or allinspections on the previous monthly report were closed. EASA should be informed as soon asyou stop sending the monthly report for one of the above-mentioned reasons.Explanatory comments to the form: Generalo The electronic template will be made available to the Member States. By usingthe electronic version, the user is able to simply add new cells (e.g. whencorrespondence has been sent to both the State of operator and State of registryif different) to a row or add more rows to the form.o Not the date of inspection, but the correspondence date determines in whichmonthly report the correspondence should be listed.o Columns 2 and 4 are considered to be optional. For maximum efficiency andmonitoring ability, Member States are encouraged to fill out the information inthese columns as well.Header and Footer: State: the official name of the Member State; NAA: the official name of the competent authority; Month: the concerned calendar month including the calendar year.OPERATOR SECTIONColumn (1) “Ramp inspection report number(s)”: Every row should represent the information related to a certain ramp inspection.Column (2) “Operator Code” (optional) List the 3 letter ICAO operator code as in the SAFA databaseColumn (3) “Operator Name” List the operator’s name as in the SAFA databaseColumn (4) “Findings” (optional) List the findings raised in the respective report using the following format (x number ofcategory 1 findings – y number of category 2 findings – z number of category 3findings) (e.g. 3-1-2 = 3 category 1 findings; 1 category 2 finding and 2 category 3findings)Column (5) “Written communication to operator (date)” List the date when the written communication to the operator was sent (format: ddmm-yyyy).Leave blank if no communication was sent because the operator/authorityreacted already based on POI.Column (6) “Receipt confirmed” Indicate (Y/N) whether the receipt of the written communication is confirmed (thiscould be in the form of a fax receipt, e-mail read confirmation or a receipt confirmationin the case of registered mail).Column (7) “Received on” List the date when the operator reply was received (format: dd-mm-yyyy)Column (8) “Answer Satisfactory” Indicate if the answer given by the operator is satisfactory (Y/N/P = Yes/No/Partially)Column (9) “Findings closed/Supplemental Communication” Indicate, based on the reply of operator, whether the findings in the report have beenclosed I or if a supplemental communication was sent (S). Such supplementalcommunication should also be sent to the State of oversight. If a supplementalcommunication was sent, add an additional line filling-in the required fields (1, 5-17).SAFA Coordination Section Page 29 of 217© European Aviation Safety Agency, 2012 V 2.0
Page 1 and 2: European Aviation Safety AgencyEuro
Page 4 and 5: SAFA Ramp InspectionsGuidance mater
Page 32 and 33: SAFA Ramp Inspection ProceduresGuid
Page 78 and 79:
SAFA Ramp Inspection ProceduresGuid
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
show all

SAFA Ramp Inspections - Code7700

Create successful ePaper yourself

Delete template?

Save as template?