A highly structured conceptual framework (theory of multifactor flight domains) used to formalize the problem of flight safety research into complex situations.

A two-level knowledge model of flight, which includes:

1. the ‘micro-structure’ of flight (a single situation model), and
2. the ‘macro-structure’ of flight (a model of a large domain of situations).

A flight scenario scripting language in the form of events and processes used to quickly formalize the content and logic of any multifactor situation for simulation.

High-precision mathematical equations and computational algorithms of the system dynamics model, which describe:

• a human pilot’s (automaton’s) control tactics,
• non-linear unsteady 6DOF motion of the vehicle, and
• the effect of operating environment (pilot errors/ inattention, onboard malfunctions, demanding weather), including multifactor composites.

An interrelated set of unified data structures designed to accommodate input (‘parametric definition’), interim and output data flows of the system model.

Algorithms for automatic ‘mining’ of safety knowledge from virtual ‘flights’.

A design-of-experiments technique is used to plan autonomous fast-time simulation experiments on a PC, ‘plant’ and control the growth of a situational tree.

A family of color-coded knowledge maps designed to ‘granulate’ and represent high-level (‘bird’s eye view’) knowledge on the safety of a complex operational domain.

An integrated, standardized process of MS& based flight safety research:

Flight event (E)

The flight event is a special state of the system which is important to the pilot/designer in terms of flight control ‘switching’ logic and stands for a substantial change in the flight situation. Examples:

– “left engine out”
– “speed VR achieved”
– “altitude 360 ft and speed 180 kt”
– “on the runway”
– “high angle of attack”
– “30o left bank”
– “go-around decision”

Flight process (П)

The flight process is a time-history of one or several flight parameters which characterize a continuous aspect of the ‘pilot (automaton) – aircraft – operating environment’ system behavior (dynamics, control, weather, etc.). Examples:

– “steer runway’s centerline”
– “keep pitch at 10o in takeoff”
– “apply windshear (10 ft/s /H=30 ft)”
– “rpm decay during engine #1 failure”
– “extend flaps from 0o to 15o”
– “turn at 10o bank and 0o sideslip”
– “apply wet runway condition (m=0.3)”

Flight scenario (S)

The flight situation scenario is a concise plan of a flight situation. It specifies the content and the logic of flight in this situation. A flight scenario is depicted as a directed graph or a matrix. Examples:

– “normal takeoff”
– “aborted takeoff with LEO”
– “landing in crosswind conditions”
– “groundroll on wet runway”
– “coordinated turn at 15o bank”
– “stall in takeoff configuration”
– “cruise flight at 600 kt & 30000 ft”

Color

Code

Name

Definition

Green

I

Safe

The system state resides mainly inside the ‘green’ zone. As a maximum, the system state may stay, for a short period of time, in close proximity to the operational constraints, i.e. inside the ‘yellow’ zone, but must leave it by the end of the situation.

Salad

II-A

Conditionally

Safe – a

As a maximum, the system state may stay temporarily, or for a medium period of time, in close proximity to the operational constraints, i.e. inside the ‘yellow’ zone.

Yellow

II-B

Conditionally

Safe – b

As a maximum, the system state may stay for a long period of time in close proximity to the operational constraints, i.e. inside the ‘yellow’ zone.

Orange

III

Potentially

Unsafe

As a maximum, the system state may violate operational constraints, i.e. enter the ‘red’ zone, for a short or between short and medium period of time, but must leave it by the end of the situation.

Red

IV

Dangerous

(Prohibited)

As a maximum, the system state may stay beyond the operational constraints, i.e. inside the ‘red’ zone, for a medium or long period of time or till the end of the situation.

Black

V

Catastrophic

(‘Chain Reaction’)

There is at least one (i.e. for a very short time) occurrence of the violation of any operational constraint on the ‘black’ level.