Aviastar Flight 7503

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Aviastar Flight 7503
DHC-6-300 Aviastar.JPG
An Aviastar de Havilland Canada DHC-6 similar to the aircraft involved in the incident
Accident summary
Date 2 October 2015 (2015-10-02)
Summary Crashed off course, under investigation
Site Pajaja Mountains, Latimojong, Ulusalu, Luwu Regency, Indonesia
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 7
Crew 3
Fatalities 10 (all)[1]
Survivors 0
Aircraft type de Havilland Canada DHC-6 Twin Otter
Operator Aviastar
Registration PK-BRM
Flight origin Andi Jemma Airport, Masamba, Indonesia
Destination Sultan Hasanuddin International Airport, Makassar, Indonesia

Aviastar Flight 7503 (MV7503/VIT7503) was a scheduled 60-minute passenger charter flight, operated by Aviastar (Indonesia) en route from Andi Jemma Airport, Masamba, to Sultan Hasanuddin International Airport, Makassar, Indonesia. On 2 October 2015 it was reported that the de Havilland Canada DHC-6 Twin Otter aircraft, registered PK-BRM with 10 on board, went missing from air traffic controller near Palopo 11 minutes after takeoff. There was no distress call from the plane.[2]

After an extensive and massive search operation, the plane was eventually found crashed on Monday 5 October 2015 and it was confirmed that all 10 on board were dead.[3] It is the third commercial airliner accident and fourth aviation incident involving major airlines in nine months in Indonesia, after Indonesia AirAsia Flight 8501, 2015 Indonesian Air Force Lockheed C-130 Hercules crash, and Trigana Air Service Flight 257. It was the airline's deadliest crash, surpassing the previous crash of a British Aerospace carrying presidential logistics which killed all six people on board.

Flight

The aircraft took off from Masamba Airport at 14:25 WITA (06:25 UTC) with 3 crew and 7 passengers on board.[4] It was expected to land in Makassar one hour later at 15:25, but eleven minutes after take-off, the plane lost contact with the control tower. At the time of the loss, the aircraft was on an elevation of 8,000 ft. According to local reports, the weather was cited as excellent, with visibility above 100 km and winds at 5 knots.[5] The route which was chosen in this flight was a "very safe" route with elevation ranging around 10–100 ft, meaning that there are no mountains or large hills in the route. The communication between the flight crews and the air traffic controller at the time was also reported as very good.[6] The fuel was also counted as enough. As for the condition, the aircraft itself was determined to be in a very good condition according to Aviastar. This was also backed up by evidence from KNKT (National Transportation Safety Committee).[7]

Search

Immediately after the crash, the Indonesian National Search and Rescue Agency (BASARNAS) set up a crisis centre in Makassar. They also sent 100 search and rescue personnel to the area. The first day of the search was by foot. The plane had not yet been located at that time. As nightfall approached, the search was suspended, even though citizens in the regency of Palopo claimed that they saw a "very low" flying plane in the area. These reports were later confirmed to be hoaxes.

On the second day, search and rescue personnel from Masamba and Makassar searched the same area with one helicopter and three aircraft from Aviastar. The search area was widened, from Palopo and the surrounding areas to Luwu shoreline. In a press conference, BASARNAS reported that the position of the missing plane was around 14 nautical square miles. It had officially widened to 24 nautical square miles, which would take around 2.5 hours by land from the nearest city. There were three coordinates which BASARNAS suspected to be the crash site, which is at 14 nautical miles, 24 nautical miles and 34 nautical miles.[8][9] The aircraft was finally located by the signal from the engineer's cellphone, which was set in Airplane Mode. The ELT was also detected, but the search operation was hampered due to poor weather condition in the area. At early dusk, some people reported that the plane was found in the area of Sidrap. The claim was later investigated.[10]

BASARNAS sent around 125 personnel on the second day of the search operations, with National Armed Forces assistance. Head of BASARNAS, Bambang Soelistyo, said in a press conference that his personnel along with the National Armed Forces and some other personnel from Luwu had scoured four main areas, in Luwu regency, Northern Luwu regency and Palopo Regency.[11]

On the third day of the incident search BASARNAS added aircraft. They also added additional personnel from 125 to 299 persons. The Vice Governor of South Sulawesi, Agus Arifin Nu'mang joined the search for the flight from the ground.[12] As the search widened, assistance from various government organizations also arrived, including BPBD, Indonesian Red Cross and the IRC. Relatives of the passengers were also joining the search, hoping for survivors.[13]

Eyewitness

Numerous people claimed that they saw the plane crash, but all of them were giving different locations.[14] Some people claimed that the plane crashed into Palopo Mountains, while others claimed that the plane crashed near Sidrap waterfall. A young student, claimed that the plane was flying very low, and had smoke on the wing, then impacted the sea at the Luwu shoreline.[15] Some villagers also stated that the plane flew into the Barru and Pare-Pare sea. BASARNAS stated that there are possibilities that the plane flew off course, using a different route and flew over the shoreline due to the mountains in the west. As the results the search area was to widen again until Makassar Strait.[16][17]

Recovery

File:PK-BRM crash site.jpg
Crash site of Flight 7503

On the fourth day, the search area was officially widened into the sea.[18] In the afternoon, at 15:55 WITA, some personnel of BASARNAS and the Indonesian police found debris on Latimojong Mountain. BASARNAS later confirmed that the debris belonged to the missing aircraft. Photos taken by BASARNAS shown that the wreckage of the aircraft was burned even days after the disappearance. At the time of the discovery, there were three burned bodies in the area. No survivors were found.[19]

File:PK-BRM wreckage distribution.jpg
Wreckage distribution of Aviastar Flight 7503

On 6 October, the black boxes were recovered as well as the bodies. The black boxes were found in a good condition. BASARNAS took the bodies to a military hospital in Makassar. President Joko Widodo observed the recovery. There were 22 DVI personnel which will help the identification of the victims.[20]

Passengers and crew

All on board the aircraft were Indonesians. There were seven adults, one child and two infants. Among the passengers were the head of Seko Airport in Northern Luwu and five Andi Djemma Airport staff. One family was also on board.[21][22] The pilot and the co-pilot as released by Aviastar, were:

  • Captain Iri Afriadi, with 2,900 hours of flying experience.
  • First Officer Yudhistira Febby with 435 hours of flying experience.[23]

Investigation

As investigators arrived at the crash site, they suspected that the plane bounced twice before exploded and burned. According to reports, the plane hit a tree on the other side of the mountain, as there were broken tree branches found in the area. The plane caught fire and slammed into the top of the mountain, killing all on board. Investigators also created the chronology of the discovery of the wreckage and explained how the plane crashed with drone footage.[24]

A preliminary investigation report was published 21 January 2016. At 06:37 UTC, the pilots agreed to fly direct to Barru as one had this experience. Few second later the second-in-command suggested to delay the direct flight for a while. There was partial cloud formation. At 06:50 UTC, the pilot-in-command told that he wanted to climb and the CVR stopped recording. The aircraft impacted trees and crashed at 7,734 ft.[25]

See also

References

  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. 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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  19. 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. Lua error in package.lua at line 80: module 'strict' not found.
  23. 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.