Indonesia AirAsia Flight 8501

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Indonesia AirAsia Flight 8501
PK-AXC.jpg
The aircraft involved in the crash, registered as PK-AXC, eight months before the crash
Accident summary
Date 28 December 2014 (2014-12-28)
Summary Rudder travel limiter failure followed by inappropriate pilot response[1][2]
Site Karimata Strait, Java Sea (near Belitung and Borneo Islands, Indonesia)[3]
Lua error in package.lua at line 80: module 'strict' not found.[lower-alpha 1]
Passengers 155
Crew 7
Fatalities 162 (all)[4]
Survivors 0[4]
Aircraft type Airbus A320-216
Operator Indonesia AirAsia
Registration PK-AXC
Flight origin Juanda International Airport, Surabaya, Indonesia
Destination Singapore Changi Airport, Singapore

Indonesia AirAsia Flight 8501 (QZ8501/AWQ8501) was a scheduled international passenger flight, operated by AirAsia Group affiliate Indonesia AirAsia, from Surabaya, Indonesia, to Singapore. On 28 December 2014, the aircraft operating the route, an Airbus A320-216, registered as PK-AXC, msn: 3648,[5] crashed into the Java Sea during bad weather, killing all 155 passengers and seven crew on board.[6] Two days after the crash, debris from the aircraft and human remains were found floating in the Java Sea. Searchers located wreckage on the sea floor beginning on 3 January 2015, and the flight data recorder and cockpit voice recorder were recovered by 13 January. The search for bodies ended in March 2015 after recovery of 113 of the 162 bodies.[7]

On 20 January 2015, it was reported that the aircraft had stalled during an abnormally steep climb and had been unable to recover. On 1 December 2015, the Indonesian National Transportation Safety Committee released its report concluding[8] that the sequence of events leading to the crash started with a malfunction in the rudder travel limiter unit that eventually led to a 104-degree roll of the aircraft. The pilots' response, and apparent miscommunication between them, was a significant link in the chain of events that led to the loss of the aircraft.[8][9][10]

The air crash became the second-deadliest in Indonesian territory, behind Garuda Indonesia Flight 152 in 1997 and the only fatal crash of AirAsia's group. It was also the second deadliest plane crash involving an Airbus A320 and the third deadliest involving an Airbus A320 family. It was the third deadliest plane crash in 2014.

Sequence of events

Flight path and location of debris. Flight path (red) is limited to range of Flightradar24 coverage; it does not reflect ATC coverage.

Flight 8501 was a scheduled flight from Surabaya, Java, Indonesia to Singapore on Sunday, 28 December 2014. It was scheduled to depart Juanda International Airport at 05:20 Western Indonesian Time (WIB, UTC+7) and arrive at Singapore Changi Airport at 08:30 Singapore Standard Time (SST, UTC+8).[11] Flight 8501 took off at 05:35.[lower-alpha 2] Indonesia AirAsia did not have permission from the Indonesian Ministry of Transportation to operate the route on Sundays.[lower-alpha 3][14]

After departure, Flight 8501 was in contact with the Jakarta Area Control Centre (callsign: "Jakarta Centre"),[15] which provides air traffic control (ATC) service over the western Java Sea, and flying along air route M635,[15] when it approached a line of thunderstorms off the southwest coast of Borneo.[16] At 06:12, Flight 8501 was flying at flight level 320—approximately Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value).—when the cockpit requested and received permission to deviate left from its original flight path to avoid these storms.[17] The pilot then requested to climb to flight level 380,[18] which was deferred by ATC because of other aircraft in the vicinity.[15][19][20][21] AirNav Indonesia, which operates the Jakarta Area Control Centre, reported that Jakarta Centre then cleared Flight 8501 to flight level 340 at 06:14,[lower-alpha 4] but no response was received; other aircraft in the vicinity were asked to contact Flight 8501, but also did not receive a response.[15][22]

