TransAsia Airways Flight 235

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
TransAsia Airways Flight 235
250px
Still from a dashcam video, showing Flight 235's left wing clipping a taxi and the Huandong Viaduct, moments before the aircraft crashed into the Keelung River
Accident summary
Date 4 February 2015 (2015-02-04)
Summary Crashed soon after takeoff; under investigation
Site Keelung River, Taipei, Taiwan
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 53
Crew 5
Injuries (non-fatal) 17 (including 2 on ground)
Fatalities 43
Survivors 15
Aircraft type ATR 72-600
Operator TransAsia Airways
Registration B-22816
Flight origin Taipei Songshan Airport, Songshan, Taipei, Taiwan
Destination Kinmen Airport, Kinmen, Fujian

TransAsia Airways Flight 235 (GE235/TNA235) was a domestic flight that crashed into the Keelung River on 4 February 2015, shortly after takeoff from Taipei Songshan Airport, 5.4 km (3.4 mi) to the west. The TransAsia Airways flight, operated with a ten-month-old ATR 72-600 aircraft, was flying from Taipei to Kinmen (Quemoy), a Taiwanese island off the coast of mainland Fujian, with 53 passengers and five crew on board. There were 15 survivors.

Two minutes after takeoff, the pilots reported an engine flameout. Flight 235 climbed to a maximum height of 1,500 feet (460 m), then descended. The other, working engine was then shut down mistakenly.[1][2] Immediately before crashing into the river, it banked sharply left and clipped a taxi travelling west on the Huandong Viaduct, then the viaduct itself, with its left wing.

Flight 235 was the second fatal accident involving a TransAsia Airways ATR aircraft within seven months. Flight 222 crashed on 23 July 2014, killing 48 of the 58 on board.

Flight

Flight 235 departed Taipei Songshan Airport at 10:52 a.m. Taiwan time (02:52 UTC), for its destination of Kinmen Airport, with 53 passengers and five crew members on board.[3] It climbed to an altitude of 1,500 feet (460 m) and then began descending until it crashed.[4] The last pilot communication to air traffic control was: "Mayday, mayday, engine flameout."[5][6] At 10:54, the aircraft crashed into the Keelung River, on the border of Nangang District of Taipei and Xizhi District of New Taipei.

The crash was recorded by the dashcams in several cars travelling west along the elevated Huandong Viaduct next to the river. The aircraft, flying level, first cleared an apartment building. Then it rolled sharply, at nearly a 90-degree bank angle, left wing down. As the aircraft flew low over the elevated viaduct, its left wingtip struck the front of a taxi travelling west on the viaduct, and the outboard section of the wing was torn off when it struck the concrete guardrail at the edge of the viaduct.[6][7] The aircraft continued its roll and impacted the water upside down,[8] breaking into two main pieces.[9] Two people in the taxi were injured.[5][7]

At the time of the accident, no adverse weather phenomena were observed. At 11:00 a.m., the cloud base at Songshan was about 1,500 feet (460 m), the visibility was unlimited, and a light breeze was blowing from the east at 10 knots (19 km/h; 12 mph). The temperature was 16 °C (61 °F).[4]

Rescue and recovery

File:TransAsia Airways Flight 235.JPG
The aircraft in the Keelung River under rescue, Huandong Viaduct in background

Taipei police and fire departments received dozens of calls from eyewitnesses, almost immediately after the crash. The Taipei Fire Department, military and volunteer rescue workers arrived at the crash scene only minutes later. They began removing survivors from the rear section of the semi-submerged fuselage and ferried them to shore in inflatable boats. Divers were forced to cut the seat belts of dead passengers, located mostly in the front section, to remove their bodies. That work was made difficult by low visibility underwater.

The aircraft's flight recorders were recovered shortly after 4 p.m. that day. After 8 p.m., cranes were used to lift large sections of the fuselage ashore.[5][10][11]

Of the 58 people on board the flight, only 15 survived.[12] On 5 February, the bodies of the pilot, co-pilot and observer were recovered.[13] One of the two flight attendants survived.[14]

Aircraft

B-22816, 34 days before it crashed

The aircraft involved in the accident was an ATR 72-600 twin turboprop, registration B-22816, MSN 1141. It first flew on 28 March 2014, and was delivered to TransAsia Airways on 15 April 2014.[15] Both Pratt & Whitney Canada PW127M engines were replaced due to technical issues on 19 April 2014.[16]

Passengers and crew

The passenger manifest was composed of 49 adults and four children. Thirty-one passengers were mainland Chinese; many were visitors from Xiamen on a six-day tour of Taiwan.[17][18] The remaining 22 passengers were Taiwanese.[6]

The flight crew consisted of two pilots, both ranked as captains; the pilot was aged 42, with a total of 4,914 flying hours and the co-pilot was 45, with a total of 6,922 flying hours.[19][4][18] There was also an observer seated in the cockpit jump seat, who had a total of 16,121 flying hours.[20] There were also two flight attendants as cabin crew. All crew members were Taiwanese citizens, the copilot was a dual New Zealand–Taiwanese citizen.[19]

Investigation

