Egyptair MS804: significance of ACARS messages clarified

Airbus is not, at present, able to give specific advice to A320 operators based on information available from the Egyptair MS804 investigation, according to a report by Flightglobal senior journalist David Kaminski-Morrow.

Data transmitted by the aircraft’s ACARS messaging unit to the Egyptair operations centre is insufficient to point to a cause, he reports, explaining: “Airbus has already informed operators, via two accident information bulletins, that the available data is limited and that the analysis of the transmissions does not contain enough data to determine the accident sequence, Flightglobal has established.”

The Flightglobal report continues: “With the inquiry unable to conclude whether a technical flaw contributed to the crash, the airframer has been unable to provide any immediate advisory to operators.

“Although seven ACARS maintenance messages transmitted in the space of 3min – between 02:26 and 02:29 Egyptian time – hint at the possibility of smoke and heat in the forward fuselage, there is no confirmation that the time-stamp of the messages correlates with the order of the trigger event and no clear indication of the precise time interval between them.”

The unknown factor is the “trigger event” referred to. The ACARS messages (see earlier blog entries) and the circumstances of the crew’s loss of control over the aircraft do not provide specific evidence to indicate either sabotage or a fault as the trigger event.  But whichever it was, it appears to have generated fire that caused progressive electrical failures, and the crew’s loss of control over the aircraft ensued soon after that.

Floating wreckage and body parts recovered from the water where the aircraft crashed into the Mediterranean Sea north of Alexandria, Egypt, so far provide no clue as to whether sabotage or another cause brought the aircraft down. And the search coordinators have released no information about how widely the wreckage field is spread. This can be an indicator of whether the aircraft came down in one piece or had broken up in the sky, but after time the clues can be lost because the floating wreckage can be spread by sea currents and wind.

All this makes the recovery of the main wreckage and the flight data and cockpit voice recorders from the sea bed vital for the understanding of what caused the loss.

 

MS804; did the crew report smoke to Egyptian ATC?

French television news channel M6 reports that Egyptian air traffic control sources have told them the crew of Egyptair flight MS804 radioed to Cairo control that there was smoke in the aircraft and that the crew intended to make a rapid descent.

There was indeed a rapid descent, but one over which the crew lost control for reasons that are still being investigated (see previous blog entry).

If the M6 report is confirmed as accurate, this would contradict official statements by the Egyptian authorities that there had been no emergency call or reports to ATC of trouble in the aircraft.

All communications about this tragic event are sensitive because the friends and relatives of the passengers and crew, despite their distress, are hungry for information about what happened to cause their death.

So if the Egyptian authorities were indeed withholding simple but established facts about the flight, such a policy of silence needs to be reviewed.

It’s already known that Egyptair held ACARS data (see previous blog entry) about MS804’s technical troubles just before the aircraft was lost, and the authorities did not release these facts, although they were leaked two days after the accident and confirmed by the French accident investigator BEA as accurate.

In contrast, following the loss of Air France flight 447 over the South Atlantic in 2009, Air France and the investigator BEA quickly released information from ACARS about an airspeed-reading anomaly that occurred at the beginning of the sequence of events that led to the loss of the aircraft, although it was not known until much later what part that anomaly played in the crash.

About 30 years ago there was a universal policy by air accident investigators all over the world to tell the press and people that they should wait for the final report, and no facts would be released until then, because they might be understood out of context.

But for the last 15 years or so it has become practice in most advanced economies to release significant facts when they have been established, even if the full context is not yet clear, and to release interim reports when a basic picture of the situation – or a part of it – becomes known. Usually interim reports are issued with caveats about what is not yet known or understood.

The latter policy treats the friends and relatives of accident casualties with respect, and credits the general public with enough intelligence to interpret incomplete but factual information as what it is – incomplete information.

Not only has policy about the release of information changed in these countries, but the communications environment has been transformed by the internet, 24h news coverage, and social media.