Between 06:17:00 and 06:17:54, the aircraft climbed from 32,000 to 37,000 ft (9,800 to 11,300 m),[23] exceeding a climb rate of 6,000 ft (1,800 m) per minute, about twice the maximum rate that a commercial aircraft should climb in still air.[24][25] A photo of a secondary radar screen, without a timestamp, showed the aircraft at flight level 363—approximately 36,300 ft (11,100 m)—and climbing with a ground speed of 353 knots (654 km/h; 406 mph), which is too slow to maintain stable level flight in still air.[21][26] The Indonesian Minister of Transport interpreted the apparent aircraft behaviour at peak altitude as an aerodynamic stall, when it began to descend at 06:17:54, descending Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). within six seconds and Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). within 31 seconds.[23] The aircraft also began a turn to the left, forming at least one complete circle before disappearing from radar at 06:18:44.[23][27][28] The cockpit voice recorder captured multiple warnings, including a stall warning, sounding in the cockpit during the final minutes of the flight.[29] No distress signal was sent from the aircraft.[30][31]

Timeline of disappearance

Elapsed (HH:MM) Time Event
UTC WIB
UTC+7
SST
UTC+8
00:00 27 December 28 December Flight departed from Juanda International Airport.[lower-alpha 2] Scheduled departure was 05:20 WIB.[11]
22:35 05:35 06:35
00:37 23:12 06:12 07:12 Pilots requested and received air traffic controller (ATC) clearance to divert left from the flight plan to avoid bad weather. The pilot then also requested permission to climb from Lua error in Module:Convert at line 272: attempt to index local 'cat' (a nil value). to Lua error in Module:Convert at line 272: attempt to index local 'cat' (a nil value).. Jakarta ATC deferred this request because of traffic.[11][18][19]
00:39 23:14 06:14 07:14 ATC offered permission to climb, but no response was received from pilots.[22]
00:42 23:17 06:17 07:17 Radar contact was lost, according to AirNav Indonesia. AirAsia initially reported that contact was lost at 06:24.[11][13][32][33]
00:43 23:18 06:18 07:18 ADS-B transponder signal was lost, with last position reported as Lua error in package.lua at line 80: module 'strict' not found., according to Indonesia's Ministry of Transport.[27]
01:20 23:55 06:55 07:55 AirAsia Flight QZ8501 was officially declared missing. Its last known position is over the Java Sea, Karimata Strait between the islands of Belitung and Kalimantan.[34]
01:55 28 December 07:30 08:30 The aircraft missed scheduled arrival at Singapore Changi Airport.
00:30
04:47 03:22 10:22 11:22 Search and rescue (SAR) operations were activated by the Indonesia National Search and Rescue Agency (Basarnas) from the Pangkal Pinang office.[35]
04:55 03:30 10:30 11:30 The Civil Aviation Authority of Singapore (CAAS) and Changi Airport Group (CAG) Crisis Management Centres were reported to have been activated, working with the airline’s crisis management team.[36]
05:06 03:41 10:41 11:41 AirAsia announced on Facebook and Twitter (six minutes later) that AirAsia flight QZ8501 from Surabaya to Singapore lost contact with air traffic control.[37][38]

Search and recovery

Shortly after the aircraft was confirmed to be missing, unconfirmed reports stated that wreckage had been found off the island of Belitung in Indonesia.[39][40][41] Indonesia's National Search and Rescue Agency (Basarnas) deployed seven ships and two helicopters to search the shores of Belitung and Kalimantan.[42] The Indonesian Navy and the provincial Indonesian National Police Air and Water Unit each sent out search and rescue teams.[43] In addition, an Indonesian Air Force Boeing 737 reconnaissance aircraft was dispatched to the last known location of the airliner.[44]

The Indonesian Navy dispatched four ships by the end of the first search day and the Air Force deployed aircraft including a CASA/IPTN CN-235.[45] The Indonesian Army deployed ground troops to search the shores and mountains of adjacent islands.[46] Local fishermen also participated in the search.

Ongoing search and rescue operations were under the guidance of the Civil Aviation Authority of Indonesia.[47] The search was suspended at 7:45 pm local time on 28 December due to darkness and bad weather, to be resumed in daylight.[48] An operations center to coordinate search efforts was set up in Pangkal Pinang.[49] The search area was a 270-nautical-mile (500 km) radius near Belitung Island.[11]

