Zitat von »Flusirainer«

Nach dem Aufsetzen bewirkt der große Abstand des Hauptfahrwerkes zum Schwerpunkt genau das Gegenteil.Jetzt neigt der Bud dazu,abrupt nach unten zu fallen,was wiederum durch entsprechendes Ziehen am Höhenruder abgedämpft werden muss.

Zitat von »Flusirainer«

Wenn eine MD-11 viel zu hart aufsetzt,kann es passieren,das nicht nur das Fahrwerk,sondern auch der Hauptflügelholm ebenfalls bricht.Genauso wie es bei der FEDEX passierte und es wohl mit ihr bereits der vierte Unfall mit diesen fatalen Auswirkungen einer MD-11 war.

Zitat von »hasegawa«

Ganz einfach, das sie auch von einem durchschnittlichen Piloten ohne Macho-Allüren sicher geflogen werden kann.

Zitat von »BlackBox«

Peter: wollen wir mal anfangen ganz sinnfrei über Autopilot-Piloten, Busfahrer und MD-11 Crew sinnieren? Ich glaube, dass sollten wir lassen

Zitat von »Balu der Bär«

Zitat von »Flusirainer«

Wenn eine MD-11 viel zu hart aufsetzt,kann es passieren,das nicht nur das Fahrwerk,sondern auch der Hauptflügelholm ebenfalls bricht.Genauso wie es bei der FEDEX passierte und es wohl mit ihr bereits der vierte Unfall mit diesen fatalen Auswirkungen einer MD-11 war.

Dann kann man das im Endeffekt als Pilots Error auslegen, denn man kann ja einer hohen Sinkrate entgegenwirken. Der Absturz der FedEx in Subic Bay beispielsweise, da waren die Wetterbedingungen außerhalb der zugelassenen Limits....

Zitat

Ziata von Fogrunner:

Significant side loading caused damage to main gear which in turn caused a tire failure. There may be wing spar involvement, if so a sad end for 701.
I flew the aircraft for Gemini.

Zitat von »Flusianer«

[offtopic] Gibts diese Flugzeugpläne von jedem Muster? Wenn ja, wo findet man die? [/offtopic]

Zitat

Ein Feuer in der MD 11... doch, das hat etwas mit dem Flugzeug zu tun, zum Beispiel wie schnell sich das Feuer durch die Verkleidung arbeitet, weil diese nicht so hitzebeständig sind, wie man annahm... siehe Swissair MD 11... aber inzwischen hat man wohl bei diversen Maschinen dieses Typs anderes Material eingesetzt, als bei Auslieferung der ersten MD 11... So sind viele Probleme der Maschine im Lauf der Zeit abgestellt oder zumindest gemindert worden.

Zitat

Wenn man sich etwas näher mit den Geschichten befasst, stellt man doch fest, das eine ganze Reihe der Vorkomnisse komplett oder beitragend mit dem Flugzeug selbst zu tun haben.

Zitat

A statement by Lufthansa provided to Lufthansa employees on Lufthansa's internal website around Aug 10th said, that the black boxes have been analysed by the German Bureau for Aviation Accident Investigation (BFU). The results indicate, that the airplane touched down normally in the touch down zone, however two more ground contacts followed which caused the rear of the aircraft to fracture just aft of the main gear. After 2400 meters (7880 feet) the airplane departed the runway 33L to the left, at this stage the nose gear collapsed. The airplane came to rest after another 375 meters (1230 feet). The crew left the airplane via slide 1L. Further information can not be provided due to the ongoing investigation, every (internal or external) statement must be authorised by Saudi Arabia's investigator in charge. The investigator hopes to release a preliminary report in fall 2010, which requires interviews with the crew however. The interview has been scheduled for next week (Aug 16th-20th). A final report is expected in about a year. The wreckage has been removed from the accident site and is currently being dismantled. Lufthansa Technics checks whether some of the undamaged parts can be re-used, all the rest is going to be scraped in Saudi Arabia.

The German BFU stated, that the airplane bounced after first touch down and broke on next touch down.

Zitat

The German news magazine Spiegel reported on Aug 14th, that ground witnesses at Frankfurt Airport confirmed the cargo contained highly inflammable chemicals as well as other hazardeous goods like weaponry and other military goods. According to that report the chemicals were located exactly in the area where the fire started. Lufthansa Cargo did not comment on that report.

Zitat

Flugschreiber dokumentieren Landeunfall von Lufthansa Cargo
FRANKFURT - Nach dem Unfall einer MD-11F der Lufthansa Cargo am 27. Juli in Riad liegen den Ermittlern erste belastbare Erkenntnisse zum Ablauf der Landung vor. "Die Auswertung der Flugschreiber durch die Bundesstelle für Flugunfalluntersuchung (BFU) in Braunschweig ist erfolgt", erklärte ein Lufthansa Cargo-Sprecher am Mittwoch gegenüber aero.de. "Nach ersten Erkenntnissen kam es nach dem Anflug zu einem ersten normalen Aufsetzen."

