Document ID: chunk:federal_register_of_legislation:F2024L01024:front:0:p228
Version: federal_register_of_legislation:F2024L01024
Segment Type: other
Provision Reference: 
Character Range: 651583–654981

"fly‑by‑light systems" "active flight control systems";
2. Not used;
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 include algorithms for the purpose of off‑line maintenance.
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 include algorithms for the elimination of fault effects through comparison of redundant data sources, or off‑line pre‑planned responses to anticipated failures.
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 apply to:
a. "Technology" for integration of digital flight control, navigation and propulsion control data, into a digital flight management system for 'flight path optimisation';
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.
7. E. 004. b. 6. Not used;
7. E. 004. b. 7. "Technology" "required" for deriving the functional requirements for "fly‑by‑wire systems" having all of the following:
                  a. 'Inner‑loop' airframe stability controls requiring loop closure rates of 40 Hz or greater; and
                  Technical Note:
                  For the purposes of 7E004.b.7.a., 'inner-loop' refers to functions of "active flight control systems" that automate airframe stability controls.
              b. Having any of the following:
                     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. Couples controls in two or more axes while compensating for 'abnormal changes in aircraft state';
                     Technical Note:
                     For the purposes of 7E004.b.7.b.2., 'abnormal changes in aircraft state' include in-flight structural damage, loss of engine thrust, disabled control surface, or destabilizing shifts in cargo load.
                     3. Performs the functions specified by 7E004.b.5.; or
                     Note: 7E004.b.7.b.3. does not apply to autopilots.
                     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;
7. E. 004. b. 8. "Technology" "required" for deriving the functional requirements for "fly‑by‑wire systems" to achieve all of the following:
                  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. Probability of loss of control of the "aircraft" being less (better) than 1x10‑9 failures per flight hour;
Note: 7E004.b. does not