One-Two-GO Airlines Flight 269

One-Two-GO Airlines Flight 269
One-Two-GO Airlines Flight 269

Crash scene
Accident summary
Date September 16 2007
Type Impact with Embankment
Site Phuket International Airport
Passengers 123
Crew 7
Fatalities 90
Survivors 40
Aircraft type McDonnell Douglas MD-82
Operator One-Two-GO Airlines
Tail number HS-OMG
Flight origin Don Mueang International Airport
Destination Phuket International Airport
Location of Phuket

One-Two-GO Airlines Flight 269 (OG269), a McDonnell Douglas MD-82, crashed into a non-frangible embankment beside runway 27 at Phuket International Airport (HKT) bursting into flames upon impact on September 16, 2007, at about 15:41 ICT during an attempted go-around after an aborted landing, killing 89 of the 130 persons on board. (One survivor succumbed to burn injuries several days after the crash.) OG269 was a scheduled domestic passenger flight from Bangkok to Phuket, Thailand.[1]

Thai crash investigators from the Thailand Department of Civil Aviation initially speculated that wind shear was the cause of the crash. Two years later, National Transportation Safety Board (NTSB) reported that wind shear was not a factor in the crash. [1]

A two-year investigation by NTSB resulted in a report [1] mainly incorporated into the crash report published by the Thai Department of Civil Transportation[2]. Both reports found that the Captain and First Officer had worked hours vastly in excess of the legal flight limits; that the first officer attempted to transfer control to the captain during the go-around; that neither pilot initiated a go-around and that the training and safety programs at the airline were deficient.

Corruption within One-Two-GO Airlines and the Thai Department of Civil Aviation was a factor for crash investigators. A television crew initially learned of fraudulent work rosters for the captain and first officer, obfuscating their illegal work schedule, had been provided to the crash investigators.[3] The lead Thai Department of Civil Aviation investigator, who reported documents he had received from One-Two-GO were fiction. The National Transportation Safety Board report included the true work rosters, obtained by the family of a victim. The NTSB report documents check ride fraud among four other One-Two-GO pilots in the months following the crash.[4] Legal filings[5] and press articles[6] reference an email among executives of One-Two-GO Airlines, including CEO Udom Tantiprasongchai.

More than three years after the crash, the British coroner[7] cited the "flagrant disregard for passenger safety" by the airline and said "the primary failure so far as I am concerned relates to the corporate culture which prevailed both One-Two-GO Airlines and Orient Thai Airlines prior to and following the air crash."

One-Two-Go Airlines is prohibited from operating in European Union nations due to safety concerns.[8] At the time of the accident the airline was owned by Orient Thai Airlines and in July 2010, it fully re-branded as Orient Thai Airlines.



On the day of the crash, the McDonnell Douglas MD-82 [9] departed Bangkok’s Don Mueang International Airport, Thailand at 14:31 local time en route to Phuket International Airport as flight number OG269[2]. The flight crew consisted of captain Arief Mulyadi, an Indonesian national and the Chief Pilot of One-Two-Go Airlines, and a former Indonesian Air Force pilot, first officer Montri Kamolrattanachai, a Thai national who had recently completed his flight training with One-Two-GO’s ab initio program. The aircraft was carrying 123 passengers and 7 crew members. OG269 was the fourth of six flights between Bangkok and Phuket that Arief and Montri were scheduled to fly that day.[2]

On approach to Phuket, captain Arief made several radio communications errors including read-back/hear-back communications and misstating their flight number. First officer Montri was the flying pilot.[2]

Another aircraft landed immediately prior to flight 269 and experienced wind shear. That aircraft's captain contacted the tower and reported wind shear on final and cumulonimbus over the airport, a report audible to all incoming aircraft. Air Traffic Control requested flight 269 acknowledge the weather information provided and re-state intentions. Captain Arief acknowledged the transmission and stated his intention to land.[2]

