| | |

Philippines Cargo Crash

Similar Posts

  • | |

    Kit Crash In Brazil Kills Pilot

    brazilkitplane
    An Aero Designs Super Pulsar 100 kit plane with only the pilot aboard was flying over Amercana São Paulo, Brazil when it crashed on farmland bordering between Americana and Nova Odessa. The impact was close to Americana Municipal Airport where the pilot had just taken off from, en route to Guaratinguetá, São Paulo. The pilot was businessman Claito Finger, who died on impact. The kit plane crash will be investigated by the police. The pilot’s remains were taken to Instituto Médico Legal.

    Finger owned Finger Jewelry stores.

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

    Ultralight Plane Crash at Lowell Airport Kills a Man

    UltralightAn ultralight plane offered for sale crashed during its test flight at Lowell Airport, Vergennes Township, near Lowell, Michigan, at about 11:30 a.m. on August 24.

    Kent County sheriff’s Sgt. Russ Larson confirmed that a New Mexico man who was taking the test flight in the aircraft owned by a local resident, was killed in the crash. He was identified as Bryan Bowker, 67, of Edgewood.

    Authorities said that the plane successfully took off and landed once but crashed during a second take off attempt. Jeff Ostrander, who runs a flight school at Lowell Airport, said, “He had been doing some practicing with the aircraft, taxing up and down the runway to become familiar with the ground handling characteristics…I think what probably happened is a narrow dynamic stall where in the wing is held at such angle to the wind that no longer provides normal lift and airplanes do not fly in that condition.”

    The FAA is investigating the crash.

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

    The BEA releases the “Final report” on Air France Flight 447


    The BEA report (pp 200-201) concluded:

    • The crew possessed the licenses and ratings required to undertake the flight.
    • The aeroplane possessed a valid Certificate of Airworthiness, and had been
      maintained in accordance with the regulations.
    • The aeroplane’s weight and balance were within operational limits.
    • The aeroplane had taken off from Rio de Janeiro without any known technical
      problems, except on one of the three radio management panels.
    • The composition of the crew was in accordance with the operator’s procedures.
    • The meteorological situation was not exceptional for the month of June in the
      inter-tropical convergence zone.
    • There were powerful cumulonimbus clusters on the route of AF 447. Some of
      them could have been the centre of some notable turbulence.
    • An additional meteorological analysis showed the presence of strong
      condensation towards AF 447’s flight level, probably associated with convection
      phenomena.
    • The precise composition of the cloud masses above 30,000 feet is little known,
      in particular with regard to the super-cooled water/ice crystal divide, especially
      with regard to the size of the latter.
    • Several aeroplanes that were flying before and after AF 447, at about the same
      altitude, altered their routes in order to avoid cloud masses.
    • The crew had identified some returns on the weather radar and made a heading
      change of 12° to the left of their route.
    • At the time of the autopilot disconnection, the Captain was taking a rest.
    • The departure of the Captain was done without leaving any specific instructions
      for crossing the ITCZ.
    • There was an implicit designation of a pilot as relief Captain.
    • There was an inconsistency between the speeds measured, likely following the
      blockage of the Pitot probes by ice crystals.
    • The AP then the A/THR disconnected while the aeroplane was flying at the upper
      limit of a slightly turbulent cloud layer.
    • The aeroplane systems detected an inconsistency in the measured airspeeds. The
      flight control law was reconfigured to alternate 2B.
    • No failure message on the ECAM clearly indicates the detection by the system of
      an inconsistency in measured airspeeds.
    • The pilots detected an anomaly through the autopilot disconnection warning
      that surprised them.
    • The engines functioned normally and always responded to the crew’s inputs.
    • The PNF called out imprecise flight path corrections. They were however essential
      and sufficient for short-term management of the situation.
    • The last recorded values were a pitch attitude of 16.2 degrees nose-up, roll of
      5.3#degrees to the left and a vertical speed of -10,912 ft/min.
    • The Pitot probes installed on F-GZCP met requirements that were stricter than
      the certification standards.
    • Analysis of the events related to the loss of airspeed indications had led Airbus
      and Air France to replace C16195AA Pitot probes by the C16195BA model. The
      first aeroplane had been modified on 30 May#2009.
    • EASA had analyzed Pitot probe icing events; it had confirmed the severity of the
      failure and had decided not to make the probe change mandatory.
    • The flight was not transferred between the Brazilian and Senegalese control
      centres.
    • Between 8 h 22 and 9 h 09, the first emergency alert messages were sent by the
      Madrid and Brest control centres.
    • The crew was not able to use the ADS-C and CPDLC functions with DAKAR Oceanic.
      If the connection had been established, the loss of altitude would have generated
      an alert on the controller’s screen.
    • The first floating aeroplane parts were found 5 days after the accident.
    • The flight recorders were recovered 23 months after the accident.

    The accident occurred after the following events:

    1. Temporary inconsistency between the airspeed measurements, likely following
      the obstruction of the Pitot probes by ice crystals that, in particular, caused the
      autopilot disconnection and the reconfiguration to alternate law;
    2. Inappropriate control inputs that destabilized the flight path;
    3. The lack of any link by the crew between the loss of indicated speeds called out
      and the appropriate procedure;
    4. The late identification by the PNF of the deviation from the flight path and the
      insufficient correction applied by the PF;
    5. The crew not identifying the approach to stall, their lack of immediate response
      and the exit from the flight envelope;
    6. The crew’s failure to diagnose the stall situation and consequently a lack of inputs
      that would have made it possible to recover from it.

    Download the complete final report here:

    BEA FINAL REPORT on AF 447

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

    Valencia County Crash

    What: home built plane en route to Los Chavez
    Where: Mid-Valley airport in Los Chavez, Valencia County
    When: Oct 17, 2010 7: 58 am
    Who: pilot and passenger
    Why: The plane was on approach to Los Chavez when it crashed into a drainage ditch. The occupants survived but had to be extracted from the wreckage.

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

    Cebu Pacific’s ATR Emergency Landing in Philippines


    What: Cebu Pacific Flight 5J 893 ATR-72-500 propeller-plane, bound for Caticlan, Aklan
    Where: NAIA 1’s Runway 06 Ninoy Aquino International Airport in Manila
    When: 7:21 am Wednesday morning
    Who: 53 passengers and four crew w
    Why: the pilot reported a problem in the right engine. Alarm lights in the instrument panel were blinking. The carrier provided flight vouchers for Caticlan via Kalibo. The passengers were bound for Caticlan, gateway airport of the country’s most popular tourist destination Boracay island. The carrier stated officially that “The engine of the 11-month-old ATR 72-500 aircraft will be checked by an international maintenance crew from Cebu Pacific”

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

    Yakutia Boeing Skids off slick Runway

    What: Yakutia Boeing 737-86-N en route from Rimini Italy to Rostov Russia
    Where: Rostov Airport
    When: Dec 1, 2012
    Who: 120 aboard
    Why: The Yakutia flight was landing at Rostov Airport and skid off the runway when the pilot applied brakes.

    Passengers disembarked safely with no injuries.

    It took half an hour to tow the plane the ten yards back to the runway with a 20 ton truck.

    No injuries were reported. Passengers exited the plane via “ladder.” (Possibly a mistranslation!) The plane stopped on soft ground off the runway while it was raining.

    Video

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