Search and rescue operations quickly became an international effort. By 30 December naval and air units from Singapore, Malaysia and Australia had joined Indonesian authorities in patrolling designated search areas.[50] Singapore's Rescue Coordination Centre (RCC) deployed three C-130 Hercules aircraft to aid in the search and rescue operation.[51][52] A Formidable-class frigate, a Victory-class corvette, a Landing Ship Tank, and a submarine support and rescue vessel subsequently took part in the search and rescue after Indonesia's National Search and Rescue Agency accepted the offer of help from the Republic of Singapore Navy. Singapore's Ministry of Transport provided specialist teams from the Air Accident and Investigation Bureau and underwater locator equipment.[52] The Malaysian government set up a rescue coordination centre at Subang and deployed three military vessels and three aircraft, including a C-130, to assist in search and rescue operations.[53][54][55] Australia deployed a P-3 Orion to assist in the search and rescue operation.[56][57] Elements of the United States Navy joined the search effort; USS Sampson arrived on station late on 30 December,[58] and USS Fort Worth on 3 January.[59]

By 5 January, 31 bodies had been recovered with the aid of the Russian and the US search teams.[60] Divers entered the main section of the fuselage underwater and discovered 6 bodies on 24 January.[61][62]

More than ninety vessels and aircraft from Indonesia, Singapore, Malaysia, Australia, South Korea, Japan, China, the United States, and Russia participated in the search.[63][64][65][66] This fleet included three ships with underwater detectors and two fuel tankers seconded to ensure efficient operation of the vessels in the search area.[67] On 2 January the Indonesian Ministry of Transport reported that two other Indonesian tender vessels had been fitted with equipment which could detect acoustic signals from the flight recorder ("black box") beacons and airframe metal, as well as multibeam side scan sonar.[68]

The official search for bodies ended on 17 March, after 106 bodies had been recovered. 56 bodies remained unaccounted for.[7][69][70]

A live Reddit feed that was constantly updating the details of the search and recovery efforts, leaked details of the operation. An April press conference revealed details discovered by the BASARNAS rescue team divers. 115 remains (including body parts) were recovered. 111 of them are believed to be from 99 passengers.[71]

Wreckage

An offshore supply ship with the tail of PK-AXC on its stern on 10 January 2015

On the day of the disappearance, a fisherman observed "a lot of debris, small and large, near Pulau Tujuh. [...] It looked like the Air Asia colours."[72][73][74] Another fisherman reported that, while moored on Sunday at Pulau Senggora, south of the town of Pangkalan Bun in Central Kalimantan, "Around 7am, I heard a loud booming sound. Soon afterwards, there was haze that usually happened only during the dry season. [...] Before the exploding sound, my friends saw a plane from above Pulau Senggaro heading towards the sea. The plane was said to be flying relatively low but then disappeared."[75][76]

The fishermen's reports, delivered after they had returned home the next day, were credited with guiding the search and rescue team to the vicinity of the crash.[75] The first items of wreckage were spotted by search aircraft on 30 December in the Karimata Strait, 10 kilometres (6.2 mi) from where the crew last contacted air traffic control,[77][78][79][80] and three bodies were recovered by the warship KRI Bung Tomo.[81][82][83][84][lower-alpha 5] Also on 30 December Indonesia's Search and Rescue Services reported that the wreckage of the aircraft had been located on the Java Sea floor, 97–100 nautical miles (180–185 km) southwest of Pangkalan Bun.[citation needed]

On 31 December, Basarnas claimed that a sonar image obtained 30 December by an Indonesian naval ship appeared to show an aircraft upside down on the seabed in about 24–30 m (80–100 ft) of water, approximately 3.2–3.5 km (2.0–2.2 mi) from the debris found on 30 December.[87][88][89] The head of the Search and Rescue Agency also denied the existence of any sonar images of the wreckage (as well as the reported recovery of a body wearing a life vest).[27] He stressed that only official information from his Search and Rescue service can be considered to be reliable.

On 2 January 2015, Basarnas reported evidence of a fuel slick on the water surface in the search area, but detection of the fuselage remained unconfirmed.[67]