That change in communications has radically altered people’s expectations about being able to access information quickly. So if – during investigation of an issue of public interest – it becomes clear that the authorities have been withholding information, or simply not processing it efficiently because of bad internal communication systems, it tends to engender a failure of public trust in those authorities.

It is far better for the authorities themselves, let alone for those whom they serve, to release established facts officially as soon as possible rather than to see them – inevitably in today’s communications environment – leak out unofficially.

MS804: smoke in avionics bay, then flight control computers begin to fail

Egyptair operations centre plane screenshot

 

This is a screenshot of ACARS messages automatically datalinked from Egyptair flight MS804 to the airline’s operations headquarters shortly before the aircraft appeared – on radar – to go out of control.

News of the ACARS datalinked message first appeared in the Aviation Herald, a respected Salzburg, Austria-based journal that publishes on aviation safety issues. The French accident investigator BEA, which is helping Egypt with the inquiry, has confirmed the existence of the information. (ACARS = Aircraft Communications Addressing and Reporting System).

The printout/screenshot shows that all was more-or-less well in the aircraft until smoke was recorded in the forward lavatory just behind the flight deck.

A minute later smoke was recorded in the avionics bay, which is below the flightdeck floor, therefore close to the forward lavatory. The avionics bay contains all the electronic sensors and computers that provide the pilots with the information they need, and connections to the computers that direct the flight controls.

Two minutes after the smoke warning for the avionics bay the FCU 2 (second flight control unit) recorded a fault, and the SEC 3 (the N0 3 spoiler/elevator computer) also recorded a fault.

According to the Aviation Herald’s source, the ACARS feed then stopped.

Warnings about all these would have appeared on the pilots’ instrument panel.

There were other symptoms in the ACARS messages that popped up before the smoke was sensed by the system. These related to cockpit window de-icing and related window sensors, and were nothing to do with the aircraft controls but may have been yet another symptom of early fire damage to electrical systems.

The question now is whether the fire that caused the smoke was the result of an electrical fault – for example a short-circuit caused by damaged wiring – or whether some form of explosive or incendiary device was used – for example by a terrorist – to generate a fire or other damage.

The fire appears to have propagated fast. Flight control computers were failing within two minutes of the avionics bay smoke warning. If more of them failed subsequently the pilots would have limited means for controlling the aircraft, and with fire present, crew stress would have been extremely high.

That might explain the fact that there was no distress call. The pilots were trying to understand what the cause of the fire warnings was, where the source of the fire was located, whether they could do anything to stop it, and coping with a gradual degradation of their ability to control the aircraft.

These facts, providing they are not some kind of macabre coincidence, may have provided the basic reason why the aircraft went out of control and crashed.

But it is still not clear whether this situation was the result of terrorist action or an aircraft fault. Certainly no terrorist group has claimed responsibility.

And that answer is unlikely to be forthcoming soon. Even the recovery of the cockpit voice recorder and flight data recorded may not provide absolute proof of terrorist action – or lack of it – although the data will probably provide compelling circumstantial evidence.

 

 

Missing Egyptair flight MS804

It’s tempting to speculate that the loss of Egyptair MS804, an A320, was caused by sabotage because that’s what happened to the Metrojet flight out of Sharm el-Sheikh last year.

But, in the last decade, several aircraft have quietly gone missing during cruising flight without being brought down by explosives or in-flight break-up. The most obvious example was an Air France A330 that went missing in the south Atlantic in 2009, but there are others. And there is no information yet which would rule in or rule out either of those scenarios.

Greece’s Defence Minister Panos Kammenos has told a news conference that soon after entering Egyptian airspace, the A320 had turned “90 degrees left and 360 degrees to the right” before descending and disappearing off radar at 15,000ft. If that information is confirmed – and I have no reason to doubt it – the flight had clearly been destabilised, but the cause of the destabilisation is not known.

