John, PM please with an e-mail address. However, first try direct linking, which may also help others with download difficulties:-
From
European Operators FDM forum, select
> Annual EOFDM Conference menu and view a conference year as required; this will list the presentations which can viewed / downloaded;
Thus FDM and Safety Promotion – 2013, or Characterisation of deep long landings – 2012, 2014 is active.
Re the original question; although not associated with any one operator, I did not see any requirement published during visits to many operators worldwide.
This may be a dated view, but perhaps self-evident as the early days of FDM programs followed (were part of) confidential reporting systems where anonymity was paramount.
Written reports can be completely confidential, thus there was a need for a gatekeeper if further investigation was warranted; perhaps well implmented FDM is less dependent on confidentiality.
With FDM it is unlikely that any event can be completely de-identified unless integrated within the analysis system.
Any need for a gatekeeper in FMD might be driven by the safety culture and use of FDM. If FDM only considers exceedances then further understanding – safety value, is limited unless the crew provide narrative. This an old view of safety, the human as a hazard, blame and train, only looking at what goes wrong.
Exceedances might only occur in 1 in 1,000 flights, whereas data from all flights can provide a much better picture of safety health. Why point the finger at one ‘spotty’ crew for a 2kt exceedance, when 500 others have operational ‘high temperatures’, flying 2kts below the limit; how do the latter crews manage, what is the actual safety margin, risk, etc. Many of the presentations in the links above consider the latter view with little discussion of or need for a gatekeeper.
A presentation relevant to the question is “Applying Just Culture Principles in an OFDM Program” (2013)
https://easa.europa.eu/essi/ecast/wp...st_Culture.pdf Note the emphasis on trust, communication, and feedback.