Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

(WARNING: content may disturb viewers) On This day: in 2005 Mandala Airlines Flight 091, a Boeing 737, crashes in Sumatra (Indonesia). Seconds after taking off from Polonia Int, Airport. The jet stalled and went down in a heavily populated area. 103 of 111 aboard are killed, along with another...

105,491 Aufrufe • vor 11 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

OTD in 2010: Air India Express Flight 812, a Boeing 737, crashes in Mangalore (India), 158 of 166 aboard die. On landing, the aircraft overran runway, fell down in a gorge and caught fire. Inquiry noted Captain actions in the unstabilized approach maneuver, despite multiple F/O and EGPWS warnings (More info below)⬇️ 🎥 Air Crash Animation (Youtube - go follow them there) From the accident enquiry (via ASN) "Direct Causes: The Court of Inquiry determines that the cause of this accident was Captain's failure to discontinue the 'unstabilised approach' and his persistence in continuing with the landing, despite three calls from the First Officer to 'go around' and a number of warnings from EGPWS. Contributing Factors to the Accident: 1. In spite of the availability of an adequate rest period prior to the flight, the Captain was in prolonged sleep during the flight, which could have led to sleep inertia. As a result of a relatively short period of time between his awakening and the approach, it possibly led to impaired judgment. This aspect might have got accentuated while flying in the Window of Circadian Low (WOCL). 2. In the absence of Mangalore Area Control Radar (MSSR), due to unserviceability, the aircraft was given descent at a shorter distance on DME as compared to the normal. However, the flight crew did not plan the descent profile properly, resulting in remaining high on approach. 3. Probably in view of ambiguity in various instructions empowering the 'copilot' to initiate a 'go around ', the First Officer gave repeated calls to this effect, but did not take over the controls to actually discontinue the ill-fated approach. "

Francisco Cunha

33,823 Aufrufe • vor 3 Monaten

Another ill-fated take-off over V1 (in this case, V2!) June 13 1996: Garuda Indonesia Flight 865, a DC-10, crashes in Fukuoka (Japan) 3 of 275 aboard die. On take-off, the jet had just left the ground when one of the engines failed. Crew opted to reject the maneuver; the aircraft was unable to stop safely and left the runway: landing gear collapsed, and the airplane caught fire. Inquiry noted pilot actions by aborting takeoff above V1, where SOP dictated pilots should have continued takeoff and deal with the engine later. More info below from Aviation Safety Network – Aftermath video is from Aircrashdaily (go give them a follow on YouTube) “The DC-10 accelerated for takeoff. The nose was raised, and at a speed of 158 kts, the first officer called "Rotate". It was 12:07:40. Three seconds later, at a radio altitude of 9 feet, a fan blade of the 1st stage HP turbine from the no. 3 engine separated. The N1 dropped to 23,7% within a few seconds. At 12:07:45, the flight engineer called "Engine failure number one." Takeoff was aborted at about the V2 speed, and the airplane contacted the runway one second later at a vertical acceleration force of 2.1 Gs. The thrust reversers were deployed and ground spoilers were extended. The DC-10 skidded off the runway through a ditch, fence and a road, before coming to a halt 620 m past the runway threshold. Investigation revealed that the turbine blade that failed, had operated for 30913 hours and 6182 cycles. General Electric had advised customers to discard blades after about 6000 cycles. Accident cause Although the Aircraft was well in excess of V1 and the aircraft had already lifted off from the runway, the takeoff was aborted. Consequently, the aircraft departed the end of the runway, came to rest and caught fire. It is estimated that contributing to the rejection of the takeoff under this circumstance was the fact that the CAP's judgement in the event of the engine failure was inadequate."

Francisco Cunha

157,331 Aufrufe • vor 3 Monaten

A preventable tragedy On This Day in 1967: Stockport air disaster (England). A British Midland C-4 [G-ALHG] crashes in Stockport, 72 of 84 aboard die. On a go-around, crew lost control after 2 engines failed. Investigation traced the issues to a known - but never addressed - design issue in the fuel system. More details here by ASN (video is from British Pathé) PROBABLE CAUSE: "The immediate cause of the accident was loss of power of both engines on the starboard side, resulting in control problems which prevented the pilot from maintaining height on the available power with one propeller windmilling. The loss of power of the first engine was due to fuel starvation due to inadvertent fuel transfer in flight. The loss of power of the second engine was due either to fuel starvation resulting from inadvertent fuel transfer in flight or to misidentification by the crew of which engine had failed followed by failure to restore power in time to the engine misidentified as having failed. Contributory causes of the accident were: (a) The design of the fuel valves and location in the cockpit of their actuating levers, so that a failure by the pilot correctly to position the lever by an amount so small as to be easy to do and difficult to recognize would result in inadvertent fuel transfer on a scale sufficient to involve the risk after a long flight of a tank expected to contain sufficient fuel being in fact empty. (b) Failure of those responsible for the design of the fuel system or the fuel valves to warn users that failure by a small amount to place the actuating levers in the proper position would result in inadvertent fuel transfer on a scale involving this risk after a long flight. (c) Failure of British Midland's air crew or engineers to recognize the possibility of inadvertent fuel transfer in the air from the evidence available in previous incidents in flight and contained in the fuel logs. (d) Failure of other operators of Argonauts who had learned by experience of the possibility of inadvertent fuel transfer in flight to inform the Air Registration Board, the Directorate of Flight Safety of the Board of Trade or its predecessors, or the United Kingdom Flight Safety Committee of the facts which they had learned so that these might be communicated to other operators of Argonauts and other aircraft equipped with similar systems and fuel cocks."

Francisco Cunha

24,189 Aufrufe • vor 3 Monaten

“Probable Cause: The pilot's operation of the airplane while intoxicated, which resulted in a loss of airplane control on landing” (and at the wrong airport) July 18 2019: a private Citation II crashes in Nevada (US), no casualties. Jet left the runway on landing at Mesquite, lost its undercarriage, and was destroyed in a fire. The aircraft was on a ferry flight, and it was not intended to land at Mesquite: the pilot was later arrested on suspicion of flying while drunk (later confirmed) (Below is an exact quote of the accident report: I can imagine that when this came out, the pilot was busy printing CVs) “After authorities arrived on site, the pilot was arrested for operating an aircraft under the influence of alcohol. The pilot was found to have a blood alcohol level of .288, which exceeded the FAA's allowable limit of .040. This likely contributed to the pilot landing at the incorrect airport and his subsequent loss of airplane control during landing” More info here, from the NTSB report "The flight departed Pasco-Tri-Cities Airport, Washington, at about 16:25 on a ferry flight to Las Vegas-Henderson Sky Harbor Airport, Nevada. While approaching Class B airspace, air traffic control noted the pilot’s slurred speech and repeatedly asked if the oxygen system was working. About 85 miles from the destination, the pilot reported having a nearby airport in sight and requested a visual approach several times, despite being instructed to continue southwest. The airplane soon dropped off radar, landed at the unintended airport instead, and touched down hard about halfway down the runway before sliding to a stop on the left side, with the fuselage and wings largely destroyed by post-impact fire".

Francisco Cunha

25,158 Aufrufe • vor 1 Monat