# baseURI: http://onto.fel.cvut.cz/ontologies/aviation/376-form-ext # imports: http://onto.fel.cvut.cz/ontologies/aviation/376-form-0.2 # imports: http://spinrdf.org/spin @prefix form: . @prefix form376: . @prefix form376ext: . @prefix owl: . @prefix rdf: . @prefix rdfs: . @prefix sp: . @prefix spin: . @prefix xsd: . rdf:type owl:Ontology ; owl:imports ; owl:imports ; . form376ext:entity-type rdf:type owl:Class ; spin:query [ rdf:type sp:Construct ; sp:templates ( [ sp:object [ sp:varName "label"^^xsd:string ; ] ; sp:predicate rdfs:label ; sp:subject [ sp:varName "term"^^xsd:string ; ] ; ] [ sp:object [ sp:varName "comment"^^xsd:string ; ] ; sp:predicate rdfs:comment ; sp:subject [ sp:varName "term"^^xsd:string ; ] ; ] [ sp:object owl:NamedIndividual ; sp:predicate rdf:type ; sp:subject [ sp:varName "term"^^xsd:string ; ] ; ] [ sp:object form376ext:entity-type ; sp:predicate rdf:type ; sp:subject [ sp:varName "term"^^xsd:string ; ] ; ] [ sp:object [ sp:varName "top_section"^^xsd:string ; ] ; sp:predicate form376ext:has-relevant-part ; sp:subject [ sp:varName "term"^^xsd:string ; ] ; ] ) ; sp:text """CONSTRUCT { ?term rdfs:label ?label . ?term rdfs:comment ?comment . ?term a owl:NamedIndividual . ?term a form376ext:entity-type . ?term form376ext:has-relevant-part ?top_section . } WHERE { GRAPH { ?term . ?term rdfs:label ?label . ?term ?comment . BIND ( AS ?type) . } . ?top_section a form:section . FILTER NOT EXISTS { ?other_section form:has-subsection ?top_section . } . }"""^^xsd:string ; sp:where ( [ rdf:type sp:NamedGraph ; sp:elements ( [ sp:object [ sp:varName "term"^^xsd:string ; ] ; sp:predicate ; sp:subject ; ] [ sp:object [ sp:varName "label"^^xsd:string ; ] ; sp:predicate rdfs:label ; sp:subject [ sp:varName "term"^^xsd:string ; ] ; ] [ sp:object [ sp:varName "comment"^^xsd:string ; ] ; sp:predicate ; sp:subject [ sp:varName "term"^^xsd:string ; ] ; ] [ rdf:type sp:Bind ; sp:expression ; sp:variable [ sp:varName "type"^^xsd:string ; ] ; ] ) ; sp:graphNameNode ; ] [ sp:object form:section ; sp:predicate rdf:type ; sp:subject [ sp:varName "top_section"^^xsd:string ; ] ; ] [ rdf:type sp:Filter ; sp:expression [ rdf:type sp:notExists ; sp:elements ( [ sp:object [ sp:varName "top_section"^^xsd:string ; ] ; sp:predicate form:has-subsection ; sp:subject [ sp:varName "other_section"^^xsd:string ; ] ; ] ) ; ] ; ] ) ; ] ; rdfs:label "Entity type"^^xsd:string ; rdfs:subClassOf owl:Thing ; . form376ext:has-irrelevant-part rdf:type owl:ObjectProperty ; rdfs:label "has-irrelevant-part"^^xsd:string ; . form376ext:has-relevant-part rdf:type owl:ObjectProperty ; rdfs:label "has-relevant-part"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • This category includes the intentional maneuvering of the aircraft to avoid a collision with terrain, objects/obstacles, weather or aircraft (note: the effect of intentional maneuvering is the key consideration). • Abrupt maneuvering may also result in a loss of control or system/component failure or malfunction. In this case the event is coded under both categories (e.g., AMAN and LOC-I, AMAN and SCF-NP, or AMAN and SCF-PP). • Abrupt maneuvering may also occur on ground, examples include hard braking maneuver, rapid change of direction to avoid collisions etc."""^^xsd:string ; rdfs:label "1 - AMAN: Abrupt maneuvre"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Includes accumulations that occur inflight or on the ground (i.e., deicing-related). • Carburetor and induction icing events are coded in the FUEL Related (FUEL) category. • Windscreen icing which restricts visibility is also covered here. • Includes ice accumulation on sensors, antennae, and other external surfaces. • Includes ice accumulation on external surfaces including those directly in front of the engine intakes."""^^xsd:string ; rdfs:label "10 - ICE: Icing"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • May be used as a precursor to CFIT, LOC-I or LALT. • Applicable if the pilot was flying according to Visual Flight Rules (VFR), as defined in Annex 2 – Rules of the Air – to the Convention on International Civil Aviation and by any reason found oneself inadvertently in IMC • Only to be used when loss of visual references is encountered, • Only to be used if pilot not qualified to fly in IMC and/or aircraft not equipped to fly in IMC"""^^xsd:string ; rdfs:label "100 - UIMC: Unintended flight in IMC"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Includes cases where external load or the load lifting equipment used (e.g. long line, cable) contacts terrain, water surface or objects. • Includes cases where the load or, in the absence of a load, the load lifting equipment strikes or becomes entangled with the main rotor, tail rotor, or the helicopter fuselage. • Includes injuries to ground crew handling external loads as result of contact with/dropping/inadvertent release of external load. • Includes ground injuries to ground crew handling external loads due to the downwash effect or falling branch, trees etc. • Includes external hoist, human external cargo, long lines. • If the preparation of the external load by ground crew played a role, also code under RAMP. • Failures or malfunctions of the onboard external load handling lifting equipment or release systems should be coded under SCF-NP, as these are considered to be aircraft systems."""^^xsd:string ; rdfs:label "101 - EXTL: External load related occurrences"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • To be used only in cases where the crew was aware of the true location of the obstacle, but its clearance from the aircraft flightpath was inadequate. • Includes contact with obstacles, such as vegetation, trees and walls, snow drifts, power cables, telegraph wires and antennae, offshore platforms, maritime vessels and structures, land structures and buildings. • Includes collisions during take-off to and landing from the hover. • Includes water obstacles during take-off from water (e.g. waves, dead-heads, ships, swimmers). • Not to be used for occurrences classified under CFIT, LOC-I or SCF-PP."""^^xsd:string ; rdfs:label "102 - CTOL: Collision with obstacle(s) during take-off and landing"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • Applicable only to aircraft that rely on static lift to maintain or increase flight altitude, namely sailplanes, gliders, hang gliders and paragliders, balloons and airships. • All static lift forms to be considered, including atmospheric lift, namely from Orographic, Thermal, Mountain Wave and Convergence Zone, and buoyancy lift namely from lighter than air gas or hot air. • Also include motorglider and paramotor aircraft if operating under static atmospheric lift conditions and the engine could not be started. • If the aircraft was flying intentionally at low height above the terrain, use LALT instead (typical cases occur with gliders in competition flying)."""^^xsd:string ; rdfs:label "103 - LOLI: Loss of lifting conditions en-route"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Applicable both to aircraft under tow by winch or by another aircraft or to aircraft executing towing. • To be used in events only after reaching airborne phase. • Includes loss of control because of entering the towing aircraft wake turbulence and events where of airspeed is out of limits during tow."""^^xsd:string ; rdfs:label "104 - GTOW: Glider towing related events"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • ‘Terrain’ includes: water, vegetation, rocks, and other natural elements laying, on or growing out of, the earth. • Includes ostentatious display, manoeuvring at low height, aerobatics, sight seeing, demonstration flights, aerial inspection, avalanche mining, human hoist or human cargo sling, search and rescue operations, aerial application, intentional helicopter operations close to obstacles during aerial work and scud running (ducking under low visibility conditions). • Also includes intentional manoeuvring in close proximity to cliffs, mountains, into box canyons, and similar flights where the aircraft aerodynamic capability is not sufficient to avoid impact. • If there is a loss of control during low altitude operations, both loss of control – inflight (LOC-I) and LALT are coded. • NOTE: excluding rotorcraft air taxi phase of flight. • NOTE: includes maneuvering at low height while searching for an off-aerodrome landing location. Do not use LALT in conjunction with CFIT."""^^xsd:string ; rdfs:label "11 - LALT: Low altitude operations"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • Used only for non-airborne phases of flight, i.e., ground/surface operations. • The loss of control may result from a contaminated runway or taxiway (e.g., rain, snow, ice, slush). • The loss of control during ground operations can occur as the result of other occurrence categories as well. For example, LOC-G may result from a system/component failure or malfunction to the powerplant (SCF-PP) or non-powerplant (SCF-NP), or from evasive action taken during a Runway Incursion (RI-VAP, or RI-A). For these occurrences, the event is coded under both categories (e.g., LOC-G and SCF-PP, LOC-G and SCF-NP, or LOC-G and RI-VAP or RI-A). • Do not use when a mechanical failure rendered the aircraft uncontrollable. • Rotorcraft during sloping ground or moving helideck operations, dynamic rollover and ground resonance events are also included here."""^^xsd:string ; rdfs:label "12 - LOC-G: Loss of control - ground"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Loss of control inflight is an extreme manifestation of a deviation from intended flightpath. The phrase “loss of control” may cover only some of the cases during which an unintended deviation occurred. It is therefore suggested that the occurrence title is reviewed and changed accordingly. For example: Deviation from Intended Flightpath- DEV. Usage Notes: • Used only for airborne phases of flight where aircraft control was lost. • Loss of control can occur during either Instrument Meteorological Conditions (IMC) or Visual Meteorological Conditions (VMC). • The loss of control during flight may occur as a result of a deliberate maneuver (e.g., stall/spin practice) • Occurrences involving configuring the aircraft (e.g., flaps, slats, on-board systems, etc) are included as well as rotorcraft retreating blade stall • Stalls are considered loss of control and are included here. • Rotorcraft occurrences which involve power settling (vortex ring), or settling with power to ground contact are coded here and also as ARC if during normal landing or takeoff. • Rotorcraft External Load operations involving loss of control related to the external load should be coded as LOC-I as well as EXTL. • Includes Rotorcraft “Loss of Tail Rotor Effectiveness”. • Includes Loss of Control during practice or emergency autorotation. • Includes Pilot induced or assisted oscillations. • For icing-related events, which are also loss of control, code both LOC-I and ICE). • If the loss of control is a direct result of a system/component failure or malfunction (SCF), code the occurrence as an SCF-NP, or SCF-PP only. However, loss of control may follow less severe system/component failures, and in this case, code both categories. • Cockpit crew vision-related events and flight in degraded visual environments (for example, obscuration, black hole approach events, brownouts or whiteout events), where the aircraft is flown under control into terrain, water, or obstacles, are coded under CFIT, not LOC-I"""^^xsd:string ; rdfs:label "13 - LOC-I: Loss of control - inflight"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • Includes all collisions between aircraft while both aircraft are airborne. • Both air traffic control and cockpit crew separation-related occurrences are included. • To be used for AIRPROX reports • Genuine TCAS alerts are included here."""^^xsd:string ; rdfs:label "14 - MAC: Airprox/ ACAS alert/ loss of separation/ (near) midair collisions"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • Only applicable during either the takeoff or landing phase • The excursion may be intentional or unintentional. For example, the deliberate veer off to avoid a collision, brought about by a Runway Incursion. In this case, code both categories • Use RE in all cases where the aircraft left the runway/helipad/helideck regardless of whether the excursion was the consequence of another event or not."""^^xsd:string ; rdfs:label "15 - RE: Runway excursion"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • If the failure renders the aircraft uncontrollable it is coded as SCF-NP only, not as loss of control (LOC-I or LOC-G). However, if the failure does not render the aircraft uncontrollable, but leads to a loss of control, code the event under both SCF-NP and LOC-I or LOC-G, as appropriate. • Rotorcraft cyclic, collective, and tail rotor drive and control system failures/malfunctions are also coded here. • Includes errors or failures in software and database systems. • Includes non-powerplant parts or pieces separating from an aircraft. • Includes all failures/malfunctions, including those related to or caused by maintenance issues."""^^xsd:string ; rdfs:label "18 - SCF-NP: System/component failure or malfunction [non-powerplant]"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • If the failure renders the aircraft uncontrollable it is coded as SCF-PP only, not as loss of control (LOC-I or LOC-G). However, if the failure does not render the aircraft uncontrollable, but leads to a loss of control, code the event under both SCF-PP and LOC-I or LOC-G, as appropriate. • Includes failures or malfunctions of any of the following: propellers, rotors, propeller/main rotor drive train (gearbox, transmission), reversers, and powerplant controls. • Includes powerplant parts or pieces separating from a powerplant. • Includes all failures/malfunctions, including those related to or caused by maintenance issues. • Rotorcraft cyclic, collective and tail rotor drive and control failures or malfunctions are coded as non-powerplant failures (SCF-NP), not SCF-PP. • The following fuel-related powerplant problems are coded under the category FUEL, not under the category SCF-PP: fuel exhaustion; fuel starvation/mismanagement; fuel contamination; wrong fuel; carburetor and induction icing. NOTE: For sub-categorization of SCF-PP, a separate taxonomy has been developed and can be found on the CICTT website http://intlaviationstandards.org."""^^xsd:string ; rdfs:label "19 - SCF-PP: powerplant failure or malfunction"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """ABNORMAL RUNWAY CONTACT (ARC) Any landing or takeoff involving abnormal runway or landing surface contact. 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. NOTE: Does not include off-field landing by gliders."""^^xsd:string ; rdfs:label "2 - ARC: Abnormal runway contact"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • While security related acts can lead to accidents as defined as by ICAO Annex 13, they are not considered accidents by some organizations. Regardless, these events have similar consequences in that they result in serious injury or death to person(s) and/or substantial damage to the aircraft. For these reasons, they are categorized as security-related occurrences for prevention purposes only. • Examples include: a) hijacking and/or aircraft theft; b) interference with a crewmember (e.g., unruly passengers); c) flight control interference; d) ramp/runway/taxiway security; e) sabotage; f) suicide; and g) acts of war."""^^xsd:string ; rdfs:label "20 - SEC: Security related"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Includes encounters with turbulence in clear air, mountain wave, mechanical, and/or cloud associated turbulence. • Wake vortex encounters are also included here. • Flights into windshear or thunderstorm related turbulence are coded as WSTRW. • Includes turbulence encountered by aircraft when operating around or at buildings, structures and objects."""^^xsd:string ; rdfs:label "21 - TURB: Turbulence encounter"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • An undershoot/overshoot of a runway/helipad/helideck occurs in close proximity to the runway/helipad/helideck and also includes offside touchdowns and any occurrence where the landing gear touches off the runway/helipad/helideck surface. • Off-airport emergency landings are excluded from this category. • To be used for occurrences during the landing phase. • Includes offside touchdowns on heliports, helidecks and other defined areas to be used wholly or in part for the arrival, departure and surface movement of helicopters (does not include helicopter unprepared or natural landing sites). Do not use ARC in conjunction with USOS."""^^xsd:string ; rdfs:label "22 - USOS: Undershoot/overshoot"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Includes flight into windshear and/or thunderstorm related weather. • Includes inflight events related to hail • Includes events related to lightning strikes • Includes events related to heavy rain (not just in a thunderstorm) • Icing and turbulence encounters are coded separately (see ICE and TURB)."""^^xsd:string ; rdfs:label "23 - WSTRW: Windshear or thunderstorm."^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Includes deficiencies/issues associated with a State approved Aerodrome- runways, taxiways, ramp area, parking area, buildings and structures, Crash/Fire/Rescue (CFR) services, obstacles on the Aerodrome property, lighting, markings, signage, procedures, policies, and standards. • Examples include closed runways, improperly marked runways, construction interference, lighting failures, signage limitations, etc. • Occurrences do not necessarily involve an aircraft. • Effects of Aerodrome design are also included here. For example, building layout and architecture which leads to surface wind disruptions would be coded as both ADRM and WSTRW or TURB as appropriate. • Includes heliports (excludes unprepared or natural landing sites). • Includes loose foreign objects on aerodromes and on heliports (excludes unprepared or natural landing sites) Includes failures of the winch launch equipment (gliders)."""^^xsd:string ; rdfs:label "24 - ADRM: Aerodrome"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • Includes ATC facility/personnel failure/degradation, CNS service failure/degradation, procedures, policies, and standards • Examples include, NAVAID outage, NAVAID service error, controller error, Supervisor error, ATC computer failure, Radar failure, and navigation satellite failure • Occurrences do not necessarily involve an aircraft. NOTE: ATM includes all of the facilities, equipment, personnel, and procedures involved in the provision of State approved Air Traffic Services."""^^xsd:string ; rdfs:label "25 - ATM: ATM/CNS"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Includes significant events related to carry-on baggage, supplemental oxygen, or missing/non-operational cabin emergency equipment. • Includes inadvertent deployment of emergency equipment. • Includes medical emergency for a person other than a flight crewmember or a medical evacuation patient. • Excludes turbulence and other weather-related events, which are covered under TURB, ICE, or WSTRW respectively."""^^xsd:string ; rdfs:label "26 - CABIN: Cabin safety events"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Includes encounters with wildlife on a runway in use. • Includes instances where evasive action is taken by the flight crew that leads to a collision off the runway or to consequences other than a collision (e.g., gear collapsing). • Runway incursions may occur at controlled or uncontrolled airports. • Excludes unprepared / natural landing sites. Includes encounters with wildlife other than birdstrikes which are coded as BIRD."""^^xsd:string ; rdfs:label "27 - RI-A: Runway incursion - animal"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Note: • From Procedures for Air Navigation Services – Air traffic Management (ICAO DOC 4444), first included in April 2004. • Excludes unprepared / natural landing sites."""^^xsd:string ; rdfs:label "28 - RI-VAP: Runway incursion - vehicle, aircraft or person"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-irrelevant-part form376:airspace-class ; form376ext:has-irrelevant-part form376:airspace-type ; form376ext:has-irrelevant-part form376:atm-contribution ; form376ext:has-irrelevant-part form376:effect-on-atm-service ; form376ext:has-irrelevant-part form376:fir-or-uir-name ; form376ext:has-irrelevant-part form376:number-of-injuries-on-aircraft ; form376ext:has-irrelevant-part form376:number-of-injuries-on-ground ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """A collision / near collision with or ingestion of one or several birds or wildlife. Usage Notes: • May occur in any phase of flight NOTE: Bird strikes were previously categorized as \"other\". Users may wish to update their historic data by replacing \"other\" with \"BIRD\" where the occurrence involved a bird / wildlife strike."""^^xsd:string ; rdfs:label "29 - BIRD: Birdstrike"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • CFIT is used only for occurrences during airborne phases of flight. • CFIT includes collisions with those objects extending above the surface (for example, towers, trees, power lines, cable car support, transport wires, power cables, telephone lines and aerial masts). • CFIT can occur during either Instrument Meteorological Conditions (IMC) or Visual Meteorological Conditions (VMC). • Includes instances when the cockpit crew is affected by visual illusions or degraded visual environment (e.g., black hole approaches and helicopter operations in brownout or whiteout conditions) that result in the aircraft being flown under control into terrain, water, or obstacles. • If control of the aircraft is lost (induced by crew, weather or equipment failure), do not use this category; use Loss of Control – Inflight (LOC–I) instead. • For an occurrence involving intentional low altitude operations (e.g., crop dusting, aerial work operations close to obstacles, and Search and Rescue (SAR) operations close to water or ground surface) use the Low Altitude Operations (LALT) code instead of CFIT. • Do not use this category for occurrences involving intentional flight into/toward terrain. Code all collisions with obstacles during take-off and landing under TOL. Code all suicides under Security Related (SEC) events. • Do not use this category for occurrences involving runway undershoot/overshoot, which are classified as Undershoot/Overshoot (USOS). • Includes flying into terrain during transition into forward flight. • For helicopter operations, not to be used for take-off and landing phases, except when the occurrence involves flying into terrain without indication of loss of control during transition into forward flight."""^^xsd:string ; rdfs:label "3 - CFIT: Controlled flight into or toward terrain"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • Includes cases where an injury(ies) was(were) sustained during the evacuation through an emergency exit or main cabin door. • Includes cases where the evacuation itself is the accident (in essence, had there not been an evacuation there would not have been an accident). • An unnecessary evacuation is one that was either erroneously commanded by the crew or uncommanded. • Only used for passenger carrying operations involving transport category aircraft. • Includes evacuation following a ditching or survivable crash landing in water provided one of the conditions above are met."""^^xsd:string ; rdfs:label "4 - EVAC: Evacuation"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Includes fire due to a combustive explosion from an accidental ignition source. • Includes fire and smoke from system/component failures/malfunctions in the cockpit, passenger cabin, or cargo area. • Non-combustive explosions such as tire burst and pressure bulkhead failures are coded under System/Component Failure - Non-Powerplant (SCF-NP). • Fire/Smoke resulting from an accident impact is coded under Fire/Smoke (post-impact) (F-POST)."""^^xsd:string ; rdfs:label "5 - F-NI: Fire/smoke (non-impact)"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • This category is only used for occurrences where post impact fire was a factor in the outcome. • This category is only used in conjunction with another category. For example: a system/component failure that also results in a post-impact fire will be coded as SCF-PP and F-POST or SCF-NP and F-POST."""^^xsd:string ; rdfs:label "6 - F-POST: Fire/smoke (post-impact)"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • The following fuel related definitions are provided for clarity: - Exhaustion: No usable fuel remains on the aircraft. - Starvation/mismanagement: Usable fuel remains on the aircraft, but it is not available to the engines. - Contamination: Any foreign substance (for example: water, oil, ice, dirt, sand, bugs) in the correct type of fuel for the given powerplant(s). - Wrong fuel: Fuel supplied to the powerplant(s) is incorrect, for example: Jet A into a piston powerplant, 80 octane into a powerplant requiring 100 octane. • Includes cockpit crew or ground crew-induced fuel-related problems that are not the result of mechanical failures. Interruptions of the fuel supply caused by mechanical failures are coded elsewhere as non-powerplant or powerplant system/component failures (SCF-NP or SCF-PP), as appropriate. • Also used when the wrong fuel causes a powerplant failure (e.g., through detonation). In this case it should be coded as FUEL, not as a system/component failure or malfunction- powerplant (SCF-PP). • Includes cases where there was a high risk of fuel exhaustion but there was no actual loss of power."""^^xsd:string ; rdfs:label "7 - FUEL: Fuel related"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; rdfs:comment """Usage Notes: • Includes collisions that occur while servicing, boarding, loading, and deplaning the aircraft also during boarding and disembarking while helicopter is hovering. • Includes injuries to people from propeller/main rotor/tail rotor/fan blade strikes. • Includes pushback/powerback/towing events. • Includes Jet Blast and Prop/rotor down wash ground handling occurrences. • Includes aircraft external preflight configuration errors (examples: improper loading and improperly secured doors and latches) that lead to subsequent events. • Includes all parking areas (ramp, gate, tiedowns). • Except for powerback events, which are coded here, if a collision occurs while the aircraft is moving under its own power in the gate, ramp, or tiedown area, code it as a ground collision (GCOL). • Includes operations at aerodromes, heliports, helidecks, and unprepared operating sites. • If external loads involved, also code as EXTL."""^^xsd:string ; rdfs:label "8 - RAMP: Ground Handling"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • Includes collisions with an aircraft, person, ground vehicle, obstacle, building, structure, etc. while on a surface other than the runway used for landing or intended for takeoff. • Ground collisions resulting from events categorized under Runway Incursion (RI) or Ground Handling (RAMP) are excluded from this category. NOTE: Taxiing includes ground and air taxiing for rotorcraft."""^^xsd:string ; rdfs:label "9 - GCOL: Ground Collision"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment "This category includes any occurrence type that is not covered by any other category."^^xsd:string ; rdfs:label "98 - OTHR: Other"^^xsd:string ; . rdf:type form376ext:entity-type ; rdf:type owl:NamedIndividual ; form376ext:has-relevant-part form376:aerodrome-related-data-fields ; form376ext:has-relevant-part form376:aircraft-damage-or-personal-injury-related-data-fields ; form376ext:has-relevant-part form376:aircraft-related-data-fields ; form376ext:has-relevant-part form376:data-fields-relating-to-air-navigation-services ; rdfs:comment """Usage Notes: • Includes cases where the aircraft is missing. • Includes those occurrences where there is not enough information at hand to classify the occurrence or where additional information is expected in due course to better classify the occurrence."""^^xsd:string ; rdfs:label "99 - UNK: Unknown or undetermined"^^xsd:string ; .