OG269 conducted an ILS approach just north of the centerline on runway 27. As the landing proceeded, ATC reported increasing winds at 240 degrees from 15–30 knots (28–56 km/h; 17–35 mph), then to 40 knots (74 km/h; 46 mph). Captain Arief acknowledged the reports. ATC requested intentions again. Captain Arief said, “Landing”.[2]

As the aircraft descended to 115 feet (35 m) above ATL, its airspeed dropped. Captain Arief repeatedly called for more power as First Officer Monti attempted the landing. The aircraft continued to descend and fell below 50 feet (15 m) above ATL, causing the auto-throttle to reduce engine thrust to idle. One second later, First Officer Montri called “Go Around”. This was acknowledged by the captain. The first officer then attempted to transfer control of the aircraft to captain Arief. There was no verbal acknowledgement of this from captain Arief.[2]

The pilots retracted the landing gear and set flaps for go-around. The aircraft pitch changed from 2 degrees to 12 degrees as the aircraft climbed, its engines still at idle. Airspeed fell and the aircraft climbed to a maximum altitude of 262 feet (80 m) ATL before beginning to descend. For 13 seconds the engines remained at idle. The aircraft pitch angle decreased to near 0 and then the throttle was manually increased two seconds before impact with an embankment along the runway at 15:40. The aircraft was severely damaged by a post crash fire.[2]


Passengers and crew of OG269 received little benefit from fire and rescue services. On the day of the crash, Phuket Airport did not meet the requirements of fire and rescue protection required by international standards [10] the foam and water in the trucks used three days earlier in a training exercise and had not been restocked. When an airport has a reduction in fire or rescue capacity, ATC is required to notify incoming traffic of the reduction, but no notification was made.[10]

Hampering rescue efforts was a six-foot ditch beside and parallel to runway 27 running the length of the runway. Rescue vehicles were unable to cross this ditch, though they could have entered at either end of the runway. None did.[2]. Survivors complained that only a single ambulance arrived, and forced the healthy into the vehicle, leaving behind trapped and injured.[2]

Additional fire and rescue from the town of Phuket arrived 30 minutes later. Their slower than normal response was due to the ATC radio call to for help from town that an aircraft that had “slid” off the runway rather than declaring an emergency situation.[2] Additionally, the Airport failed to include "Crash on Airport" procedures in its air service manual as required by ICAO, so the highly skilled and trained rescuers within Thailand were never contacted [7]. The only passengers who exited the aircraft alive, did so of their own accord. These inadequate materials and delays may have had a negative impact on passengers who initially survived the crash. Some bodies were found days later in the mud beneath the aircraft.

A non air conditioned airport hanger was used as a morgue until the identity of foreign victims was confirmed via either DNA or fingerprint. The bodies of foreign nationals were repatriated only after cremation or embalming, so autopsies were not possible.

Survivors and fatalities

Of the 130 people on board, 84 passengers and 5 crew members died.[citation needed]. The body of the pilot, Arief Mulyadi, has been identified.[11] As of 09:17 local time (0217 UTC) on September 18, 2007, 21 out of 57 bodies of foreign nationals had also been identified. The airline contacted the rest of the victims' families for evidence to aid in identification. Some victims suffered head injuries caused by dislodged airline internals. Others were trapped and burned alive in the cabin. Many survivors sustained burns. [12]

Various embassies and ministries in Bangkok confirmed the following numbers:[13]

  • Australian embassy: 1 Australian killed and 1 survived
    (National Nine News reported at 3 P.M. on 18 September that Australian foreign minister Alexander Downer and his department felt confident that no more than 2 Australians died in the crash. So far, one has been found and identified.)
  • British embassy: 8 Britons killed and at least 2 injured[14]
  • Canada: 1 killed and 1 injured[15][16]
  • French foreign ministry: 3 French nationals killed, 1 injured, and 6 missing
  • German officials: At least 1 German killed - a 29-year-old man, 4 injured
  • Ireland foreign ministry: 1 Irish national killed
  • Israel media: 8 Israelis killed, 2 injured[17]
  • Swedish foreign ministry: 2 Swedes killed - a 19-year-old female and a 20-year-old male, and 2 survived with minor injuries
  • US embassy: 5 American tourists killed[18]

