Emergency Landing of Flybondi B738 at Argentina

Flybondi B738 at Buenos Aires faced an emergency due to "technical novelty"




A Flybondi Boeing 737-800, registration LV-KEF performing flight FO-5100 from Buenos Aires Ezeiza,BA to Iguazu,MI (Argentina), was climbing out of Ezeiza's runway 11 when the crew stopped the climb at FL060 reporting a hydraulic failure and entered a hold. In the meantime the airport stopped arrivals causing a number of aircraft to divert.



The aircraft subsequently returned to Ezeiza for a safe landing on runway 11 at a higher than normal speed (about 160 knots over ground) about 30 minutes after departure and vacated the runway.



Passengers reported the captain announced a "technical problem", they believe it was a problem with one of the engines (CFM56) possibly related to hydraulics.



The airline reported the aircraft returned safely due to technical novelty, a minor issue, possibly a false indication or minor failure. Argentina's JST announced they have opened an investigation into the occurrence.




Flight details are available here: https://www.flightaware.com/live/flight/FBZ5100


Comments

Post a Comment

Popular posts from this blog

Crippled Safair attempts a low approach after loosing wheel on takeoff

Image
Safair B737-800 dropped its wheel on departure  A Safair Boeing 737-800, registration ZS-FGE performing flight FA-212 from Johannesburg to Cape Town (South Africa), was departing from Johannesburg's runway 21R when the outboard left main wheel separated from the airframe.  The crew stopped the climb at about FL220, descended to FL150 and entered holds to burn off fuel.  The aircraft performed a low approach to runway 21R about 90 minutes after departure, entered another hold and landed safely on runway 21R about 40 minutes after the low approach and about 2:15 hours after departure. The lost wheel was recovered within the airport perimeter.
Read more

Engine! Engine!! Engine!!! Egypt Air had a taste of failure in-flight

Image
Egypt B738 at Alexandria experienced engine failure   An Egypt Air Boeing 737-800, registration SU-GCM performing positioning flight MS-4413 from Alexandria (Egypt) to Jeddah (Saudi Arabia), was climbing through FL170 out of Alexandria when the crew stopped the climb, initiated a descent and entered a hold due to an engine (CFM56) failure.  The aircraft subsequently returned to Alexandria for a safe landing about 50 minutes after departure. A replacement Boeing 737-800 registration SU-GED positioned from Cairo (Egypt) to Jeddah to pick up the 140 Umrah pilgrim waiting for their flight back home. The airline reported the occurrence aircraft suffered a technical malfunction. A replacement aircraft was dispatched from Cairo to pick up the 140 pilgrim waiting for their flight home. The occurrence aircraft was able to position to Cairo about 14 hours after landing back in Alexandria. Detailed flight information: https://www.flightaware.com/live/flight/MSR4413
Read more

Computer malfunction over the Atlantic

Image
Jetblue A321-200N over the Atlantic had a computer problem  A Jetblue Airbus A321-200N, registration N4048J performing flight B6-842 from Dublin (Ireland) to New York JFK,NY (USA), was enroute at FL340 over the Atlantic Ocean about 230nm westnorthwest of Shannon (Ireland) when the crew decided to return to Dublin.  The aircraft landed safely on Dublin's runway 28L about 110 minutes after departure. The airline reported the crew decided to return due to a problem with an onboard computer. The flight was cancelled, the passengers were rebooked onto other flights. Detailed flight information: https://flightaware.com/live/flight/JBU842/history/20240410/0955Z/EIDW/KJFK
Read more