Both engines failed on forced-landing Ural A321: carrier
August 16, 2019
Both engines on a Ural Airlines Airbus A321 failed before the aircraft conducted a forced landing in a field outside Moscow.
The Russian carrier says the aircraft lost power in both engines following a severe bird-strike as it departed Moscow Zhukovsky for Simferopol early on 15 August. It came to rest in a field about 5km from the far end of Zhukovsky's runway 12. "Several people sought medical attention," it says, but states that there were no fatalities. A formal commission is being convened to probe the accident. Ural Airlines is crediting the "professionalism" and "co-ordinated actions" of the crew in safely bringing down and evacuating the aircraft. It says the captain, who has been with the operator since about 2013, had logged more than 3,000h while the first officer, employed by the carrier only last year, had some 600h. The aircraft has suffered "significant" damage, it adds. Five cabin crew were on board, the airline indicates. It puts the total number of passengers on board at 224. Federal air transport regulator Rosaviatsia says the aircraft struck a flock of gulls, and that the aircraft came down between inner and outer marker beacons for the airport's landing system. "The landing was carried out with the undercarriage retracted," it adds. "Before the landing, the crew shut down the engines." Slides were deployed from all eight exits of the A321.
Source: FlightGlobal
Undercarriage fire on 767 behind Shannon closure
August 16, 2019
Irish investigators have indicated that an undercarriage fire was behind the aborted take-off by a Boeing 767-300 at Shannon. The incident, involving an Omni Air International aircraft, occurred at about 06:15 and closed the main runway 06/24. Shannon tower transmissions reveal that a controller asked the crew whether the aircraft was emitting smoke. "Is that the brakes, is it?" he queried, referring to the left-hand undercarriage of the jet. The crew responded by stating that the aircraft was stopping on the runway, and requesting firefighting vehicles and a tug. Controllers subsequently added that a fire was starting on the left-hand main bogie, to which the crew replied that they would evacuate the aircraft from the right side. The radio communications were archived by LiveATC. Although the tower controller had originally expected only a few minutes' delay while the aircraft was towed off the runway, the airport operator subsequently kept the runway shut until the Irish Air Accident Investigation Unit permitted the jet's removal.
Source: FlightGlobal
An-26 undershot crew turned off ground-proximity alerts
August 15, 2019
Investigators in Cote d'Ivoire have concluded that an Antonov An-26 crew continued an approach below minima without making visual contact with the runway before the twin-engined aircraft crashed into the sea off Abidjan. Analysis of the accident indicates that the terrain-warning system had been silenced to avoid nuisance alarms. The approach was conducted "without adequate monitoring" of the aircraft's descent flightpath and, under standard operating procedures, the crew should have executed a go-around, says the inquiry into the 14 October 2017 crash. Three crew members and one of the seven passengers were killed in the accident involving the Moldovan-registered aircraft (ER-AVB), operated by cargo charter carrier Valan. It had been arriving at Abidjan following a service from Ouagadougou in Burkina Faso. The flight, operating under the identity 'Kondor 26', was being conducted on behalf of French armed forces. Although the crew briefed for an ILS approach to runway 21, this was subsequently changed to a VOR Z approach to runway 03, which requires flying in from the south over the sea. Investigators state that the crew discussed an absence of VOR signal on board, so the captain decided – without informing air traffic control – to use area navigation and GPS for the non-precision approach. The crew was given the weather conditions – reduced visibility and light rain – but the cockpit-voice recorder did not capture evidence of an announcement updating minima. Some 3min after the tower gave landing clearance to the crew, radar contact was lost. Wreckage was subsequently located offshore, the aircraft having crashed into the sea short of the threshold.
Source: FlightGlobal