Three local hospitals treating the injured have released the following survivors according to their nationalities:[19]

1 Australian, 1 Austrian, 8 British, 1 Canadian, 2 Dutch, 4 German, 3 Iranian, 3 Irish, 2 Israeli, 1 Italian, 2 Swedish and 14 Thai.

Survivor and investigator statements

According to Vutichai Singhamany, a safety director at Thailand's Department of Civil Aviation, the pilot had deployed the landing gear on approach to Phuket airport runway 27, but had retracted it whilst attempting a go-around. Singhamany added that the wheels had not touched the runway and that the accident had happened moments after the pilot raised the nose of the aircraft to abort the landing.[20] It appears that the plane was caught in wind shear, causing it to sink abruptly.[21]

23-year-old Parinyawich Chusaeng, who survived the crash on flight 269, told Agence France Presse

"The plane just dropped really fast and then jerked back up. The right wing hit a tree and then the plane hit the ground. The people all around me were burning. Some on the floor and some standing, and they were on fire."

Chaisak Angsuwan, director general of the Air Transport Authority of Thailand said:[22]

"The visibility was poor as the pilot attempted to land. He decided to make a go-around but the plane lost balance and crashed. It was torn into two parts."

A witness, William Harding, said:[19]

"The inside (of the plane) was totally on fire and about five minutes of burning, there was a small explosion that blew off top of the plane."

Canadian survivor, Mildred Anne Furlong, said:[23]

"We started to go for the landing and [the pilot] just about hit the runway, but couldn't make it, so he lifted back up. We started to circle. I thought he was going to circle back around and try again, and then we took a sharp right and we started going for the ground."
"We bounced once and then went straight into an embankment with trees and bushes."
"It was raining really hard. We saw a couple of people who were on fire. Just a handful of us made it out. I counted 17 or 20 who had made it out on their own.".


At the time of the crash, speculation rested on the pilot’s decision to land in poor weather conditions and on the airport’s wind shear detection system which was not operational that day. In the weeks after the crash, the lead crash investigator, Vuttichai Singhamany, continued to indicate wind shear as the likely cause [21].

The US NTSB takes an interest in commercial airline incidents involving US manufactured aircraft, and they arrived on site within days. The NTSB inspected the aircraft, the crash scene, interviewed survivors and witnesses. They took information obtained from the flight data recorder (“black box”) to the United States for analysis. The flight data recorder immediately yielded significant facts about the flight[1], including:

  • Wind shear was not a factor in the crash
  • First Officer Montri was the flying pilot
  • Captain Arief’s radio communications with ATC were error prone
  • Many Crew Resource Management (CRM) issues occurred within the cockpit
  • There was no conversation between the pilots during the final 18 seconds of flight.
  • The go-around (TO/GA) button, used to configure the aircraft for go-around, had not been pushed
  • The throttle was pushed to take-off power only 2 seconds before impact.

Yet Thai investigator Director-General Vuttichai announced that NTSB had notified his department saying that it was “unable to determine the cause of the accident” and “No punishment will be imposed on any agency or personnel after completion of the investigation because the accident was beyond control”.[24]

Meanwhile, immediately after the crash, an unidentified pilot claiming to work at One-Two-GO or Orient Thai Airlines made a posting on a pilots’ internet site detailing incompetence and corruption at the airline[25]. His claims quickly spread on the internet and came to the notice of an Australian Channel 9. A Channel 9 crew, including Nick Farrow and Sarah Ferguson, came to Thailand to investigate. Their resulting program, broadcast in November 2007, detailed the accusations of maintenance fraud and specifically by CEO Udom Tantiprasongchai, coercion and bribery of pilots to fly illegal hours leveled by a number of One-Two-GO.[3]