The Taiwanese Aviation Safety Council (ASC) is leading the investigation into the accident.[6][21] The French BEA was invited to represent the country of manufacture, and the Transportation Safety Board of Canada will represent the country of engine manufacture. Other parties to the investigation include the Taiwanese Civil Aeronautics Administration, the operator (TransAsia), the aircraft (ATR) and engine (Pratt & Whitney Canada) manufacturers, and Transport Canada.[22] The cockpit voice recorder and flight data recorder were recovered in the evening of 4 February, and the data were being analysed.[4] According to the executive director of the ASC, Thomas Wang, the aircraft's right engine triggered an alarm just 37 seconds after takeoff.[23] Whereas the crew reported a flameout,[24] according to Wang, data showed one of the engines had in fact been moved into idle mode.[23] Soon the right engine failed to produce enough thrust for its rotating propeller, lapsing into auto-feathering.[24] A restart was attempted, but the aircraft crashed 72 seconds later.[23]

On 6 February, investigators revealed that the left engine, which does not appear to have had suffered a malfunction, had been manually shut off,[25] while cautioning that it was "too early to say if human error was a factor".[26] Investigators released the following preliminary sequence of events. All times are local (UTC+8).[22][27]

  • 10:51:13 — Crew receives take-off clearance
  • 10:52:34 — Tower asks crew to contact Taipei Departure
  • 10:52:38 — Right engine failure alert; master warning sounds for 3s
  • 10:53:04 — Crew reduces power to the left engine
  • 10:53:12–18 — Stall warning sounds
  • 10:53:24 — Crew cuts power to the left engine
  • 10:53:34 — Crew declares emergency: "Mayday, mayday, engine flameout"
  • 10:54:09 — Crew calls for restarting the left engine multiple times
  • 10:54:20 — Left engine is restarted
  • 10:54:34 — Master warning sounds again
  • 10:54:35 — An unidentified sound is heard
  • 10:54:36 — Recordings end

The ASC issued an interim report on 2 July. Without assigning responsibility for the crash, the report confirmed that after the failure of one engine the pilot incorrectly shut down the other, working engine.[1][2] It also said that the pilot in command had failed simulator training in May 2014, partly because of his insufficient knowledge about the procedure for handling an engine flameout on takeoff. He passed a re-test the following month. The ASC is expected to publish its final report in April 2016, with a draft version in November 2015.[1][2]

Press reports

An unnamed source was reported to have claimed that the pilot had complained of "engine abnormalities" and requested an urgent inspection of the aircraft shortly before its final take-off, but had been rebuffed.[28] This assertion has been denied by both TransAsia Airways and the Civil Aeronautics Administration, the former of whom has released the maintenance records for both powerplants, both propellers, and the airframe.[29]

Reactions

The locations of the accident and departure airports shown on a map of Taiwan.
Kinmen Airport
Kinmen Airport
Taipei Songshan Airport
Taipei Songshan Airport
TransAsia Airways Flight 235
Location of the accident and departure/destination airports

TransAsia Airways

Following the accident, TransAsia Airways changed its website and social media branding to greyscale images, in mourning for the presumed deaths of the passengers. On 5 February, TransAsia retired the flight number GE235, changing it to GE2353.[30]

Taiwan

The spokesperson of the Office of the President of the Republic of China reported that President Ma Ying-Jeou was very concerned about the accident and had given orders to the Executive Yuan and related authorities to provide maximum assistance with the rescue. Immediately after the accident, the President of the Executive Yuan, Mao Chi-Kuo, contacted the Ministry of Transportation and Civil Aeronautics Administration to instigate an investigation into the crash, and the minister of national defense to prepare the military for the rescue.[31]

China

Over half of the passengers on board the aircraft were mainland Chinese. On 5 February 2015, Xi Jinping, the president of China, released a statement, ordering that accurate information on the aircraft be obtained as quickly as possible, and that "assistance [be provided] in treating the injured".[32] On the same day, Chinese Premier Li Keqiang instructed relevant departments to obtain accurate information from Taipei as quickly as possible.[33]

Aftermath

The Civil Aeronautics Administration announced it would subject all TransAsia Airways ATR pilots to supplementary proficiency tests between 7 and 10 February,[4] resulting in the cancellation of more than 100 TransAsia flights. Ten pilots who failed the engine-out oral test and a further nineteen who did not attend were suspended for one month, pending a re-test. TransAsia subsequently demoted one pilot from captain to vice-captain.[1] Reuters reported that the government ordered all Taiwanese airlines to "review their safety protocols".[34][35] The Taiwanese CAA announced that it is focusing its attention on TransAsia's training and operations and the country's labor ministry fined the airline for breaches of the labor code over excessive working hours.[36][37]

On 11 February, TransAsia offered 14.9 million New Taiwan dollars (about US$475,000) in compensation to the family of each of the dead. This amount includes emergency relief and funeral allowance, totalling NT$1.4M (US$44,300), already paid to each family. Not all of the families have accepted the offer.[38]

See also

  • The Kegworth air disaster – Another incident where a working engine was erroneously shut down in response to the malfunction of a different engine.

References

  1. ↑ 1.0 1.1 1.2 1.3 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 2.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 4.2 4.3 4.4 Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ 5.0 5.1 5.2 Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ 6.0 6.1 6.2 6.3 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. ↑ 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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 復興空難搜救 尋獲最後一具遺體 CNA(Chinese)
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ 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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ 23.0 23.1 23.2 Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ 24.0 24.1 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. ↑ 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. ↑ 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.

External links

Multimedia

Retrieved from "https://infogalactic.com/w/index.php?title=TransAsia_Airways_Flight_235&oldid=721057565"