Jeju Air Flight 2216
Boeing 737-8AS · Accident
From Suvarnabhumi Airport (BKK) to Muan International Airport (MWX)
Event
- NTSB case
- DCA25WA072
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Preliminary · ARAIB preliminary report, 27 Jan 2025
- Event fatalities
- 179 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 181
- Survivors
- 2
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 2
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Not recorded
Boeing 737-8AS
- Flight
- 7C2216
- Aircraft type
- Boeing 737
- Category
- Airplane · from aircraft type
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- HL8088
- Operator
- Jeju Air
- Onboard fatalities
- 179
- Route
- From Suvarnabhumi Airport (BKK)To Muan International Airport (MWX)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Non-U.S., Commercial
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
Jeju Air Flight 2216 was a scheduled international passenger flight operated by Jeju Air from Suvarnabhumi Airport near Bangkok, Thailand, to Muan International Airport in Muan County, South Korea. On 29 December 2024, when the Boeing 737-800 operating the flight was approaching Muan, a bird strike occurred, with both of the engines ingesting birds, causing an apparent loss of thrust in the right engine. The pilots issued a mayday alert, performed a go-around, and on the second landing attempt, the landing gear did not deploy and the airplane belly-landed well beyond the normal touchdown zone. It overran the runway at high speed, collided with the approach lighting system, and crashed into a berm encasing a concrete structure that supported an antenna array for the instrument landing system (ILS). The collision killed all 175 passengers and 4 of the 6 crew members. The surviving two cabin crew were seated in the rear of the plane, which detached from the fuselage, and were rescued with injuries.
Both the cockpit voice recorder (CVR) and flight data recorder (FDR) stopped functioning a few seconds before the mayday call, and evidence of a bird strike with a species of migratory duck was later found in both engines, with the right engine having sustained severe bird damage. In July 2025, South Korean media reported that the investigation board found that the crew mistakenly turned off the relatively unscathed left engine rather than the badly damaged right engine. In January 2026, it was revealed that researchers had concluded that the passengers would have survived if the ILS antenna array and its support had been constructed in accordance with international safety guidelines.
The crash was the deadliest aviation disaster involving a South Korean airliner since the 1997 crash of Korean Air Flight 801 in Guam and also the deadliest in South Korea, surpassing the 2002 crash of Air China Flight 129 that killed 129 people. This was also the first fatal accident in Jeju Air's 19-year history and was the deadliest aviation accident since the 2018 crash of Lion Air Flight 610.
Accident
On 29 December, the aircraft took off from Suvarnabhumi Airport at 2:28 a.m ICT (UTC+7). Kerati Kijmanawat, the director of Airports of Thailand, stated that no abnormalities regarding the aircraft nor the runway had been reported.
At 8:54 a.m. KST (UTC+9), the plane was authorized to land at Muan International Airport on runway 01. As the plane was preparing to land, it was warned at 8:57 a.m. about the potential for a bird strike. At 8:58:56 a.m., the pilots broadcast a mayday alert and advised they were going around. This was followed by a request at 9:00 a.m. to land in the opposite runway, runway 19, after the landing gear was not deployed. This request was authorized at 9:01 a.m.
The crash occurred at 9:03 a.m. as the aircraft belly landed, touching down 1,200 m along the runway.
It overshot, with video footage showing the aircraft sliding down the runway on the engine nacelles with a sustained nose-high attitude. It continued 250 m past the runway threshold and exploded after colliding with the berm supporting the instrument landing system localizer. Both engines were embedded into the berm structure while the tail assembly continued forward, rolling over and resting inverted. Wreckage from the forward fuselage was found 20 to 300 m past the berm, and partially damaged the perimeter wall.
Local residents said they saw flames and sparks originating from the aircraft's right wing and heard explosions and "metal scraping" before impact. Some reported seeing a flock of birds being ingested into the right engine, causing a fire. The only survivors were two crew members rescued from the tail section of the aircraft. A local restaurant owner heard "loud bangs" that sounded like the backfiring of a motorcycle engine, leading him to rush to the restaurant rooftop and record a 54-second video on his cell phone of the aircraft's descent and crash which subsequently went viral.
Emergency services received multiple calls around 9:03 a.m., and the fire response issued a level-3 emergency, its highest alert. According to the National Fire Agency and the Ministry of National Defense, 1,562 personnel, including 490 firefighters, 500 military personnel and 455 police officers, were dispatched. One of the survivors was rescued at 9:23 a.m., and the other was rescued from the tail section at 9:50 a.m. The fire was extinguished within 43 minutes of the crash, and the flight recorders were retrieved within the day. The flight data recorder (FDR) was found partially damaged without a connector linking its data storage unit to the power supply, while the cockpit voice recorder (CVR) was intact.
The two flight attendants seated in the aft jump seats were the only survivors of the crash and remained conscious during the crash. Hydraulic equipment was used to rescue one of the survivors, who had been pinned down by a fallen cabinet. They both sustained moderate to serious wounds, one with fractures to his ribs, shoulder blade and upper spine, and the other with injuries to her ankle and head. Both received medical treatment at separate hospitals in Mokpo before being transferred to a hospital in Seoul. Both survivors appeared to be disoriented and were unable to remember what had happened immediately following the landing.
By 1:36 p.m., the firefighters had switched to search operations to recover bodies. A temporary morgue was set up in an airport hangar to handle the bodies recovered from the wreckage, and a waiting room was created for family members of the occupants at the airport with civil servants assigned to each family for support while they awaited news from the crash. Tents were also erected inside the airport to temporarily house arriving family members. Later at night, the family members were temporarily accommodated at the dormitories of Mokpo National University.
Regular operations of Muan International Airport were suspended. At the time of the crash, ongoing construction work had shortened the runway's length from 2800 to 2500 m; officials from the Ministry of Land, Infrastructure and Transport dismissed the possibility of the relatively short runway length having contributed to the accident. The airport's sole runway is expected to remain closed to commercial traffic until 1 January 2026. Emergency and training flights resumed at the airport on 24 February 2025.
Investigation and cause
Investigation
The crash is currently being investigated by the South Korean Aviation and Railway Accident Investigation Board (ARAIB), with assistance from the US National Transportation Safety Board (NTSB), Federal Aviation Administration (FAA) and Boeing. Eight investigators arrived at the crash site on 31 December. GE Aerospace, which co-manufactured the engines on the plane in its CFM International joint venture, joined the investigation.
At a press conference on the day of the accident, Muan County fire chief Lee Jeong-hyun said that the cause of the landing gear failure was presumed to have been adverse weather combined with a bird strike; the weather around the airport at the time of the crash was favorable with almost no wind, rain or clouds, and visibility was 9 km.
Both flight recorders, the cockpit voice recorder (CVR) and the flight data recorder (FDR), were recovered and taken to Gimpo International Airport for analysis. On 11 January, the ARAIB stated that both the CVR and FDR had stopped recording four minutes before the aircraft crashed. Investigators say the cutoff may have resulted from loss of all electrical power, including backup.
By 1 January 2025, initial CVR data had been extracted and the CVR transcript was created on 4 January. The damaged flight data recorder was sent to Washington, DC, United States, for analysis on 6 January. A preliminary report was released on 27 January.
On 7 January, the director of the ARAIB resigned. The Transport Ministry's head of aviation policy was removed from the board's investigation and all of its activities.
On 8 January, the South Korean National Assembly passed a motion to set up a parliamentary committee, with two subcommittees (investigation and prevention, and families support and memorial projects) placed under the panel.
Text from the Wikipedia article “Jeju Air Flight 2216” (revision 1373716357, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
Sources
Wikipedia article: Jeju Air Flight 2216
- Article
- Jeju Air Flight 2216
- Revision
- 1373716357 · 2026-09-07 · retrieved 2026-09-18
- Wikidata
- Q131581945
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA25WA072
- Event ID
- 20241229199476
- Case number
- DCA25WA072
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "Jeju Air Flight 2216" (page 78748114, revision 1373716357); merged with NTSB case DCA25WA072 (events / aircraft)
- Date
- Wikipedia infobox: date; matches the Aviation and Railway Accident Investigation Board (ARAIB), Republic of Korea preliminary report
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia: Wikipedia article coordinates; matches the Aviation and Railway Accident Investigation Board (ARAIB), Republic of Korea preliminary report
- Aircraft, operator and route
- Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA25WA072
- Operation
- airline flight number in the infobox
- Fatalities
- Wikipedia: Wikipedia infobox: aircraft fatalities; matches the Aviation and Railway Accident Investigation Board (ARAIB), Republic of Korea preliminary report
- Ground fatalities
- Wikipedia: not stated in the Wikipedia infobox
- Summary
- Wikipedia infobox: summary
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "Jeju Air Flight 2216" and NTSB case DCA25WA072, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
- No bulk values were replaced by the NTSB case API.
- Checked against the Aviation and Railway Accident Investigation Board (ARAIB), Republic of Korea preliminary report (2025-01-27) on 2026-09-18. The report states the same date, crash-site coordinates, flight number, fatalities, registration, operator, departure, destination and damage. Not checked: place, aircraft type, type of operation and ground fatalities.