At a press conference given on the morning of 3 January by Basarnas, the discovery of two large submerged objects was reported: 9.4m × 4.8m × 0.4m, and a thin object 7.2m × 0.5m.[90] Also, the previously reported fuel slick was confirmed. A later media report mentioned four large sections of wreckage, the largest being 18m × 5.4m × 2.2m located at Lua error in package.lua at line 80: module 'strict' not found..[91] Later in the day, Basarnas announced[92] the discovery of the two larger "adjacent" objects in the afternoon of 3 January was confirmed, but apparently not "adjacent" to the first two somewhat separated items found the previous day. The two additional items were observed to be 18m × 5.4m × 2.2m and 12.4m × 0.6m × 0.5m. No more bodies were found, leaving the total at 30.

On 7 January divers found parts of the aircraft including a portion of the tail.[93] Other portions of the tail are expected to lie nearby.[94][95] On 10 January divers used an inflatable device to bring the aircraft's tail to the surface of the sea.[96][97] They continued to search the sea floor within 500 metres (1,600 ft) of where faint pings were heard.[98]

The flight data recorder was recovered by Indonesian divers on 12 January at Lua error in package.lua at line 80: module 'strict' not found.,[99] within 4 km (2.5 mi) of part of the fuselage and tail.[27] Later in the day the cockpit voice recorder was located[100] and was recovered the following day.[101]

On 14 January searchers located a large portion of the fuselage with one wing attached.[102] On 25 January ropes around the fuselage snapped during an initial failed effort to raise the wreckage. Four bodies were recovered, taking the total recovered to 69. More bodies were thought to be inside. Rear Admiral Widodo, who is in charge of recovery operations, said that the fuselage might be too fragile to be lifted.[103]

On 27 February salvage workers recovered a large piece of fuselage, including the wings, of the A320. Lifting balloons were used to lift the fuselage, but the first attempt failed as the balloons deflated.[104] By March 2015 all large pieces of fuselage from the jet had been lifted from the seafloor and moved for investigation purposes.

Aircraft

The aircraft was an Airbus A320-216,[lower-alpha 6] with serial number 3648, registered as PK-AXC. It first flew on 25 September 2008, and was delivered to AirAsia on 15 October 2008. The aircraft had accumulated approximately 23,000 flight hours over 13,600 flights. It had undergone its most recent scheduled maintenance on 16 November 2014.[13] The aircraft was powered by two CFM International CFM56-5B6 engines and was configured to carry 180 passengers.[105]

Passengers and crew

Persons on board by nationality:[106]
Nationality No.
 Indonesia[lower-alpha 7] 155
 South Korea 3
 France[lower-alpha 8] 1
 Malaysia 1
 Singapore 1
 United Kingdom[lower-alpha 9][107] 1
Total 162

AirAsia released details of the 155 passengers which included 137 adults, 17 children, and one infant. The crew consisted of two pilots and four flight attendants. A company engineer was also on board and was not counted as one of the passengers.[108]

The pilots on board the flight were:[109]

  • Captain Iriyanto,[lower-alpha 10] age 53, an Indonesian national, had a total of 20,537 flying hours, of which 6,100 were with AirAsia Indonesia on the Airbus A320. The captain began his career with the Indonesian Air Force, graduating from pilot school in 1983 and flying jet fighter aircraft. He took early retirement from the air force in the mid-1990s to join Adam Air, and later worked for Merpati Nusantara Airlines and Sriwijaya Air before joining Indonesia AirAsia.[110]
  • First Officer Rémi Emmanuel Plesel, age 46, a French national, had a total of 2,275 flying hours with AirAsia Indonesia.[108] He was originally from Le Marigot, Martinique,[111] and had studied and worked in Paris. He was living in Indonesia.[112]

41 people who were on board the AirAsia flight were members of a single church congregation in Surabaya. Most were families with young children travelling to Singapore for a new year's holiday.[113]

The bodies began to be returned to their families on 1 January 2015. At that time the East Java Department of Visual Identification commissioner stated that the victims were identified by the means of post-mortem results, thumb prints and their personal belongings.[114]

Investigation

The events leading to the crash were investigated by Indonesia's National Transportation Safety Committee (KNKT or NTSC). Assistance was provided by Australia, France, Singapore, and Malaysia.[115]