The aircraft’s last known position is over the Mediterranean south-east of Crete and south-west of Cyprus, but still more than 100nm off Egypt’s northern coast. Fairly soon some useful information is likely to become available because several military units – ships and aircraft – have been committed to a search of the area.

If, for example, there is a floating wreckage field and it is very widely dispersed, it will suggest an in-flight break-up.

But breakup can happen for reasons other than an explosion – although history and modern experience says that’s highly unlikely.

The aircraft and its “black box” recorders are almost certain to be found because, after other aircraft losses in the sea, recorders have been recovered in working condition from deeper waters than this.

 

MH370 search: winter may make it un-viable

The Australian Transport Safety Board reports that the search for the missing Malaysia Airlines flight MH370 is increasingly likely to be compromised by bad weather as the southern hemisphere winter advances.

The latest ATSB report says: “Poor weather conditions prompted the crew of Fugro Discovery to recover the deep-tow vehicle and go to weather avoidance on 8 May. The vessel is expected to depart for Fremantle later today.

Fugro Equator departed Fremantle for the search area on 6 May but poor weather has slowed transit to the search area. The vessel is anticipated to arrive on 11 May but weather conditions in the coming days are expected to preclude search operations.

Dong Hai Jiu 101 completed testing of the SLH‑ProSAS‑60 deep tow system and departed for the search area on 10 May.”

The sea conditions report speaks of 12m high waves and 50kt winds, but the Board says searches will resume whenever the weather permits.

This does not sound promising because the search is nearing its end, as the ATSB explains: “It is anticipated this will be completed around the middle of the year. In the absence of credible new information that leads to the identification of a specific location of the aircraft, Governments have agreed that there will be no further expansion of the search area.”

But if they do find the wreckage within the remaining search area, Malaysia, China and Australia are committed to recovering it all.

Past and future merge at Farnborough’16

The Farnborough International Airshow 2014 Farnborough Air show- 2014. Photo By Phil Weymouth- Streetlight. Bahrain. philweymouth@me.com
Farnborough aerodrome and show site

In July the Farnborough International Air Show will reflect an accelerating world aerospace industry while celebrating and drawing inspiration from its roots.

At the 11-17 July Show one of the world’s great aerospace companies – Boeing – while flying its latest products in the display will also celebrate 100 years of building commercial and military aeroplanes. The company is proudly fielding a Centennial Pavilion to parade its achievement milestones.

BOAC Boeing 707
Boeing’s classic 707 in BOAC livery. The jet airliner that, in the 1950s and ’60s, set the standards for the future

Meanwhile Farnborough International (FI) has just previewed a major development of its historic airfield site.

The company reveals that, in time for the 2018 Show, it will open a new purpose-built, permanent exhibition and conference centre less than 100m from the point where pioneer Samuel Cody took to the air in his British Army Aeroplane No 1 in October 1908, the UK’s first heavier-than-air flight.

Little more than a decade ago Farnborough aerodrome still looked, in some respects, as it did in the 1920s. Now, although most of the historic hangars and structures – like the wind-tunnel – have been preserved, they are dominated by 21st century glass and steel architecture as high-tech enterprises move in, and TAG Aviation’s elegant control tower and hangar/terminal complex define the airport horizon. Even the exhibition halls and chalet lines familiar to Show regulars are increasingly constructed to be permanent.

3 entrance view exterior_LR_AB
Farnborough International’s state of the art conference and exhibition centre to open in 2018

FI commercial director Amanda Stainer confirms chalets and exhibition stands will be sold out for the 2016 show. She says 67% of exhibitors will be international, 33% British, and the event will see its biggest ever participation by China, among 22 countries that have set up national pavilions.

FI has enhanced special reception facilities for delegations, and the proven “meet the buyer” enabling programme for small and medium enterprises will again be active.

Also repeated at Farnborough this year is the Innovation Zone, a showcase for gestating ideas looking for backers and buyers.

And Friday is designated Futures Day, intended to concentrate on the young generation, inspiring them to choose studies that will take them into the exciting world of aerospace engineering, design and operations.

