| | |

Helicopter Crashes into Residential Building in Orlando; 3 Killed

Similar Posts

  • | | | | | |

    BEA on SwiftAir Air Algeria (Burkina Faso to Algiers) Crash July 2014

    Accident 24 July 2014 in Gossi, Mali to the MD-83 registered EC-LTV operated by Swiftair S.A.

    Press release from the BEA and the Commission d’Enquêtes Accidents et Incidents de l’Aviation civile (Mali)

    Following the publication of the Interim Report on 20 September 2014 in Bamako (Mali), investigative work has continued, based on the analysis of the accident flight parameters. Progress made in this work has led the Republic of Mali Commission of Inquiry and the BEA to communicate jointly the following information.

    On 24 July 2014, the MD-83 registered EC-LTV was performing scheduled night flight AH 5017 from Ouagadougou (Burkina Faso) to Algiers (Algeria). Takeoff occurred at 01h15, the climb towards the cruise altitude took place without any significant events, and the crew made several heading changes in order to fly around a storm cell. The autopilot and the autothrottle were engaged. The aeroplane reached the cruise altitude of 31,000 ft, that’s to say about 9,500 m. The autopilot then switched to the mode that maintains the altitude and the autothrottle to the mode that maintains the speed (Mach).

    About two minutes after levelling off at an altitude of 31,000 ft, calculations performed by the manufacturer and validated by the investigation team indicate that the recorded EPR , the main parameter for engine power management, became erroneous on the right engine and then about 55 seconds later on the left engine. This was likely due to icing of the pressure sensors located on the engine nose cones. If the engine anti-ice protection system is activated, these pressure sensors are heated by hot air.

    Analysis of the available data indicates that the crew likely did not activate the system during climb and cruise.

    As a result of the icing of the pressure sensors, the erroneous information transmitted to the autothrottle meant that the latter limited the thrust delivered by the engines. Under these conditions, the thrust was insufficient to maintain cruise speed and the aeroplane slowed down. The autopilot then commanded an increase in the aeroplane’s pitch attitude in order to maintain the altitude in spite of this loss of speed.

    This explains how, from the beginning of the error in measuring the EPR values, the aeroplane’s speed dropped from 290 kt to 200 kt in about 5 minutes and 35 seconds and the angle of attack increased until the aeroplane stalled.

    About 20 seconds after the beginning of the aeroplane stall, the autopilot was disengaged. The aeroplane rolled suddenly to the left until it reached a bank angle of 140°, and a nose-down pitch
    of 80°

    The recorded parameters indicate that there were no stall recovery manœuvres by
    the crew.

    However, in the moments following the aeroplane stall, the flight control surfaces remained deflected nose-up and in a right roll.

    CORRECTIVE ACTIONS

    At least two similar events occurred, in June 2002 and in June 2014, with no serious consequences.

    The event in June 2002 was the subject of an NTSB investigation report. On 4 June 2002, the McDonnell Douglas MD-82, registered N823NK performing Spirit Airlines flight 970, suffered a loss of thrust on both engines, in cruise at an altitude of 33,000 ft, that is about 10,000 m. The two pressure sensors, located on the engine nose bullets, were blocked by ice crystals, leading to incorrect indications and over-estimation of the EPR. The crew noticed the drop in speed and the precursor indications of a stall just before disengagement of the autopilot and putting the aeroplane into a descent. They had not activated the engine anti-ice systems. This event occurred during the day, outside the clouds.

    On 8 June 2014, the MD83 registered EC-JUG belonging to Swiftair, which was performing a passenger transport flight at flight level FL 330, suffered a drop in speed while it was flying during the daytime above the cloud layer. The crew detected the problem, put the aeroplane into a descent and activated the engine anti-ice systems without reaching a stall situation, then continued the flight.

    This background, as well as the data on the accident to flight AH5017, was shared with the European Aviation Safety Agency (EASA) and through EASA with the American authorities (FAA); they should serve as the basis for future publication of corrective measures aimed at assisting crews in identifying and responding to similar situations to those encountered at the time of this accident.

    NEXT STEPS

    The investigative work is continuing, in particular on the analysis of:

    the flight parameters to complete the scenario described above,
    possible crew reactions, despite the absence of Cockpit Voice Recorder data from the accident flight, which remain unusable to this day,
    the training and follow-up of Swiftair crews,
    previous events and the follow-up undertaken.

    The publication of the final report is planned before the end of December 2015.

    Download Interim below:

    https://airflightdisaster.com/wp-content/uploads/2015/04/ec-v140724.e1.en_.pdf

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | | |

    Magnicharters Airlines Jet Crash-Landed at Mexico City Airport

    MagnichartersA Magnicharters airlines jet crash-landed at Mexico City International Airport in Mexico, on November 26.

    The Boeing 737 plane was coming from the Caribbean coast resort of Cancun when its landing gear partially collapsed upon landing.

    There were 139 passengers and 5 crew members aboard at the time; none of them were injured. Authorities said some of the passengers were treated for “nervous crisis.”

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | | |

    Propair Flight 420

    Propair Flight 420, chartered by General Electric to transport their workers to their facility in Lachine, Quebec and Peterborough, Ontario, took off from Dorval. The left brakes overheated during take-off leading to a fire in the left wing which ruptured pipelines. The crew made an emergency landing. All 11 passengers and crew on board were killed. As a result of this accident, an overheat warning system inside the wheel-wells of every Metroliner was required. The pilot was Captain Jean Provencher. The co-pilot was Walter Stricker.

    The official summary:

    The aircraft, a Fairchild-Swearingen Metro II (SA226-TC), registration C-GQAL, serial number TC 233, took off as Propair 420 from Dorval / Montréal International Airport, Quebec, around 0701 eastern daylight time bound for Peterborough Airport, Ontario. On board were nine passengers and two pilots. About 12 minutes after take-off, at an altitude of 12 500 feet above sea level (asl), the crew advised air traffic control (ATC) that they had a hydraulic problem and requested clearance to return to Dorval. ATC granted this request. Around 0719, at 8600 feet asl, the crew advised ATC that the left engine had been shut down because it was on fire. Around 0720, the crew decided to proceed to Mirabel / Montréal International Airport, Quebec. At 0723, the crew advised ATC that the engine fire was out. On final for Runway 24, the crew advised ATC that the left engine was again on fire. The landing gear was extended on short final, and when the aircraft was over the runway, the left wing broke upwards. The fuselage pivoted more than 90? to the left around the longitudinal axis of the aircraft and struck the ground. All 11 occupants were fatally injured.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | | | | |

    TAM Update

    What: TAM Linhas Aereas Airbus A320 Flight JJ3054
    Where: Sao Paulo Brazil Congonhas airport
    When: July 17, 2007
    Who: 199 fatalities
    Why: Sao Paulo Institute of Criminology 16-month investigation places blame on government agencies for failing to ensure runway safety. Government failure to set rainy-day landing rules for the short runway whose new surface had not yet been grooved to drain rainwater.

    NTSB Factual
    NTSB Identification: DCA07RA059
    Scheduled 14 CFR operation of TAM Linhas Aéreas
    Accident occurred Tuesday, July 17, 2007 in Sao Paulo, Brazil
    Aircraft: Airbus Industrie A320-233, registration: PR-MBK
    Injuries: 199 Fatal.
    On July 17, 2007, at 21:54 UTC, an Airbus A320-233, Brazilian registration PTMBK, serial number 789, operated by TAM Linhas Aéreas overran the end of runway 35 at the Sao Paulo Congonhas airport upon landing. The airplane was on a scheduled domestic flight from Porto Alegre, Brazil. The airplane departed the runway to the left side near the departure end and crossed over a road prior to impacting a cargo depot and gas station. The end of the runway is on elevated terrain approximately 80 meters above the surface of the road. The 6 crew members, 162 passengers, and 18 persons on the ground suffered fatal injuries. The aircraft was destroyed by impact forces and fire.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | | |

    Envoy Air Flight Makes Emergency Landing at DFW Airport

    Envoy Air flight MQ-3612 had to return and make an emergency landing at Dallas/Fort Worth International Airport, Texas, on December 8th.

    The plane took off for Wichita Falls, Texas, but had to turn back due to a problem with the anti-ice system.

    The plane landed back safely. All passengers and crew members remained unharmed.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | | | |

    Alaska Airlines Flight Diverts to Spokane due to Medical Emergency

    An Alaska Airlines flight made an emergency landing in Spokane, Washington, on September 21st.

    The plane heading from Chicago, Illinois, to Seattle, Washington, was diverted after a passenger suffered a medical emergency.

    The plane landed safely. The patient was rushed to a hospital.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.