Data from the flight data recorder were downloaded.[116] One-hundred and twenty-four minutes of cockpit dialogue was successfully extracted from the cockpit voice recorder. The sound of many alarms from the flight system can be heard in the final minutes, almost drowning out the voices of the pilots. The investigators ruled out a terrorist attack as the cause and then examined the possibility of human error or aircraft malfunction.[29] The aircraft altitude recorded by ATC radar increased from Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). to Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). between 06:17:00 and 06:17:54 WIB, at an initial rate of up to Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value).. At 06:17:54, the aircraft descended from Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). to Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). in six seconds, and to Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). in 31 seconds.[23][clarification needed]

The Indonesian Agency for Meteorology, Climatology and Geophysics had reported that bad weather was believed to be the major factor to triggering the incident, specifically a weather phenomenon called atmospheric icing, "which can cause engine damage due to a cooling process".[117]

Acting director of Air Transportation, Djoko Murjatmodjo, clearly stated that the investigation of the flight route and the investigation of the crash itself are separate. Murjatmodjo said that "AirAsia is clearly wrong because they didn’t fly at a time and schedule that was already determined."[104] Both Singapore’s civil aviation authority and the Changi Airport Group stated that Air Asia was allowed daily flights between Surabaya and Singapore.[118] Tatang Kurniadi, head of Indonesia’s national transportation safety committee, stated that sabotage was ruled out as a cause of the incident by the black boxes, and a preliminary report was supposedly submitted to the International Civil Aviation Organisation by early February.

Final NTSC report

FDR data at the time of the stall showing sidesticks dual input. The captain is pushing down (Left, +10), the co-pilot is pulling up (Right, -10), which resulted in no movement of the elevator control surfaces (= 0) and the plane kept stalling until the end of the blackbox recording.[119]

After studying the wreckage of the Airbus A320-216 as well as the two black boxes and the cockpit recorder, Indonesia's National Transportation Safety Committee issued a report with their conclusions from the investigation on 1 December 2015. The report stated that the sequence of events that led to the crash started with a malfunction in two of the plane’s rudder travel limiter units.[120] A tiny soldered electrical connection in the rudder-travel limiter unit was found to be cracked, causing it to send four amber master caution warnings to the electronic centralised aircraft monitor (ECAM) system.[121][122] The ECAM system gave the warning "Auto Flight Rudder Travel Limiter System", and the pilot in command followed the instruction book for ECAM procedures, by toggling the flight augmentation computer (FAC) 1 and 2 buttons on the cockpit's overhead panel to off and then on.[123] The crew repeated the procedure for the first three warnings.[124]

Specifics in the report indicate that French First Officer Rémi Emmanuel Plesel was at the controls just before the stall warning sounded in the cockpit indicating that the jet had lost lift. The final step of the attempted fix consisted of one of the pilots pulling out and then pushing in the circuit breaker of the Flight Augmentation Computer (FAC),[125] which disengaged the autopilot and the system did not start up again after the circuit breakers were reset.[126] This circuit breaker is not on the list of circuit breakers that are allowed to be reset in flight,[127] and disabling both FAC computers places the aircraft in alternate law mode, disengaging the autopilot and stopping the automatic stall protection.[128] The FAC is the part of the fly-by-wire system in A320 aircraft responsible for controlling flight surfaces including the rudder. Without the FAC's computerized flight augmentation, pilots would have to "rely on manual flying skills that are often stretched during a sudden airborne emergency".[129] When the crew was required to fly the Airbus A320 manually, there was an unexplained nine-second delay between the start of the roll and a pilot attempting to take control.[130] After nine seconds, the aircraft was banking at a 54° angle.

The report did not specifically conclude that pilot error caused the crash[131] while detailing the chain of events leading to the loss of Flight 8501. However, one of the investigators, the NTSC's Nurcahyo Utomo, referred to an apparent miscommunication between the pilots (based on the recordings on the cockpit voice recorder) and said that the malfunction should not have led to a total loss of control had they followed the recommended procedure.[8]