Danach folgten zwei weitere Bodenberührungen. "Das Heck brach daraufhin direkt hinter dem Hauptfahrwerk ab", erläuterte Lufthansa Cargo die ausgewerteten Daten. "Die Landung erfolgte auf dem vorgesehenen Landebahnabschnitt. Nach ca. 2.400 Metern verließ das Flugzeug die Runway zur linken Seite. In der letzten Phase knickte das Bugrad ein. Nach weiteren 375 Metern kam das Flugzug im Sand zum Stillstand und fing Feuer."

Beide Piloten konnten sich über die fehlerfrei auslösende Rutsche 1L in Sicherheit bringen. Der 39 Jahre alte Kapitän der Maschine blieb unverletzt, sein 29-jähriger Erster Offizier musste im Krankenhaus behandelt werden. Die in den Unfall verwickelte MD-11F mit dem Kennzeichen D-ALCQ wurde vollständig zerstört und soll in Saudi Arabien abgewrackt werden.

Zitat

Germany's BFU reported in their July bulletin on Sep 17th, that the airplane touched down on runway 33L with a vertical acceleration of approximately 2G and lifted off again, two more touch downs with 3G and 4.3G occurred. The rear section of the aircraft broke just aft of the landing gear while the airplane was still on the runway, about 2400 meters after first touch down the airplane veered to the left, exited the runway and stopped after another 375 meters. The crew left the burning aircraft. (Editorial note: this report does not specify when the fire started and does not specify when exactly the rear section broke).

Zitat

Ein Airbuss soll auch nur 1,6g(oder weniger) aushalten.

Zitat von »mischi«

wer entscheidet ob es eine harte Landung war,oder nicht

Zitat

und ist die Überprüfung(der Maschine) von der Meldung des Piloten abhängig?

Zitat

Beschleunigungen dürfen zb A340 und B777 haben, bevor Inspektion wg Hard Landing fällig wird?

Zitat

wer entscheidet ob es eine harte Landung war,oder nicht

Zitat

von der Meldung des Piloten abhängig?

Zitat

Vielleicht etwas offtopic, aber wie sieht das eigentlich bei den noch größeren Maschinen aus? Werden die größenbedingt noch empfindlicher oder bleibt dieses Limit mehr oder weniger baureihenübergreifend gleich?

YouTube

Zitat

DCA04MA011

The Safety Board's full report is available at http://www.ntsb.gov/publictn/publictn.htm. The Aircraft Accident Report number is NTSB/AAR-05/01.

On December 18, 2003, about 1226 central standard time, Federal Express Corporation (FedEx) flight 647, a Boeing MD-10-10F (MD-10), N364FE, crashed while landing at Memphis International Airport (MEM), Memphis, Tennessee. The right main landing gear collapsed after touchdown on runway 36R, and the airplane veered off the right side of the runway. After the gear collapsed, a fire developed on the right side of the airplane. Of the two flight crewmembers and five nonrevenue FedEx pilots on board the airplane, the first officer and one nonrevenue pilot received minor injuries during the evacuation. The postcrash fire destroyed the airplane's right wing and portions of the right side of the fuselage. Flight 647 departed from Metropolitan Oakland International Airport (OAK), Oakland, California, about 0832 (0632 Pacific standard time) and was operating under the provisions of 14 Code of Federal Regulations (CFR) Part 121 on an instrument flight rules flight plan.

The first officer was the flying pilot for that leg.

The captain and first officer remained in Oakland on December 17, with no flight duties assigned, then reported for duty on December 18 before the accident flight's scheduled departure time of 0810 (0610 Pacific standard time). The airplane's departure to MEM was delayed until 0832 because of a package sorting issue that was later resolved. The first officer was the flying pilot, and the captain performed the nonflying pilot and line check airman duties......


.....The captain obtained the current MEM automatic terminal information service (ATIS) information and, about 1200:34, stated that the winds were out of "three twenty...sixteen gusts to twenty-two, so...it's more favorable to the three sixes." About 1202:08, the first officer stated, "I just think we should start putting out slats about twenty miles on the other side...because I'm...still fairly unfamiliar with Memphis, so I wanna get configured a bit earlier for that." The captain responded, "do what you want," and provided additional information about normal arrival operations, addressing typical stepdown and traffic pattern procedures, altitudes, airspeeds, and the probability of an early turn into MEM. The first officer acknowledged the information and requested the in-range checklist. About 1203:22, the captain stated, "you're driving and you stay focused on that and make me do whatever you need done." The first officer stated, "okay."

