DRS

Dek Regulatory System

Welcome to the World of Certification!

§25.721 General (See AMC 25.963(d))

CS-25 · Subpart D — Design And Construction · at CS25-28 (current)

Text in force at CS25-28: from CS25-3, effective 19 Sep 2007.

(a) The landing gear system must be designed so that when it fails due to overloads during take-off and landing, the failure mode is not likely to cause spillage of enough fuel to constitute a fire hazard. The overloads must be assumed to act in the upward and aft directions in combination with side loads acting inboard and outboard. In the absence of a more rational analysis, the side loads must be assumed to be up to 20% of the vertical load or 20% of the drag load, whichever is greater. (b) The aeroplane must be designed to avoid any rupture leading to the spillage of enough fuel to constitute a fire hazard as a result of a wheels-up landing on a paved runway, under the following minor crash landing conditions: (1) Impact at 1.52 m/s (5 fps) vertical velocity, with the aeroplane under control, at Maximum Design Landing Weight, (i) with the landing gear fully retracted and, as separate conditions, (ii) with any other combination of landing gear legs not extended. (2) Sliding on the ground, with - (i) the landing gear fully retracted and with up to a 20° yaw angle and, as separate conditions, (ii) any other combination of landing gear legs not extended and with 0° yaw angle. (c) For configurations where the engine nacelle is likely to come into contact with the ground, the engine pylon or engine mounting must be designed so that when it fails due to overloads (assuming the overloads to act predominantly in the upward direction and separately predominantly in the aft direction), the failure mode is not likely to cause the spillage of enough fuel to constitute a fire hazard.

ED Decision 2007/010/R · Source

Report an issue

Report an issue

Is something wrong with what you are looking at? Tell the maintainer; the report is filed against this page.

What kind of issue is it? (required)

Reports are posted publicly on GitHub with the address of this page. Please don't include personal information.