The example of miscommunication between the pilots was when the plane was in a critical stalling condition, the co-pilot misunderstood the captain's command "pull down"; instead of pulling the airplane's nose down (pushing up the stick, to regain speed and escape stall), he pulled the stick down. Because the captain was also pushing up the stick and because Airbus has dual input system, the plane doesn't change its condition and keeps stalling until the end of black box recording.

Specifically, the report stated, "Subsequent flight crew action resulted in inability to control the aircraft... causing the aircraft to depart from the normal flight envelope and enter a prolonged stall condition that was beyond the capability of the flight crew to recover".[1] CNN's aviation correspondent Richard Quest summarized the chain of events as follows: "it's a series of technical failures, but it's the pilot response that leads to the plane crashing."[132]

On 3 December 2015, Indonesia's air transportation director general Suprasetyo said that the National Safety Transportation Board (KNKT) had provided recommendations as to tightened controls on aircraft maintenance and flight crew competence. He added that the government had implemented "... a series of corrective actions as a preventive measure so that the same accident will not happen again in the future."[133] Suprasetyo also confirmed that the suspension of Indonesia AirAsia’s Surabaya–Singapore route would not be lifted until the carrier had completed the steps recommended by the KNKT.

Aftermath

AirAsia

Following the disappearance, all AirAsia subsidiaries changed their website and social media branding to greyscale images, in mourning for the presumed deaths of the passengers; Changi Airport's Facebook page was similarly changed as well.[134][135] An emergency call center has also been established by the airline, for family of those who were on board the aircraft,[136] and an emergency information center was set up at Juanda International Airport, providing hourly updates and lodging for relatives.[137] Smaller posts were also opened at Soekarno–Hatta International Airport[138] and Sultan Hasanuddin International Airport.[139]

On 31 December 2014, Indonesia AirAsia retired the flight number QZ8501, changing it to QZ678. The return flight number was also changed, from QZ8502 to QZ679.[140]

Subsequent to the 1 December 2015 NTSC report as to the causes of the crash, the airline said it had already implemented improved pilot training. The founder of Indonesia AirAsia, Tony Fernandes, posted the following tweets on Twitter: "These are scars that are left on me forever but I remain committed to make Airasia the very best" and "We owe it to the families and my crew. My heart and deep sorrow goes out to all the families involved in QZ8501."[141] In another tweet, Fernandes wrote: "There is much to be learned here for AirAsia, the manufacturer and the aviation industry. We will not leave any stone unturned to make sure the industry learns from this tragic incident."[142]

Airbus

Immediately after the NTSC report on the crash was released on 1 December 2015, the manufacturer of the A320 aircraft was not ready to provide a comment, stating in an e-mail that “Airbus has just received the final accident report. We are now carefully studying its content.”[143]

Indonesia

AirAsia did not have any official permission to fly the Surabaya–Singapore route on Sunday – the day of the crash – but was licensed on four other days of the week, and, according to an Indonesian Ministry of Transport statement, "The Indonesian authorities are suspending the company's flights on this route with immediate effect pending an investigation."[14] In response on the same day, the Civil Aviation Authority of Singapore (CAAS) and the Changi Airport Group (CAG) made a clarification that AirAsia QZ8501 "has been given approval at Singapore's end to operate a daily flight for the Northern Winter Season from Oct 26, 2014 to Mar 28, 2015".[144]

On 6 January 2015, Indonesian Ministry of Transport representative Djoko Murjatmojo stated that "officials at the airport operator in Surabaya and [the] air traffic control agency who had allowed the flight to take off had been moved to other duties", and an immediate air transport directive had been issued "making it mandatory for pilots to go through a face-to-face briefing by an airline flight operations officer on weather conditions and other operational issues prior to every flight".[145]

The loss of Flight 8501 also brought attention to the lack of weather radar at Indonesian air traffic control centres.[146][147] According to the Toronto Star, "Indonesia’s aviation industry has been plagued with problems ... pilot shortages, shoddy maintenance and poor oversight have all been blamed following a string of deadly accidents in recent years."[142]