Then as usual, on the final weekend, the public days are a time-honoured acknowledgement of the importance to the industry of generating public enthusiasm for all things aviation.

The air display detail has not yet been finalised, but there will be 3h 30min of it each day, ranging from the Lockheed Martin F35A and F35B Lightnings on their UK show debut to another unusual debutante, Hybrid Air Vehicles’ Airlander, a highly manoeuvrable airship that also generates aerodynamic lift.

The weekend display will show 50 aeroplane types, also including the Red Arrows, the Battle of Britain Memorial Flight, a P51 Mustang, Catalina amphibian, plus energetic manoeuvring from a Pitts Special and other crowd-pleasers.

Farnborough also presents the UK Drone Show for the first time this year, demonstrating drone racing for sport, providing participative drone piloting simulation, and aiming generally to raise drone safety awareness. The slogan pushing drone safety says it all: “Don’t fly a toy, be a Drone Pilot”.

The romance of aviation is clearest when the brilliance of today’s aviation engineering is seen in its historic context, and to that end the RAF Museum will man a stand at the Show this year, heralding the RAF’s centenary to be celebrated at Farnborough 2018.

Meanwhile the historic aerodrome site’s own extensive legacy is guarded by the Farnborough Air Sciences Trust, founded to “make available to the public the story of Farnborough’s unique aviation history and the air science that it spawned.”

 

 

Crisis of confidence follows Norway helicopter disaster

Video footage from the fatal 29 April Norway helicopter disaster horrified the millions who saw it on television news.

The main rotor blades were filmed spinning slowly to earth like a sycamore seed while, unseen by the camera, the flightless body of the machine had plunged to impact on an island just offshore from Bergen.

The two-pilot crew and all 11 passengers – North Sea oil industry workers – died in the aircraft. It was operated by CHC Helikopter Services. Very quickly all the affected type – the Airbus Helicopters H225 Super Puma – in the Norwegian and British fleets were grounded.

This is a disaster not just for those who died and their relatives, but also for manufacturer Airbus Helicopters because, on 1 April 2009, a Bond Offshore Helicopters Super Puma also suffered main rotor separation offshore from Peterhead on Scotland’s east coast.

In that case the aircraft hull plunged into the sea killing all 16 people on board. There was no video of the accident, but ultimately the investigation determined it was caused by the catastrophic failure of a main gearbox component – the epicyclic reduction gear. The disaster aircraft in 2009 was an AS332L, a lighter four-bladed variant of the heavy-lift five-bladed H225, but the cause of the Norway crash – still unknown – already looks as if it may be very different from the Scottish case.

Perceptions of Super Puma safety were not helped when, in 2012, two UK sector EC225s (the earlier designation of the H225) were forced to ditch in the North Sea because of main gearbox loss of oil pressure. The ditchings were successful, and the component failure that caused the problem in both cases has since been fixed, but the events exacerbated the crisis of confidence over the Super Puma fleet, especially among the oil workers who depended on them for transport to and from the rigs.

A press conference given by the Norwegian Air Accident Investigation Branch on 3 May has now confirmed that the accident was the result of a “technical” cause, not some kind of crew error, and that the time between a fault indication and rotor detachment was less than one second. Data from the cockpit voice and flight data recorder is complete, says the investigator, but the nature of the mechanical failure is still being investigated and a further statement will be released when they have more information.

Meanwhile EASA has issued an airworthiness directive requiring H225 operators to check the correct installation of the main gearbox suspension bars, examine chip detectors and oil filters for metallic particles, and to download data from the vibration health monitoring system to check for exceedences. The agency describes the measures as “interim”, but the breadth of the instructions suggests a precise cause is not yet known. On 3 May Airbus put out a bulletin to operators telling them to check the main gearbox suspension bars.

In Norway, oil industry workers are being quoted in the press as saying they will not fly in H225s when they are cleared to fly again. This will make life difficult because the type is the main heavy-lift helicopter used for transporting industry workers’ between the shore and the rigs.