Furthermore, the program contained an interview with lead Thai investigator Director-General Vuttichai as he reviewed the daily flight rosters for One-Two-GO given to him by reporter Ferguson, documenting captain Arief and first officer Montri’s routes showing that both pilots had flown vastly beyond the legal limit for the week and for month of the crash. Director-General Vuttichai said he would demand an explanation for the fraud from One-Two-GO. [3]

But the NTSB did not receive information about the flight rosters from the Thai investigators or from the airline.[1]

In late February 2008, the victim’s families, concerned about the impartiality and transparency crash investigation, created a website and on-line petition called calling for a proper investigation into the root causes of the crash.[26] The commercial aviation community responded with evidence, and the website soon became a repository of false statements and evidence of corruption within the airline, including

  • Approved One-Two-GO re-currency check-rides *approved* by a chief pilot who was out of the country for the month
  • The true daily work rosters August 2007 – September 16 for the One-Two-GO pilots showing
  • An email from the One-Two-GO and Orient Thai’s flight scheduler to COO Cho Tsing Tsang, and CEO Udom Tantiprasongchai detailing the roster fraud provided to crash investigators and suggesting log book alterations to cover up the illegal flight of OG269.

Family members provided this material to the NTSB. As requested by the Thai Government, the NTSB ghost-wrote the crash report for the Thai authorities who thanked the NTSB for their assistance.[1]


After completing the inspection of the aircraft, the NTSB found it to have functioned properly and to have remained fully controllable until impact.[1] The cause of the crash was found to be due to a combination of human performance and operational issues, including: Human Performance[1]:

  • CRM issues, including attempted transfer of control of the aircraft at a critical moment
  • Failure of either pilot to apply power while attempting to regain altitude
  • Fatigue issues as both pilots had worked illegally excessive hours for the week and the month


  • Lack of governance in the corporate culture at One-Two-GO airlines
  • Failure of One-Two-Go to complete pilot proficiency checks as required by law
  • Training on a simulator that did not include wind shear alerting and did not match the configuration of One-Two-GO’s MD-82s.

The NTSB noted that

"although the weather deteriorated in the later stages of this flight, wind shear was not a factor in this accident” and “It is understood that during the accident sequence, the pilots were potentially distracted by the weather conditions; however, that distraction should not cause a loss of control of the airplane."[1]

Runway discrepancy

According to ICAO standards, the runway at an international airport must be at least 150 meters wide, clear of non-frangibles, with deviation permissible when there are physical barriers and the deviation is documented in the Aeronautical Information Publication used by pilots when landing at an airport. There is a discrepancy between the NTSB and Thai authorities relating to the width of runway 27. The NTSB measured the runway 27 to be 45 meters wide free of obstructions due to the location of the non-frangible embankment running along the runway. Thai DCAT claims that the runway is 75 meters wide free of obstructions. Thai DCAT do not plan to amend the AIP of Thailand.[1][2]


July 28, 2008, after the internet publication of illegally excessive work hours and check fraud, Thai DCAT censored Orient Thai Airlines and One-Two-Go airlines over a number of issues [27], including:

  • Failure to have safety and oversight programs to ensure pilots were properly trained and certified
  • Failure to have a system and oversight over a system to ensure pilots met and did not exceed duty time limitations
  • Committing offense and breaking the law by submitting deceptive check ride reports by MD-80 pilots

The Air Operator's Certificate of One-Two-GO Airlines was revoked, grounding the airline for 5 months.[27]

In April 2009, One-Two-GO Airlines was added to the EU blacklist [28]. It was removed shortly thereafter[29]. In September 2010, the One-Two-GO brand was dropped and the airline was merged into Orient Thai Airlines.[29]