The West Kotawaringin administration in Pangkalan Bun, Central Kalimantan planned to build a memorial for the Air Asia flight which also doubles as a monument for aviation safety. Cental Kalimantan deputy governor Achmad Diran also stated that the monument is also going to be the symbol of gratitude and appreciation for the efforts of the National Search and Rescue Agency. The cornerstone ceremony took place on Wednesday, and was attended by local and state officials and representatives from Australia and Singapore. West Kotawaringin regent Ujang Iskandar stated that “With this monument, we hope that the families and the government will lay flowers every Dec. 28, and continue the dialogue on aviation safety in Indonesia." On March 22, there was a gathering of people near the site of the crash and the crowd laid flowers around.[148]

Family members of crew members and passengers

Air Asia has reportedly offered US$32,000 or Rp300 million to each of the grieving family members of the victims of the incident as 'initial compensation from an overall part of compensation, Wall Street Journal claimed from a letter on Air Asia stationary dated January 2 grieving family member David Thejakusuma received; who had 7 family members on the flight, the amount for each family member he lost.[149]

On Monday, the 16 of March, Monash University awarded in the form of posthumous title (award of posthumous degree) the Bachelor of Commerce to one of the late crash victims, Kevin Alexander Sujipto. Professor Colm Kearney, Dean of the Faculty of Business and Economics presented it to a member of his family. A memorial service was held alongside the presentation of the award, and was attended by the Consul General of Indonesia for Victoria and Tasmania Dewi Savitri Wahab, 40 of the deceased's friends and representatives from the Indonesian Student Association in Australia (PPIA) Monash University branch.[150]

Legal proceedings

France opened a criminal investigation to investigate possible manslaughter charges.[151] The family of the first officer, a French national, have filed a lawsuit against AirAsia in connection to the lack of permission to fly on that day, claiming the airline was "endangering the life of others".[151]

Surabaya Mayor Tri Rismaharini says her administration is ready to sue AirAsia should it ignore the rights of the families of passengers on flight QZ8501, following the suspension of the airline’s flight permit from the East Java city to Singapore. Risma said her administration had also consulted with legal experts from Airlangga University on the fears of most families regarding the difficulties in disbursing insurance funds, after the Transportation Ministry regarded the Surabaya-Singapore flight on Dec. 28 as illegitimate. She said her administration continued to collect data on the victims, including their valuable belongings. The data would later be used for insurance purposes and matters related to the beneficiary rights of the affected families.[152]

A US-based aviation lawyer was planning to sue AirAsia claiming that they are "representing" 10 families over an aircraft malfunction following the crash of Flight QZ8501. Principal of Chicago-based Wisner Law Firm Floyd Wisner said that although preliminary investigations found that weather was a factor, the Airbus A320-200 suffered a malfunction of the fly-by-wire system. According to the statement, the lawsuit, which was filed in the US state of Illinois, states that “at the time the accident aircraft left the control of defendant Airbus, it was defectively and unreasonably dangerous,” and names Honeywell International, Motorola Inc and other suppliers along with Airbus as defendants.[153][154]

The case is Aris Siswanto et al. v Airbus, SAS et al., 1:15-cv-05486. U.S. District Court, Northern District of Illinois (Chicago). As of 30 June 2015, the suit had still named only Airbus and its suppliers but AirAsia was to be added as a defendant, according to Floyd Wisner of the Wisner law firm.[155]

Air transport industry

Following the recovery of the flight recorders, on 12 and 13 January, an anonymous International Civil Aviation Organization (ICAO) representative said, "The time has come that deployable recorders are going to get a serious look." Unlike military recorders, which jettison away from an aircraft and float on the water, signalling their location to search and rescue bodies, recorders on commercial aircraft sink. A second ICAO official said that public attention had "galvanized momentum in favour of ejectable recorders on commercial aircraft".[156]

Indonesian tourism

Indonesia's tourism was badly affected by the incident. According to the head of Indonesia’s Central Statistics Agency (CSA) Suryamin in a press conference at his office on the 1st of April, the accident has caused the number of foreign visitors to decline. Figures from the Indonesian Ministry of Tourism has shown that the number of incoming foreign tourists at Surabaya’s Juanda Airport has declined by 5.33 percent, Jakarta’s Soekarno-Hatta International Airport by 15.01 percent, and Bandung’s Husein Sastranegara Airport by 10.66 percent.[157]

See also

