Boeing 737-800 incident near Tamuning, July 5, 2015
On July 5, 2015 at about 2:10 am local time, a Boeing 737-800, registered HL8224, suffered minor damage in an incident during landing (landing roll) near Tamuning. No one was hurt; 82 people were on board or involved.
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this incident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 5, 2015 · about 2:10 am local time
- Place
- Tamuning · map
- Type
- Incident
- Injuries
- No one was hurt; 82 people were on board or involved.
- Weather
- not recorded
- Aircraft
- Boeing 737-800 · all 737-800s on the register
- Registration
- HL8224 · no longer on the register
- Damage
- Minor damage
- Flight
- Flight
The NTSB's narrative preliminary · quoted from the NTSB record
On July 5, 2015, about 0210 local time, a Boeing 737-800, HL8224, Korean Airlines Flight 2115, had a runway excursion at A. B. Won Pat Guam International Airport. Tamuning, Guam. Korean Airlines was operating the airplane under the provisions of the Korean Civil Aviation Regulations. The 2 flight crew, 5 cabin crew, and 75 passengers were not injured; the airplane sustained minor damage. The international transport flight departed Busan, Korea. Instrument meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan had been filed.Preliminary information indicated that following an ILS approach, and after landing on runway 06R in heavy rain conditions, the airplane veered off the R/H side of the runway. The pilot corrected his trajectory, and returned the aircraft to the runway coming to a complete stop. He then asked that the aircraft be towed to the gate. Two runway edge lights, two taxiway lights, and a taxiway sign were damaged beyond repair by the impact with the aircraft. Under the provisions of ICAO Annex 13, the National Transportation Safety Board delegated authority of the incident to the Korean Aviation and Railway Accident Investigation Board (ARAIB), Republic of Korea. Further information can be obtained from: Aviation and Railway Accident Investigation Board (ARAIB) Ministry of Land, Infrastructure, and Transport Republic of Korea Phone +82-44-201-5438 Fax +82-44-201-5698 Web site www.araib.go.kr This report is for information purposes only, and contains only information obtained for, or released by, the Government of the Republic of Korea.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control on ground during landing (landing roll) defining event
The aircraft
- Landing gear: retractable
- Operator: Korean Airlines
The flight
- Departed from: HL82 Busan
- Destination: Barrigada
- Flight plan: IFR
Weather at the time
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 5 | |||
| Flight crew | 2 | |||
| Passengers | 75 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.