About 1204:46, the captain stated, "two ninety is the default descent speed. Which is just fine. That's what's in there." About 1205:22, the captain continued the in-range checklist, confirming altimeter settings with the first officer. About 1205:37, Memphis Air Route Traffic Control Center advised the pilots to contact MEM approach control. About 1206:00, the captain announced that the in-range checklist was complete, then contacted MEM approach control. The MEM approach controller advised the pilots to expect to land on runway 36L and informed them that ATIS information Zulu was current. The approach controller cleared flight 647 to descend to and maintain 8,000 feet mean sea level (msl). The captain acknowledged the clearance and repeated "three six left" to the first officer.

About 1209:12, the captain advised the first officer that the winds were out of "three twenty at sixteen gusts to twenty two. Ten miles [visibility]. It's still saying wind shear." The first officer responded, "goodness." About 1210:46, the captain stated, "I don't see any other TCAS [traffic alert and collision avoidance system] targets...We may be the lead dog coming in here." About 1211:24, the MEM approach controller instructed the pilots to reduce the airplane's airspeed to 210 knots and then descend to and maintain 6,000 feet. Shortly after the captain acknowledged these instructions, the first officer asked him to confirm the clearance, and the captain repeated the instructions. The first officer repeated the airspeed restriction and asked the captain to extend the slats.

About 1212:11, the captain stated, "there's BOWEN [a navigational intersection]...one seventy five is the heading out of BOWEN." The CVR recorded the first officer as she responded, "oh, thank you." About 1212:42, the captain stated, "FREAZ [a navigational intersection] is out there fourteen miles from touchdown." About 1213:14, the captain stated, "airport's right there," and the first officer responded, "yep."

About 1213:18, the MEM approach controller advised the pilots to contact MEM approach control on a different frequency. About 30 seconds later, the captain contacted MEM approach control on the new frequency and advised the controllers that flight 647 was level at 6,000 feet. About 1214:15, the first officer requested 15° of flaps. About 1214:33, MEM approach control cleared the pilots to descend to and maintain 5,000 feet and turn 10° right. Afterward, the MEM approach controller advised the pilots that they should expect to land on runway 36R instead of 36L, as previously instructed.

About 1215:39, the captain told the first officer, "three six right's in the fix page and it's in the...FMS [flight management system]," and the first officer thanked him. About 1216:11, the MEM approach controller instructed the pilots to reduce the airplane's airspeed to 190 knots, and the captain acknowledged this instruction. The first officer called for the approach checklist about 1218:10, and the captain responded, "approach check. Briefing's complete to three six right. The altimeter is three zero one zero." As the captain finished speaking, the MEM approach controller instructed the pilots to turn left to a heading of 020° and intercept the localizer for runway 36R. The captain acknowledged the instruction, and the pilots continued the approach checklist, completing it about 1218:58.

About 1219:00, the captain stated that the localizer was "alive" and that they were 18 miles from touchdown. About 10 seconds later, the MEM approach controller told the pilots to reduce the airplane's airspeed to 170 knots and cautioned them about possible wake turbulence from an Airbus airplane that was about 6 1/2 miles ahead of the flight 647 airplane. The captain acknowledged the speed reduction and stated that he was looking for the Airbus airplane. About 1219:24, the first officer stated, "flaps twenty two please," and the CVR then recorded the sound of two clicks. About 1219:28, the captain stated, "I got an Airbus right there...and another one out there looks...about level with us." About 20 seconds later, the MEM approach controller cleared flight 647 to descend to and maintain 2,000 feet. About 1220:20, the captain advised the first officer that they had intercepted the localizer, adding, "we're not yet cleared for the approach." The first officer responded, "that's noted."

About 1221:00, the pilots told the MEM approach controller that they saw the airport. The approach controller then stated, "FedEx six forty seven heavy cleared visual approach runway three six right, maintain a hundred and seventy knots until MAGEE [a navigational intersection] and you can contact tower now." The captain acknowledged the clearance and switched to the MEM air traffic control tower (ATCT) frequency. About 1221:53, the MEM local controller stated, "FedEx six forty seven heavy, Memphis tower, number two following a heavy Airbus two mile final caution wake turbulence runway three six right. Gain and loss of ten [knots] short final runway three six right, cleared to land."

About 1222:31, the captain stated, "how 'bout four extra knots. I don't like to add extra speed, but you know, three or four knots can make a lot of difference...if you're bumpin' around back and forth." The first officer responded, "good enough...let's go with ah landing gear down. Before landing checklist, please...glideslope's alive." The captain responded, "Spoilers are armed. The gear's down...and three green. Flaps are twenty two. Flaps to go." About 1223:38, the first officer requested 35° of flaps, and the captain acknowledged and complied with this request. About 1223:52, the CVR recorded a single central aural warning system (CAWS) "tailwind shear" alert. The captain stated, "okay, it's all right," and the first officer stated, "goodness."

