INTRODUCTION Development of a flight safety documents system is a complete process. Changes to each document comprising the system may affect the entire system. Guidelines applicable to the development of operational documents have been produced by DGCA based on the recommendations of ICAO, current best industry practices and analysis of previous accident with emphasis on high degree of operational relevanc Air operators who have yet to establish a flight safety documents system should utilize the information provided in CAR in establishing such a system. DGCA inspectors will conduct a review of the flight safety documents system to ensure that it is effective in providing vital safety information to flight crew in a timely manner. Guidelines applicable to operational documents’ development tend to focus on a single aspect of documents design, for example, formatting and typography. Guidelines rarely cover the entire process of operational documents development.
It is important for operational documents to be consistent with each other, and
consistent with regulations, manufacturer requirements and Human Factors principles. It is also necessary to ensure consistency across departments as well as consistency in application. Hence the emphasis should be placed on an integrated approach, based on the notion of the operational documents as a complete system.
A flight safety documents system should be organized according to criteria which ensure easy access to information required for flight and ground operations contained in the various operational documents comprising the system and which facilitate management of the distribution and revision of operational documents.
Information contained in a flight safety documents system should be grouped
according to the importance and use of the information, as follows:
(i) Time critical information, e.g., information that can jeopardize the safety of the operation if not immediately available;
(ii) Time sensitive information, e.g., information that can affect the level of safety or delay the operation if not available in a short time period;
(iii) Frequently used information;
(iv) Reference information, e.g., information that is required for the operation but does not fall under (2) or (3) above; and
(v) Information that can be grouped based on the phase of operation in which it is used.
c. Time critical information should be placed early and prominently in the flight
safety documents system.
d. Time critical information, time sensitive information, and frequently used information should be placed in cards and quick-reference guides.
e. The flight safety documents system should be validated before deployment, under realistic conditions. Validation should involve the critical aspects of the information use, in order to verify its effectiveness. Interactions among all groups that can occur during operations should also be included in the validation process.
f. A flight safety documents system should maintain consistency in terminology and in the use of standard terms for common items and actions.
g. Operational documents should include a glossary of terms, acronyms and their standard definition, updated on a regular basis to ensure access to the most recent terminology. All significant terms, acronyms and abbreviations included in the flight documents system should be defined.
h. A flight safety documents system should ensure standardization across document types, including writing style, terminology, use of graphics and symbols, and formatting across documents. This includes a consistent location of specific types of information, consistent use of units of measurement and consistent use of codes.
i. A flight safety document system needs to include a verification mechanism to ensure that, whenever a section of a document is amended, all other documents likely to be affected are identified and that consequential amendments are duly coordinated and agreed to by the responsible departments before the amendment is processed.
Operators should monitor deployment of the flight safety documents system to ensure appropriate and realistic use of the documents, based on the characteristics of the operational environment and in a way which is both operationally relevant and beneficial to operational personnel. This monitoring should include a formal feedback system for obtaining input from operational personnel.
AMENDMENT Operators should develop an information gathering, review, distribution and revision control system to process information and data obtained from all sources relevant to the type of operation conducted, including, but not limited to, the State of Operator, State of design, State of Registry, manufacturers and equipment vendors.
Operators should develop an information gathering, review and distribution system to process information resulting from changes that originate within the operator, including:
a) Changes resulting from the installation of new equipment;
b) Changes in response to operating experience;
c) Changes in an operator’s policies and procedures;
d) Changes in an operator certificate; and
e) Changes for purposes of maintaining cross fleet standardization.
Note.- Operators should ensure that crew coordination philosophy, policies and procedures are specific to their operation.
Flight safety documents system should be reviewed:
a) On a regular basis (at least once a year);
b) After major events (mergers, acquisitions, rapid growth, downsizing etc.)
c) After technology changes (introduction of new equipment); and
d) After changes in safety regulations. Operators should develop methods of communicating new information. The specific methods should be responsive to the degree of communication urgency.