UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

close
Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

close
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

EUROCAE - ER-005

CONTIGUOUS AIRCRAFT/SYSTEM DEVELOPMENT PROCESS EXAMPLE

active, Most Current
Organization: EUROCAE
Publication Date: 1 June 2012
Status: active
Page Count: 113
scope:

This ER provides a detailed example of the aircraft and systems development for a function of a hypothetical S18 aircraft. In order to present a clear picture, an aircraft function was broken down into a single system. A function was chosen which had sufficient complexity to allow use of all the methodologies, yet was simple enough to present a clear picture of the flow through the process. This function/system was analyzed using the methods and tools described in ED-79A/ARP4754A. The aircraft level function is "Decelerate Aircraft On Ground" and the system is the braking system. The interaction of the braking system functions with the aircraft are identified with the relative importance based on implied aircraft interactions and system availabilities at the aircraft level. This example does not include validation and verification of the aircraft level hazards and interactions with the braking system. However, the principles used at the braking system level can be applied at the higher aircraft level. The methodologies applied here are an example of one way to utilize the principles defined in ED-79A/ARP4754A. The function chosen was the braking system. Other formats may be used to accomplish the documentation, so long as the principles outlined in ED-79A/ARP4754A are followed.

This example contains references to documentation that a company may use to assure itself of the safety of its products but does not include the documentation that the Original Equipment Manufacturer (OEM) would be required to submit at the aircraft level for aircraft certification. Some of these documents are submitted to the regulatory agencies for the purpose of certification (e.g. the Wheel Brake System FHA). Other documents are internal to the company and not required to be submitted for certification. No implication is made that these documents should be submitted to a regulatory agency and none should be implied, although all documents should be available for submission if requested by the regulatory agency. Safety and Certification are not synonymous terms. The example shows the systems engineering process as applied to the development of an aircraft, including some processes that are beyond certification requirements.

Document History

ER-005
June 1, 2012
CONTIGUOUS AIRCRAFT/SYSTEM DEVELOPMENT PROCESS EXAMPLE
This ER provides a detailed example of the aircraft and systems development for a function of a hypothetical S18 aircraft. In order to present a clear picture, an aircraft function was broken down...

References

Advertisement