曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

To accomplish its objectives, CICTT has developed the following common taxonomies and definitions:  Phase of Flight, Occurrence Categories, Aircraft Make/Model/Series tables, Engine Make/Model tables, and a detailed taxonomy for accident/incident data systems.
It is important to note that CICTT does not expect governments, international organizations, and corporations to immediately change existing data systems or existing definitions.  The intent is to provide “target” taxonomies and definitions for adoption by organizations planning for, and implementing new safety systems.
“Occurrence” is defined as “accident or incident” throughout this document.  Generally, accidents and incidents differ only in the degree of injury sustained by persons involved or in damage sustained to the aircraft.  Each category has a unique name and identifier to permit common coding in accident/incident systems, a text definition, and usage notes to clarify the category and aid in coding occurrences.
An important element of the occurrence category design is that it permits the association of multiple categories with an occurrence.  Meaning, for example, if an engine failure occurred, AND loss of control followed, the occurrence would be coded in both categories.  Multiple coding supports the primary focus of CICTT—accident prevention—in which every pertinent element should be investigated, recorded, and analyzed.
As an aid to organizations using the definitions, a sample table grouping the categories into major operational categories is also included as Attachment A.
Contact point for all CICTT work: CICTT@intlaviationstandards.org

 

ABNORMAL RUNWAY CONTACT (ARC)

Usage Notes:
.  
Events such as hard/heavy landings, long/fast landings, off center landings, crabbed landings, nose wheel first touchdown, tail strikes, and wingtip/nacelle strikes are included in this category.

.  
Gear-up landings are also recorded here. However, if a system/component failure or malfunction occurred, which led to the gear up landing, the event is also coded under the appropriate system/component failure or malfunction category.   

.  
Do not use this category for runway contacts after losing control, e.g., runway contact after take-off.

.  
Occurrences in which the gear collapses during the take-off run or the landing roll are not

included here except if a condition in the usage notes above has been met. NOTE: Throughout this document the term runway or landing area is taken in its broadest sense and includes runways, landing strips, waterways, unimproved landing areas, and landing pads (which may include offshore platforms, building roofs, roads, ships, and fields), or other landing areas.
NOTE: Does not include helicopter hard/heavy landings after an off-field emergency
autorotation when there was no intention to land before the autorotation was entered.  NOTE: Includes (tail) rotor striking the intended landing surface during take-off and landing.  However, collisions with obstacles during take-off and landing, such as trees or walls, should be coded under TOL.
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：AVIATION OCCURRENCE CATEGORIES DEFINITIONS AND USAGE NOTES(5)