| | | |

Air New Zealand Flight Returns to Auckland due to Hydraulic Fault

Similar Posts

  • | | | | |

    Air Canada Flight Returns to Frankfurt due to Hydraulic Failure

    Air Canada flight AC-877 had to return and make an emergency landing in Frankfurt, Germany, on May 15th.

    The Boeing 777-300 plane took off for Toronto, Canada, but had to turn back due to a hydraulic failure.

    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.
  • | | | |

    Melbourne Emergency Landing

    What: Virgin Blue Boeing 737 en route from Melbourne to Sydney
    Where: Melbourne
    When: Nov 19 2010 7:16 a.m.
    Who: 122 passengers, 6 crew
    Why: Just after takeoff, the pilot noted a peculiar odor described as burning plastic (originally reported as smoke in the cockpit.) After being aloft for less than 30 minutes, the plane was met by 11 fire trucks on the landing which was safe; and the plane seemed to be operating as usual. Passengers were provided alternate flights as maintenance checked over the plane for the source of the smell, which may have been the new engine.

    George’s Point of View

    An electrical fire? or Old Spice? Avon? Brut? Body odor? Old Spice ON body odor?

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

    Preliminary findings on ET 302 and Boeing Statement

    Preliminary findings on ET 302 crash:

    1. Aircraft’s airworthiness was certified;
    2. The crew were capable of flying& followed Boeing’s procedures;
    3. Take off appeared normal;
    4. Crew followed all procedures, but was unable to control the aircraft.

    The release of the actual preliminary report by Ethiopia’s Ministry of Transport is expected during Apr 4th or Apr 5th 2019.

    Boeing statement
    We at Boeing are sorry for the lives lost in the recent 737 MAX accidents. These tragedies continue to weigh heavily on our hearts and minds, and we extend our sympathies to the loved ones of the passengers and crew on board Lion Air Flight 610 and Ethiopian Airlines Flight 302. All of us feel the immense gravity of these events across our company and recognize the devastation of the families and friends of the loved ones who perished.

    The full details of what happened in the two accidents will be issued by the government authorities in the final reports, but, with the release of the preliminary report of the Ethiopian Airlines Flight 302 accident investigation, it’s apparent that in both flights the Maneuvering Characteristics Augmentation System, known as MCAS, activated in response to erroneous angle of attack information.

    The history of our industry shows most accidents are caused by a chain of events. This again is the case here, and we know we can break one of those chain links in these two accidents. As pilots have told us, erroneous activation of the MCAS function can add to what is already a high workload environment. It’s our responsibility to eliminate this risk. We own it and we know how to do it.

    From the days immediately following the Lion Air accident, we’ve had teams of our top engineers and technical experts working tirelessly in collaboration with the Federal Aviation Administration and our customers to finalize and implement a software update that will ensure accidents like that of Lion Air Flight 610 and Ethiopian Airlines Flight 302 never happen again.

    We’re taking a comprehensive, disciplined approach, and taking the time, to get the software update right. We’re nearing completion and anticipate its certification and implementation on the 737 MAX fleet worldwide in the weeks ahead. We regret the impact the grounding has had on our airline customers and their passengers.

    This update, along with the associated training and additional educational materials that pilots want in the wake of these accidents, will eliminate the possibility of unintended MCAS activation and prevent an MCAS-related accident from ever happening again.

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

    ASL Airlines Belgium Plane Returns to Belgium After Bird Strikes

    ASL Airlines Belgium freight flight 3V-811 had to return and make an emergency landing in Liege, Belgium, on November 24th.

    The Boeing 747-400 freighter plane took off for Jinan, China, but had to turn back after the engines ingested several birds.

    The plane landed back safely. Everyone aboard remained unharmed.

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

    KLM Cityhopper Flight Makes Emergency Landing in Amsterdam

    KLM Cityhopper flight KL-981 made an emergency landing in Amsterdam, Netherlands, on November 23rd.

    The Embraer ERJ-190 plane took off for London City Airport, England, but had to return after the crew noticed smell of smoke in the cabin.

    The plane landed back uneventfully. All passengers and crew members remained safe.

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

    Update: Ethiopian Crash Cockpit Voice Recorder Found/not found


    Click to view full size photo at Airliners.net
    Contact photographer Alastair T. Gardiner

    In an announcement hauntingly similar to the initial release of 7 survivors (who were later confirmed as 22 dead), the cockpit voice recorder was reportedly found…but later reported to be missing the memory unit.

    Ethiopia Airlines release is below and denies recovery of the CVR.
    ET Flight 409 Accident Update 9 – 10 February, 2010

    Ethiopian Airlines would like to express its position on the latest speculative reports released on the cause of the accident on ET-409, 25 January.

    As a member of the investigation team, Ethiopian Airlines strictly adheres to the ICAO annex 13 regulation, in which it is mandated to refrain from any inconclusive comments on the process of investigation.

    The investigation is still in its early stage and the CVR (Cockpit Voice Recorder) and the aircraft wreckage are not yet retrieved for analysis, it is therefore, too early to conclude the cause of the accident. Ethiopian Airlines does not rule out all possible causes including the possibility of sabotage until the final outcome of the investigation is known.

    Ethiopian Airlines would continue to cooperate with the investigation team to complete the process in accordance with the ICAO regulation and reveal the truth.

    We share the pain and sorrow of the families of our crew and dear passengers who have lost their lives in the accident.

    What: Ethiopian Airlines Boeing 737 en route from Beirut to Addis Ababa
    Where: 2 miles west of the coastal village of Na’ameh.
    When: Jan 25 2010
    Who: 7 crew 83 passengers
    Why: Shortly after taking off in stormy weather and heavy lightning, Lebanese ATC lost contact. The plane disappeared from radar 45 minutes after leaving Beirut. Witnesses on the coast saw the plane as it crashed into the sea. So far 9 bodies have been found by members of the Lebanese army

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