OpenLegislation

Division 7E Technology

United Kingdom

Original text. Later amendments are not shown.

7E001

  • "Technology" according to the General Technology Note for the "development" of equipment or "software", specified in 7A, 7B, 7D001, 7D002, 7D003, 7D005 and 7D101 to 7D103.

    Note: 7E001 includes key management "technology" exclusively for equipment specified in 7A005.a.

    • 7E002

  • "Technology" according to the General Technology Note for the "production" of equipment specified in 7A or 7B.

    • 7E003

  • "Technology" according to the General Technology Note for the repair, refurbishing or overhaul of equipment specified in 7A001 to 7A004.

    Note: 7E003 does not control "technology" for maintenance, directly associated with calibration, removal or replacement of damaged or unserviceable LRUs and SRAs of a "civil aircraft" as described in ‘Maintenance Level I’ or ‘Maintenance Level II’.

    N.B. See Technical Notes to 7B001.

    • 7E004

  • Other "technology" as follows:

    1. a..

      "Technology" for the "development" or "production" of any of the following:

      1. 1..

        Not used;

      2. 2..

        Air data systems based on surface static data only, i.e., which dispense with conventional air data probes;

      3. 3..

        Three dimensional displays for "aircraft";

      4. 4..

        Not used;

      5. 7E004 a.5..

        Electric actuators (i.e., electromechanical, electrohydrostatic and integrated actuator package) specially designed for ‘primary flight control’;

        Technical Note:

        ‘Primary flight control’ is "aircraft" stability or manoeuvring control using force/moment generators, i.e. aerodynamic control surfaces or propulsive thrust vectoring.

      6. 6..

        ‘Flight control optical sensor array’ specially designed for implementing "active flight control systems"; or

        Technical Note:

        A ‘flight control optical sensor array’ is a network of distributed optical sensors, using "laser" beams, to provide real-time flight control data for on-board processing.

      7. 7..

        "DBRN" systems designed to navigate underwater, using sonar or gravity databases, that provide a positioning "accuracy" equal to or less (better) than 0,4 nautical miles;

    2. b..

      "Development""technology", as follows, for "active flight control systems" (including "fly-by-wire systems" or "fly-by-light systems"):

      1. 1..

        Photonic-based "technology" for sensing "aircraft" or flight control component state, transferring flight control data, or commanding actuator movement, "required" for "fly-by-light systems""active flight control systems";

      2. 2..

        Not used;

      3. 3..

        Real-time algorithms to analyze component sensor information to predict and preemptively mitigate impending degradation and failures of components within an "active flight control system";

        Note: 7E004.b.3. does not control algorithms for purpose of off-line maintenance.

      4. 4..

        Real-time algorithms to identify component failures and reconfigure force and moment controls to mitigate "active flight control system" degradations and failures;

        Note: 7E004.b.4. does not control algorithms for the elimination of fault effects through comparison of redundant data sources, or off-line pre-planned responses to anticipated failures.

      5. 5..

        Integration of digital flight control, navigation and propulsion control data, into a digital flight management system for "total control of flight";

        Note: 7E004.b.5. does not control:

        1. a..

          "Technology" for integration of digital flight control, navigation and propulsion control data, into a digital flight management system for ‘flight path optimisation’;

        2. b..

          "Technology" for "aircraft" flight instrument systems integrated solely for VOR, DME, ILS or MLS navigation or approaches.

        Technical Note:

        ‘Flight path optimisation’ is a procedure that minimises deviations from a four-dimensional (space and time) desired trajectory based on maximising performance or effectiveness for mission tasks.

      6. 7E004 b.6..

        Not used;

      7. 7..

        "Technology""required" for deriving the functional requirements for "fly-by-wire systems" having all of the following:

        1. a..

          ‘Inner-loop’ airframe stability controls requiring loop closure rates of 40 Hz or greater; and

          Technical Note:

          ‘Inner-loop’ refers to functions of "active flight control systems" that automate airframe stability controls.

        2. b..

          Having any of the following:

          1. 1..

            Corrects an aerodynamically unstable airframe, measured at any point in the design flight envelope, that would lose recoverable control if not corrected within 0,5 seconds;

          2. 2..

            Couples controls in two or more axes while compensating for ‘abnormal changes in aircraft state’;

            Technical Note:

            ‘Abnormal changes in aircraft state’ include in-flight structural damage, loss of engine thrust, disabled control surface, or destabilizing shifts in cargo load.

          3. 3..

            Performs the functions specified in 7E004.b.5.; or

            Note: 7E004.b.7.b.3. does not control autopilots.

          4. 4..

            Enables "aircraft" to have stable controlled flight, other than during take-off or landing, at greater than 18 degrees angle of attack, 15 degrees side slip, 15 degrees/second pitch or yaw rate, or 90 degrees/second roll rate;

      8. 8..

        "Technology""required" for deriving the functional requirements for "fly-by-wire systems" to achieve all of the following:

        1. a..

          No loss of control of the "aircraft" in the event of a consecutive sequence of any two individual faults within the "fly-by-wire system"; and

        2. b..

          Probability of loss of control of the "aircraft" being less (better) than 1 x 10-9 failures per flight hour;

      Note: 7E004.b. does not control "technology" associated with common computer elements and utilities (e.g., input signal acquisition, output signal transmission, computer program and data loading, built-in test, task scheduling mechanisms) not providing a specific flight control system function.

    3. c..

      "Technology" for the "development" of helicopter systems, as follows:

      1. 1..

        Multi-axis fly-by-wire or fly-by-light controllers, which combine the functions of at least two of the following into one controlling element:

        1. a..

          Collective controls;

        2. b..

          Cyclic controls;

        3. c..

          Yaw controls;

      2. 2..

        "Circulation-controlled anti-torque or circulation-controlled direction control systems";

      3. 7E004 c.3..

        Rotor blades incorporating ‘variable geometry airfoils’, for use in systems using individual blade control.

        Technical Note:

        ‘Variable geometry airfoils’ use trailing edge flaps or tabs, or leading edge slats or pivoted nose droop, the position of which can be controlled in flight.

    • 7E101

  • "Technology" according to the General Technology Note for the "use" of equipment specified in 7A001 to 7A006, 7A101 to 7A106, 7A115 to 7A117, 7B001, 7B002, 7B003, 7B102, 7B103, 7D101 to 7D103.

    • 7E102

  • "Technology" for protection of avionics and electrical subsystems against electromagnetic pulse (EMP) and electromagnetic interference (EMI) hazards, from external sources, as follows:

    1. a..

      Design "technology" for shielding systems;

    2. b..

      Design "technology" for the configuration of hardened electrical circuits and subsystems;

    3. c..

      Design "technology" for the determination of hardening criteria of 7E102.a. and 7E102.b.

    • 7E104

  • "Technology" for the integration of the flight control, guidance, and propulsion data into a flight management system for optimization of rocket system trajectory.