About 1224:27, the CVR recorded the CAWS callout "one thousand" as the airplane descended through 1,000 feet above ground level (agl). The captain then stated, "visual. Stable. We got a nine thousand foot runway...and we land at a hundred and forty six. A pretty good headwind oughta work out okay." About 1224:52, the first officer stated, "autopilot's coming off." About 1225:02, the captain stated, "checklist is complete. You're cleared to land," and the first officer responded, "thanks." Between about 1225:08 and about 1225:52, the CVR recorded the CAWS altitude alerts for 500, 100, 50, 40, 30, 20, and 10 feet agl followed by the sounds of touchdown about 1225:53. About 1225:56, the first officer stated, "wow," and the CVR recorded the sound of increasing background noise, similar to increased engine rpm, and the sound of rumbling that was increasing in volume.

About 14 seconds after touchdown (about 1226:07), the FDR data showed a lateral load factor of about 1.0 G as the right wing suddenly moved about 6° lower. About the same time, the CAWS "landing gear" alert began to sound, which repeated until the end of the recording. About 1226:25, the captain stated, "here we go," and the airplane began to veer off the right side of the runway. As the airplane veered to the right and came to a stop, a fire developed on the right side of the airplane. About 1226:30, the airplane came to rest in the grass on the right side of the runway. The accident occurred during the hours of daylight. The CVR recording ended when the pilots shut down the engines (thus stopping electrical power to the CVR) about 1226:41.

FINDINGS

1) The captain and first officer were properly certificated and qualified in accordance with, and had received the training and rest time prescribed by, Federal regulations and company requirements. The flight crewmembers possessed valid and current medical certificates appropriate for Part 121 flight operations.

2) Based on the available evidence, fatigue was not a factor in this accident. Although the cockpit voice recorder recorded the first officer coughing and clearing her throat numerous times, she stated that she was not sick, and there is no evidence that this (the coughing/clearing her throat) adversely affected the flight or her performance.

3) The accident airplane was properly certificated and maintained and was equipped and dispatched in accordance with applicable regulations and industry practices. There was no evidence of any preexisting powerplant, system, or structural failure.

4) The accident airplane's cargo and its loading were not factors in the accident.

5) Differences between the MD-11 and MD-10 handling characteristics during the landing phase were not an issue in this accident.

6) Air traffic control was not a factor in the accident.

7) The atmospheric conditions encountered during the approach and landing were within the performance capabilities of the airplane; there was no evidence of significant windshear.

The first officer did not properly apply control wheel and rudder inputs to align the airplane with the runway centerline or apply appropriate back pressure on the control column to arrest the airplane's rate of descent before touchdown; as a result, the airplane touched down extremely hard while still in a crab.

9) The captain, who was conducting a line check of the first officer, did not adequately monitor the first officer's performance during the final stages of the approach and landing at Memphis and failed to take or initiate corrective action to prevent the accident.

10) The excessive vertical and lateral forces on the right main landing gear during the landing exceeded those that the gear was designed to withstand and resulted in the fracture of the outer cylinder and the collapse of the right main landing gear.

11) A proactive program, similar in concept to FedEx's Enhanced Oversight Program, in which flight crewmembers who have demonstrated performance deficiencies or experienced training failures are identified and given additional oversight and training, would be beneficial to flight safety.

12) The nonrevenue FedEx pilot who opened the L1 emergency exit mistakenly pulled both the manual inflation and slide/raft disengage handles because he was not sufficiently familiar with their operation, thus separating the slide/raft from the L1 doorsill.

13) The guidance contained in the flight crew emergency training section of Federal Aviation Administration Order 8400.10 (Air Transportation Aviation Inspector's Handbook) is not adequate for principal operations inspectors to use in ensuring that emergency exit door/slide training for flight crewmembers is as comprehensive as that which cabin crewmembers receive and is as comprehensive as intended by the regulation.

14) FedEx's inadequate hands-on emergency procedures training and the differences between the trainer and the door/slide installation on the accident airplane contributed to the unintentional release of the slide/raft.

15) Most of the FedEx pilots on board the accident airplane showed poor judgment and exposed themselves to unnecessary risk when they delayed their evacuation from a burning airplane to salvage personal items.

16) The Rural/Metro Fire Department aircraft rescue and firefighting (ARFF) response vehicles were unnecessarily delayed in providing ARFF assistance because the Memphis air traffic control tower ground controller did not give them priority over other nonemergency airport traffic; under other circumstances, this could have adversely affected ARFF efforts.

17) Air traffic control tower controllers should recognize the importance of relaying all available pertinent information, including airplane occupant information, to aircraft rescue and firefighting (ARFF) personnel to assist them in ARFF efforts and decision making.

18 ) The required recorded flight data recorder data on the MD-10 should meet the rate, range, and accuracy requirements specified in 14 Code of Federal Regulations Section 121.344, Appendix M.