The accident is a huge story in the Norwegian media. Norway is not a populous country, and North Sea oil is an important industry there. Among the oil rig commuters, few of whom have much technical knowledge of helicopters and their operation, the issue is being talked about almost with superstition – a phenomenon that replicates the reaction of UK oil rig commuters a few years ago. For example, newspapers are quoting a fact that may not be causal in either of the main-rotor-loss accidents, and is probably just a coincidence, but they quote it none the less: in the case of the 2009 UK accident the aircraft underwent a rotor change on 1 March and the crash happened on 1 April, and in the case of the recent Norwegian accident the aircraft had a rotor change on 27 March and the crash occurred on 29 April.

An additional concern being aired by Norwegian oil rig commuters is the effect of increasing pressure on costs because of the global slump in oil prices. They express a worry that pressure from Statoil for rapid aircraft turnarounds reduces time for pilots and technicians to carry out checks, although they have no means of linking this factor to the accident.

Since the 2009 crash a great deal has been done to learn about – and rectify – the technical causes of that accident and of the 2012 ditchings. Also the UK Civil Aviation Authority has carried out a searching safety review of oil-support helicopter operations in the UK sector of the North Sea.

The Norwegians had gone through a similar soul-searching review after an accident in the late 1990s, but since then – until this disaster – they had enjoyed a long period of exemplary offshore helicopter safety while British operators struggled with a series of accidents and serious incidents, the most recent being a Super Puma fatal crash on approach to Sumburgh in August 2013. The latter, according to the final report, was the result of a crew flight monitoring problem, not a technical fault.

Now the extended safe period for Norwegian oil support operations has come to an abrupt end, and a nightmare has returned for Airbus Helicopters. Rapidly finding – and fixing – the cause for this accident is crucial to confidence in the Super Puma fleet. The H225 is still in production, as is the latest version of the AS332, new-build versions of which are now designated H215.

To put it all in proportion, the Puma series has been in production since 1968, originally designed and built by Sud Aviation. The Super Puma designation arrived in 1978, and it has been through a series of changes in manufacturer branding: Aerospatiale, Eurocopter, and now Airbus Helicopters. The series has had a long and distinguished service with the military all over the world as well as operating extensively in civil transport and utility roles. As Airbus Helicopters has pointed out to the restless Norwegian media, Super Pumas have racked up 4.3 million flight hours in the air.

But all this is cold comfort to nervous oil rig commuters while they await news of the accident cause, worried about a subsequent decision by the authorities to authorise the type’s return to service in Norway and UK.

 

 

 

 

 

Fear of drones

It looks as if the 17 April “drone strike” on a British Airways aircraft on approach to Heathrow airport may not have been a collision with a drone after all. Maybe just a wind-tossed plastic bag – the investigation is still in progress.

In an aircraft travelling at about 150kt (170mph/275km/h) on final approach, small objects can suddenly appear and flash past. At that point the pilots are concentrating on monitoring the aircraft’s performance and aiming it at the runway. So it’s easy for a pilot to misidentify whatever the object is.

But does that mean we don’t need to worry about drones?

There some very simple rules about how you may operate a drone, so the relevant question is whether people will obey the rules – or even read them in the first place.

Drones are getting popular among ordinary people, mainly for airborne video recording or still photography. First the selfie, then the selfie-stick, now the airborne selfie?

Lads mags are full of enthusiastic advice for gadget-crazy young men. Some lads will be given a drone as a birthday present. If they are given one, will they read the operating instructions when they’ve opened the pack, let alone the legal restrictions on their use?

Some won’t, but does that mean they will inevitably operate their drone in such a way as to endanger aircraft? The law of averages says that one day someone will – possibly unintentionally – fly a drone in an airport approach or departure path.