Notes

  1. Location where the aircraft's flight data recorder was found under wreckage on the sea floor
  2. 2.0 2.1 Also reported as occurring at 05:36 or 05:32 WIB.[12][13]
  3. Indonesia AirAsia did have permission to fly this route four other days of the week.[14]
  4. At least one version of the story claims that Flight 8501 requested to climb, but did not specify to what altitude and that Jakarta Centre asked for an altitude, but no response was given by Flight 8501.[22]
  5. At 10:05 UTC, Reuters, quoting Indonesian official Manahan Simorangkir, reported that 40 bodies had been recovered,[85] but this was later retracted by an Indonesian navy spokesman as a "miscommunication by staff".[86]
  6. The aircraft was an Airbus A320-200 model; the 16 specifies it was fitted with CFM International CFM56-5B6 engines.
  7. 149 passengers and six crew members, including the Captain
  8. One crew member, the first officer
  9. Dual British-Hong Kong citizen boarding with British passport.
  10. Iriyanto is a mononym (one-word name), which is common for Indonesian names.

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 11.2 11.3 11.4 Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 13.2 Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 14.2 Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 15.2 15.3 Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 22.2 Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 23.2 23.3 23.4 Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. 27.0 27.1 27.2 27.3 27.4 Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. 29.0 29.1 Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. 52.0 52.1 Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. 67.0 67.1 Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. 75.0 75.1 Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found.
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. Lua error in package.lua at line 80: module 'strict' not found.
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. 104.0 104.1 Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. 108.0 108.1 Lua error in package.lua at line 80: module 'strict' not found.
  109. Lua error in package.lua at line 80: module 'strict' not found.
  110. Lua error in package.lua at line 80: module 'strict' not found.
  111. M. Pf. avec AFP. "Crash d'Air Asia : «Enfant, il voulait être pilote», témoigne la mère de Rémi Plésel" (Archive). Le Parisien. 29 December 2014. Retrieved on 31 December 2014.
  112. "Le copilote de l'avion d'AirAsia disparu entre l'Indonésie et Singapour est un martiniquais" (Archive). Martinique 1ère (FR). 28 December 2014. Retrieved on 31 December 2014.
  113. ([1])
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. Lua error in package.lua at line 80: module 'strict' not found.
  122. Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. Lua error in package.lua at line 80: module 'strict' not found.
  128. Lua error in package.lua at line 80: module 'strict' not found.
  129. Lua error in package.lua at line 80: module 'strict' not found.
  130. Lua error in package.lua at line 80: module 'strict' not found.
  131. Lua error in package.lua at line 80: module 'strict' not found.
  132. Lua error in package.lua at line 80: module 'strict' not found.
  133. Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. Lua error in package.lua at line 80: module 'strict' not found.
  136. Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. Lua error in package.lua at line 80: module 'strict' not found.
  139. Lua error in package.lua at line 80: module 'strict' not found.
  140. Lua error in package.lua at line 80: module 'strict' not found.
  141. Lua error in package.lua at line 80: module 'strict' not found.
  142. 142.0 142.1 Lua error in package.lua at line 80: module 'strict' not found.
  143. Lua error in package.lua at line 80: module 'strict' not found.
  144. Lua error in package.lua at line 80: module 'strict' not found.
  145. Lua error in package.lua at line 80: module 'strict' not found.
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Lua error in package.lua at line 80: module 'strict' not found.
  148. Lua error in package.lua at line 80: module 'strict' not found.
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. Lua error in package.lua at line 80: module 'strict' not found.
  151. 151.0 151.1 Lua error in package.lua at line 80: module 'strict' not found.
  152. Lua error in package.lua at line 80: module 'strict' not found.
  153. Lua error in package.lua at line 80: module 'strict' not found.
  154. Lua error in package.lua at line 80: module 'strict' not found.
  155. Lua error in package.lua at line 80: module 'strict' not found.
  156. Lua error in package.lua at line 80: module 'strict' not found.
  157. Lua error in package.lua at line 80: module 'strict' not found.

External links

Wikinews-logo.svg News related to Indonesia AirAsia Flight 8501 at Wikinews

Media related to Lua error in package.lua at line 80: module 'strict' not found. at Wikimedia Commons