7E004 Other “technology” as follows (see List of Items Controlled).

TSR: N/A

STA: (1) Paragraph (c)(1) of License Exception STA (§ 740.20(c)(1) of the EAR) may not be used for 7E004, except for 7E004.a.7. (2) Paragraph (c)(2) of License Exception STA (§ 740.20(c)(2) of the EAR) may not be used for 7E004, except for 7E004.a.7.

Related Controls: (1) See also 7E001, 7E002, 7E101, and 7E994. (2) In addition to the Related Controls in 7E001, 7E002, and 7E101 that include MT controls, also see the MT controls in 7E104 for design “technology” for the integration of the flight control, guidance, and propulsion data into a flight management system, designed or modified for rockets or missiles capable of achieving a “range” equal to or greater than 300 km, for optimization of rocket system trajectory; and also see 9E101 for design “technology” for integration of air vehicle fuselage, propulsion system and lifting control surfaces, designed or modified for unmanned aerial vehicles capable of achieving a “range” equal to or greater than 300 km, to optimize aerodynamic performance throughout the flight regime of an unmanned aerial vehicle.

Related Definitions: N/A.

Items:

a. “Technology” for the “development” or “production” of any of the following:

a.1. [Reserved]

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

a.3. Three dimensional displays for “aircraft”;

a.4. [Reserved]

a.5. Electric actuators (i.e., electromechanical, electrohydrostatic and integrated actuator package) “specially designed” for 'primary flight control';

a.6. 'Flight control optical sensor array' “specially designed” for implementing “active flight control systems”; or

a.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;

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

b.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”;

b.2. [Reserved]

b.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”;

b.4. Real-time algorithms to identify component failures and reconfigure force and moment controls to mitigate “active flight control system” degradations and failures;

b.5. Integration of digital flight control, navigation and propulsion control data, into a digital flight management system for “total control of flight”;

b.6. [Reserved]

b.7. “Technology” “required” for deriving the functional requirements for “fly-by-wire systems” having all of the following:

b.7.a. 'Inner-loop' airframe stability controls requiring loop closure rates of 40 Hz or greater; and

b.7.b. Having any of the following:

b.7.b.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;

b.7.b.2. Couples controls in two or more axes while compensating for 'abnormal changes in aircraft state';

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

b.7.b.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;

b.8. “Technology” “required” for deriving the functional requirements of “fly-by-wire systems” to achieve all of the following:

b.8.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

b.8.b. Probability of loss of control of the ”aircraft” being less (better) than 1 × 10−9 failures per flight hour;

c. “Technology” for the “development” of helicopter systems, as follows:

c.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:

c.1.a. Collective controls;

c.1.b. Cyclic controls;

c.1.c. Yaw controls;

c.2. “Circulation-controlled anti-torque or circulation-controlled direction control systems”;

c.3. Rotor blades incorporating 'variable geometry airfoils', for use in systems using individual blade control.