But given another contemporary public threat to aircraft – commercially available hand-held laser pointers being shone into pilots’ eyes during take-off or final approach to land – an unsettling mentality exists out there. Use of lasers in this way is against the law, but incidents are on the increase.

So when a drone hits an aircraft, what will the result be?

Most are small and light – between one and 5kg. If one of these hits the aircraft wings, tail or forward fuselage it will cause damage but not make it impossible for the pilots to fly safely.

But if it hits the flightdeck windscreen or the engines the results could be serious. Exactly how serious we are not sure, because tests have not been carried out.

A drone-strike on an engine will probably cause its failure, and if it’s a heavier device it might smash the windscreen and injure or kill a pilot. Either of these events is very unlikely to be terminal for the aircraft, but they both could be. This would depend on the degree of direct damage and whether or not it has secondary effects.

Large-scale public drone use is still not with us, but it’s on the way. With greater use will come greater awareness among users as well as the public. That’s what the Civil Aviation Authority and Department for Transport are banking on – the public’s basic common sense.

Terrorists are unlikely to use drones against aircraft because there are more effective ways of attempting to disrupt commercial aviation.

But for those on the fringes of society – the kind who use powerful laser-pointers – dicing with risk can be attractive.

What the authorities have to decide is whether this risk is serious enough to require, for example, all drone users to register. Or some form of unique identifier like a transponder or GPS tracker to be fitted to all machines.

They’d rather not have to introduce expensive bureacracy to control the public use of devices that, used sensibly according to existing rules, are pretty much harmless.

 

More data from Flydubai crash

Russian investigator MAK has revealed that a nose-down push on the Boeing 737-800’s control  column coincided with a nose-down movement of its horizontal stabiliser as the aircraft transitioned from a go-around climb into a steep, high-speed dive to impact.

The aircraft, operating the 19 March scheduled flight FZ981 from Dubai to Rostov-on-Don, Russia, was smashed into tiny pieces by the impact, and there were no survivors among the 62 people on  board.

Earlier the MAK had stated there were no mechanical or systems failures revealed by the flight data recorder, but says it is still recovering components of the aircraft’s longitudinal control system to check there were no undetected anomalies.

The fatal approach to runway 22 took place at night in convective weather and windshear near the airport. MAK says a go-around was initiated at 220m altitude, and the nose-down yoke push and pitch-down motoring of the stabiliser occurred at 900m, while the cloudbase was recorded as 630m.

With each MAK data release, more similarities with the accident involving a Tatarstan Airlines 737-500 crash at Kazan in November 2013 are being revealed.

Flydubai accident update from MAK

Russian accident investigator MAK has released preliminary information from the flight data recorder suggesting that there was no mechanical or aircraft systems fault in the Flydubai Boeing 737-800 at the time it appeared to go out of control and crash on final approach to Rostov on Don (see details in blog entry for 20 March).

Also since the previous blog story was written, video imagery has been released indicating that the final trajectory of the aircraft to impact was a nose-down high speed dive, which matches closely the flight profile of a Tatarstan Airlines 737-500 before it crashed on approach to Kazan, Russia in November 2013 (see also 20 March story for details).

If the MAK confirms these details in a fuller release soon it will highlight a need for the industry to train crews better for all-engines go-around manoeuvres because of the potentially dangerous combination – especially at night or in IMC – of the strong pitch-up moment caused by go-around power from underslung engines, plus “somatogravic illusion” in the pilots. Somatogravic illusion is the feeling induced by rapid forward acceleration that the nose has pitched up when it has not.

Another factor in this lack of crew familiarity with all-engines-go-around risks is believed to be that the go-arounds most practiced during recurrent training involve an engine-out abandoned approach, in which the power, pitch-up moment, climb rate and airspeed acceleration are all much more gentle.

The Flight Safety Foundation has been alerting airlines to this risk for many years now, and some airlines have modified their recurrent training accordingly.

Pilot groups in Dubai are also alleging that crew fatigue may have played a part in this accident. If this is true, it will emerge in the MAK final report.