This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Guidelines for Time-Limited-Dispatch (TLD) Analysis for Electronic Engine Control Systems
- Aerospace Standard
- ARP5107C
- Revised
Downloadable datasets available
Annotation ability available
Sector:
Issuing Committee:
Language:
English
Scope
This SAE Aerospace Recommended Practice (ARP) provides methodologies and approaches which have been used for conducting and documenting the analyses associated with the application of Time Limited Dispatch (TLD) to the thrust control reliability of Full Authority Digital Engine Control (FADEC) systems. The TLD concept is one wherein a fault-tolerant system is allowed to operate for a predetermined length of time with faults present in the redundant elements of the system, before repairs are required. This document includes the background of the development of TLD, the structure of TLD that was developed and implemented on present generation commercial transports, and the analysis methods used to validate the application of TLD on present day FADEC equipped aircraft. Although this document is specific to TLD analyses (for FADEC systems) of the loss of thrust control, the techniques and processes discussed in this document are considered applicable to other FADEC system failure effects or other systems, such as: thrust reverser, and propeller control systems, and overspeed protection systems.
Rationale
This standard has been revised to harmonize its content with EASA CM-MMEL-001 and reflect new methodologies in the field.
Recommended Content
Topic
Data Sets - Support Documents
| Title | Description | Download |
|---|---|---|
| Unnamed Dataset 1 | ||
| Table 1 | Typical categorization of FADEC system elements | |
| Table 1 | Typical categorization of FADEC system elements | |
| Table 1 | Typical categorization of FADEC system elements | |
| Table 1 | Typical categorization of FADEC system elements | |
| Table 1 | Typical categorization of FADEC system elements | |
| Table 1 | Typical categorization of FADEC system elements | |
| Table 1 | Typical categorization of FADEC system elements | |
| Table 1 | Typical categorization of FADEC system elements | |
| Table 1 | Typical categorization of FADEC system elements | |
| Table 2 | Spreadsheet solution for FADEC system example shown in | |
| Unnamed Dataset 12 | ||
| Unnamed Dataset 13 | ||
| Unnamed Dataset 14 | ||
| Unnamed Dataset 15 | ||
| Unnamed Dataset 16 | ||
| Unnamed Dataset 17 | ||
| Unnamed Dataset 18 | ||
| Table 3 | Spread sheet showing the calculations for determining the coefficients a , a , b , b , c , c , d , and d used in | |
| Table 4 | Dual engine specific risk as a function of dispatch configuration |
Issuing Committee
E-36 Electronic Engine Controls Committee
Areas of interest will include, but not be limited to, the design, installation, operation and maintenance of engine control system components including metering components and actuators and the interface and communication methods for (A) Cockpit Displays, (B) Flight Control, ¿ Diagnostic and Health Monitoring Systems. Coordination with other SAE committees will occur to minimize redundant activities within the organization and maximize the benefit of additional recommendations and standards.
For details about SAE's online privacy policy; copyright, content license, and reliability statements; and membership information, click on the link to "Info on Privacy, Copyright and Membership" link in the folders area below. No copyrighted material may be posted in this forum. SAE is not liable for opinions expressed or information posted to this forum. All information posted becomes the property of SAE.Reference
| Number | Title |
|---|---|
| 14 CFR Parts 23, 25, 27, 29, 33 | This document is not part of the subscrption. |
* Redlines comparisons are available for those standards
listed in the Revision History that contain a radio button. A
redline comparison of the current version against a revision is
accomplished by selecting the radio button next to the standard and
then selecting 'compare'. At this time, Redline versions only exist
for some AMS standards. SAE will continue to add redline versioning
with ongoing updates to SAE MOBILUS.