XiamenAir Flight 8667
Boeing 737-85C (WL) · Runway excursion due to pilot error
From Xiamen Gaoqi International Airport (XMN) to Ninoy Aquino International Airport (MNL)
Event
- NTSB case
- DCA18WA268
- 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
- Unknown · led by another country; figures from NTSB notifications
- Event fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 165
- Survivors
- 165
- 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
- 0 serious · 0 minor (NTSB)
- 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-85C (WL)
- Flight
- MF8667
- Aircraft type
- Boeing 737
- Category
- Airplane
- 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
- B-5498
- Operator
- XiamenAir
- Onboard fatalities
- 0
- Route
- From Xiamen Gaoqi International Airport (XMN)To Ninoy Aquino International Airport (MNL)
- 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
- Minor
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Miscellaneous
- Organizational issues › Management
- Environmental issues › Physical environment
From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
XiamenAir Flight 8667 was a scheduled international passenger flight from Xiamen Gaoqi International Airport in Xiamen, China, to Ninoy Aquino International Airport in Manila, Philippines. On August 16, 2018, the Boeing 737-800 operating this flight skidded off the runway while attempting to land in poor weather conditions. After leaving the runway, the aircraft hit obstacles that tore off the left engine and the left main gear. The crash occurred at 11:55 p.m. Philippine Standard Time (UTC+8), and resulted in the destruction of the aircraft. No serious injuries were reported among the crew or passengers. The damaged aircraft took 36 hours to remove from the runway, leading to a major disruption at the airport, which is the primary international gateway to the Philippines. The closure caused the cancellation of more than 200 domestic and international flights, affected more than 250,000 travelers, and prompted calls for enlargement of the airport or the construction of alternative airports to serve the country in the event of future disruptions.
After the accident, the flight crew stated in interviews that a torrential downpour obstructed their view of the runway. The investigation revealed that despite the first officer of the aircraft calling for a go-around several times during the landing, the captain attempted to complete the landing despite not being able to clearly identify the runway. The investigation led to changes in airline policy relating to cockpit resource management, planning, and operations in poor weather conditions. It also led to runway improvements at the airport to remove runway obstructions that had caused most of the major damage experienced by the aircraft.
Accident
The aircraft, operating as flight number 8667, departed Xiamen, China, at 9:23 p.m. local time, bound for Manila, Philippines. MF 8667 was a regularly scheduled flight that operated daily flights between the two cities.
Upon arrival in the Manila airspace, the aircraft circled the area waiting for a break in the thunderstorms in the area. At 11:40 p.m., the pilots attempted to land, when the aircraft was 30 ft above the ground, the pilots aborted the attempt because they did not have a clear view of the ground and surrounding area. After a discussion, the pilots decided to make one more landing attempt, and then planned to divert to their planned alternate airport if they had to abort during the second approach.
On the second attempt, the pilots were able to establish a stabilized approach to the runway with the landing gear lowered, flaps at 30 degrees, and the speed brake in the armed position. The aircraft stayed on its targeted course along the glide slope down to 50 ft. As the plane passed over the runway threshold, it began to veer to the left of center of the runway. The high intensity centerline runway lights on the runway had been out of service since August 8 due to scheduled runway refurbishment. The first officer called out "go-around", but the captain answered, "No". At 13 ft above the ground, the aircraft was rolling to the left and drifting to the left of the runway center line. The first officer made another call for a go-around, but the captain again responded, "No" and "It's Okay".
The aircraft touched down on Runway 24 almost on both main gears, to the left of the runway center line, 741 m from the threshold of the runway. After touching down, the speed brakes and the autobrakes deployed, but the autobrakes disengaged shortly after due to an unknown cause. Initial witnesses reported that the aircraft appeared to bounce during the landing, before veering off to the left. The plane left the left edge of the runway, and it collided with several concrete electric junction boxes that were located in the grassy area beside the runway, causing the left main gear and the left engine to be torn off of the aircraft. As the aircraft continued into the soft grassy ground to the side of the runway, the right main landing gear and the nose gear collapsed and were folded into the gear wheel wells.
The aircraft came to a complete stop 80 m to the left of the center of the runway, about 1500 m down the runway from the threshold, at about 11:55 p.m. Philippine Standard Time (UTC+08:00). The collapse of the nose wheel caused the aircraft's internal and external communication systems to fail, so the first officer left the cockpit to announce the emergency evacuation. The cabin crew conducted the evacuation of the aircraft using emergency slides on the left and right front doors. All passengers and crew were able to evacuate the aircraft with no major injuries, and only a few reporting superficial scratches.
Investigation and cause
Investigation
CAPP officials began the investigation of the accident shortly after the accident. Investigators retrieved the aircraft's flight data recorder and cockpit voice recorder and interviewed the flight crew. By August 24, the two recorders had been taken to Singapore to have them decoded to attempt to determine the cause of the accident. By August 31, investigators in Manila had received voice transcripts and data readouts from the recorders. They announced that they expected a final report on the accident to be released soon. In October, CAAP officials stated that they expected to have a final report by November.
On August 19, Senator Grace Poe called for the Senate to investigate the aftermath of the accident to determine whether the airport was prepared for such an emergency and to get an explanation of why it took 36 hours to remove the disabled aircraft. She also said she was concerned about the crowded conditions in the airport terminals and how passengers were forced to endure significant delays without the airlines offering enough water and meals. During hearings on August 29, authorities identified several lapses in the airport's response, including delays in obtaining high-capacity cranes, failing to provide meals to stranded passengers, and a lack of training to prepare for this type of incident.
In an undated executive summary of the accident investigation released to the public on August 8, 2019, CAAP concluded that the accident was caused by the decision of the captain to proceed with the landing of an un-stabilized approach with insufficient visual reference. It also found that the captain did not apply sound crew resource management practices when he disregarded the first officer's call for a go-around. The investigation found that factors contributing to the accident included the crew's failure to discuss strategies for dealing with inclement weather, crosswind conditions, the possibility of low-level wind shear, and NOTAM information on runway lights that were out of service. It found that the airline policy was inadequate on the procedure of go-arounds and found design and construction violations on the runway that left uneven surfaces and concrete obstacles. CAAP made recommendations for the XiamenAir to strengthen company policies of actions that must be taken by a pilot once a call out of "Go-Around" is made by the pilot monitoring, including establishing no fault "Go-Around" policies and ensuring that crews receive sufficient training on the policies. The report also recommended that the airport review and update its disabled aircraft removal plan and ensure that its equipment is sufficient for current operations at the airport.
Text from the Wikipedia article “XiamenAir Flight 8667” (revision 1373743869, 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
NTSB narrative
The CAA of the Philippines has notified the NTSB of an incident involving a Boeing 737 airplane that occurred on August 16, 2018. The NTSB has appointed a U.S. Accredited Representative to assist the CAA's investigation under the provisions of ICAO Annex 13 as State of Manufacture of the airplane.All investigative information will be released by the CAA of the Philippines.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
Wikipedia article: XiamenAir Flight 8667
- Article
- XiamenAir Flight 8667
- Revision
- 1373743869 · 2026-09-07 · retrieved 2026-09-18
- Wikidata
- Q56278825
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA18WA268
- Event ID
- 20180816X71632
- Case number
- DCA18WA268
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "XiamenAir Flight 8667" (page 58175893, revision 1373743869); merged with NTSB case DCA18WA268 (events / aircraft)
- Date
- Wikipedia infobox: date
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia: Wikipedia article coordinates
- 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 DCA18WA268
- Operation
- airline flight number in the infobox
- Fatalities
- Wikipedia: Wikipedia infobox: aircraft fatalities
- Ground fatalities
- Wikipedia: not stated in the Wikipedia infobox
- Summary
- Wikipedia infobox: summary
Source notes (2)
- One occurrence in two sources, merged: the Wikipedia article "XiamenAir Flight 8667" and NTSB case DCA18WA268, 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.