October 2009, the NTSB crash report was made published. Once the Thai crash report was complete, the British government began its inquest process into the deaths of the 8 British citizens killed. The inquest, held March 22-23 2011, was presided over by H.M. coroner, S.P.G. Fisher. Coroner Fisher relied on a British aviation investigator, the NTSB and Thai reports, and victim and family statements to make his conclusions [7]. Fisher twice contacted the airline to send a representative to the hearing. The airline responded that they would not take part in the proceedings.[7] Finding that the crash of OG269 fit a finding of neither an Manslaughter nor murder, Coroner Fisher provided a narrative verdict to the court. He said [2]:

"There is no question in my mind that the catalog of systemic failures … contributed in no small part to the horrific consequences of the air crash on 16 September 2007."

"The evidence highlights systemic failures and a highly deficient safety culture at both [One-Two-Go Airlines and Orient Thai Airlines] airlines."

"[T]he Company falsified records in a clear attempt to mislead the Authorities who were investigating the circumstances surrounding this tragic air crash."

"[I]f I had powers to enforce the attendance of those two Chief Executive Officers [Udom Tantiprasongchai] I would have summonsed them to give evidence and account to you the families for the lack of safety culture that prevailed at One-Two-Go."

Fisher communicated his concerns for future travelers’ safety on Orient Thai and One-Two-Go Airlines via letters to the European Commission (EC) for Air Safety, the British Secretary for Transport and the Associate of British Travelers (ABT).[7]

See also


  1. ^ a b c d e f g h i j k National Transportation Safety Board (2009). "One-Two-Go Airlines Flight OG269, HS-OMG September 16, 2007, Phuket, Thailand" (PDF). NTSB/DCA07RA063: p.1,p.2. Retrieved July 14, 2011. 
  2. ^ a b c d e f g h i j k l m Ministry of Transport, Thailand (2009) (PDF). One-Two-Go Airlines Company Limited McDonnell Douglas DC-9-82 (MD-82) HS-OMG url= 
  3. ^ a b c Australian Channel 9 (2007). "Cut Price Safety url=" (mp4). 
  4. ^ National Transportation Safety Board (2009). "One-Two-Go Airlines Flight OG269, HS-OMG September 16, 2007, Phuket, Thailand" (PDF). NTSB/DCA07RA063: Appendix D. Retrieved July 14, 2011. 
  5. ^ "Deceased v. One-Two-GO Airlines, Orient Thai Airlines" (pdf). US District Court Southern District of Florida Miami Division 08-22558-CIV-MOORE/SIMONTON: p.57. 2008. Retrieved July 14, 2011. 
  6. ^ Heidi Blake (2011). "Thai airline 'covered up failings behind crash which killed 90' url=" (html). The Telegraph. 
  7. ^ a b c d e SPG Fisher HM Coroner (2011) (pdf). HM Coroner's Summary into the 8 Inquests of an Air Accident that Occurred on the One-Two-GO Airlines. Retrieved July 14, 2011. 
  8. ^ "[1]." EU Bans Thai, Ukraine, Kazakhstan, Benin Airlines From EU.
  9. ^ " Census info for HS-OMG". Retrieved 2007-09-17. 
  10. ^ a b "Category 7". ICAO Aerodrome Standards. 2007. 
  11. ^ "Investigators probe Phuket air disaster". Channel Newsasia. 2007-09-17. Retrieved 2007-09-17. 
  12. ^ "'People burning all around me', says Thai air crash survivor". Channel Newsasia. 2007-09-17. Retrieved 2007-09-17. 
  13. ^ "21 foreign victims of Phuket air crash identified: police". Channel Newsasia. 2007-09-18. Retrieved 2007-09-18. 
  14. ^ "Thai airport wind alert 'faulty'". BBC. 2007-09-18. Retrieved 2007-09-19. 
  15. ^ "Wind detection systems down during deadly Thai crash". Canadian Broadcasting Corporation. 2007-09-18. Retrieved 2007-09-23. 
  16. ^ "Vancouver woman confirmed dead in Thai plane crash". Canadian Broadcasting Corporation. 2007-09-23. Retrieved 2007-09-29. 
  17. ^ "Seventh Phuket crash victim identified". The Jerusalem Post. 2007-09-19. Retrieved 2007-09-20. 
  18. ^ "Survivors recount Thai jet crash". CNN. 2007-09-18. Retrieved 2007-09-27. 
  19. ^ a b "88 killed in Thai plane crash". CNN. 2007-09-16. Archived from the original on 2008-01-01. Retrieved 2007-09-16. 
  20. ^ "Thai crash officials probe system problem, foul weather". Channel Newsasia. 2007-09-19. Retrieved 2007-09-20. 
  21. ^ a b "Thai plane dead may take weeks to identify: police". Channel NewsAsia. 2007-09-20. Retrieved 2007-09-20. 
  22. ^ "88 die as Thai budget airliner packed with foreign tourists crashes in Phuket". Canadian Press. 2007-09-16. Retrieved 2007-09-16. 
  23. ^ "B.C. woman escaped through window of burning plane". Canadian Broadcasting Corporation. 2007-09-16. Retrieved 2007-09-16. 
  24. ^ "A very telling letter ...". pprune. 2007-09-18. Retrieved 2011-07-23. 
  25. ^ "Matters of the Facts regarding Suspension of Air Operator Certificate of Orient Thai Airlines Co., Ltd. and One Two Go Airline Co., Ltd". Department of Civil Aviation News. 2008-07-28. Retrieved 2011-07-23. 
  26. ^ "Families Blame Lax Safety for Budget Airline Crash". The Sunday Times. 2008-07-20. Retrieved 2011-07-23. 
  27. ^ a b "Matters of the Facts regarding Suspension of Air Operator Certificate of Orient Thai Airlines Co., Ltd. and One Two Go Airline Co., Ltd". Department of Civil Aviation News. 2008-07-28. Retrieved 2011-07-23. 
  28. ^ "Families Blame Lax Safety for Budget Airline Crash". The Sunday Times. 2008-07-20. Retrieved 2011-07-23. 
  29. ^ a b "One-Two-GO flies into History". The Bangkok Post. 2010-09-15. Retrieved 2011-07-23. 

External links

External images
Photos of HS-OMG before accident]

Wikimedia Foundation. 2010.

Игры ⚽ Нужен реферат?

Look at other dictionaries:

  • One-Two-GO Airlines — วัน ทู โก แอร์ไลน์ IATA OG ICAO OTG Callsign …   Wikipedia

  • One-Two-GO — One Two Go …   Deutsch Wikipedia

  • One-Two-Go — One Two Go …   Deutsch Wikipedia

  • China Airlines Flight 120 — Burnt out wreckage of Flight 120 at Naha Airport. Accident summary Date …   Wikipedia

  • Southwest Airlines Flight 1248 — Infobox Airliner accident|name=Southwest Airlines Flight 1248 caption = Southwest Airlines Flight 1248, at an intersection just outside Midway International Airport Date=December 8 2005 Type=Runway overrun in snowstorm Site=Chicago Midway… …   Wikipedia

  • Adam Air Flight 574 — Flight Route Accident summary Date 1 January 2007 …   Wikipedia

  • Orient Thai Airlines — โอเรียนท์ ไทย แอร์ไลน์ IATA OX ICAO OEA Callsign …   Wikipedia

  • Garuda Indonesia Flight 200 — Accident summary Date March 7, 2007 (2007 03 07) Type Runway overshoot, Pilot error …   Wikipedia

  • Air West Flight 612 — A Boeing 737, similar to the aircraft involved in the hijacking Hijacking summary Date …   Wikipedia

  • Southwest-Airlines-Flug 1248 — Southwest Airlines Flug 1248 …   Deutsch Wikipedia

Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”