Country
code

Metro Manila

Crash of an IAI 1124A Westwind II in Manila: 8 killed

Date & Time: Mar 29, 2020 at 2000 LT
Type of aircraft:
Operator:
Registration:
RP-C5880
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Manila - Tokyo
MSN:
353
YOM:
1981
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
An IAI Westwind II 1124A type of aircraft with registry number RP-C5880, was destroyed following a runway excursion while taking-off at RWY 06, Ninoy Aquino International Airport (NAIA), Manila Philippines. All eight (8) occupants (six (6) Filipino, one (1) Canadian and one (1) American citizen are fatally injured. The aircraft is being operated by Lionair Inc. and was bound for Haneda, Japan on a medical evacuation flight. While the aircraft was on take-off roll before reaching taxiway R2, sparks were noted at the runway, it continued until the aircraft came to complete stop and engulfed by fire. Chunks of rubber and metal debris were present on the runway. Scrape marks coming from the right hand (RH) wheel hub were also visible. Tire marks followed by scrape marks on the runway coming from the LH tire and wheel hub were also seen after taxiway H1 intersection. Large portion of the remaining LH tire was recovered from the grassy portion near taxiway H1. After exiting from the asphalted portion of runway safety area, the aircraft initially run over two (2) runway edge lights then impacted into a concrete electric junction box and came to a complete stop at the runway secondary fence. The aircraft settled almost 172 meters away from the end of RWY 06, in an upright position at 14°30'53.50"N; 121°1'48.48"E and heading of 170 degrees. The flight was on Instrument Flight Rules (IFR) condition. A Notice to Airmen (NOTAM) of NAIA RWY 06/24 closure for aircraft operation was declared at 2000H and opened for operation at 0420H, March 30, 2020.
Probable cause:
The accident was the caused by the combination of the decision of the PF to abort the take-off after VR that resulted to runway excursion and incorrect pilot techniques or procedures in the high-speed rejected take-off.
The following contributing factors were identified:
- Operational pressures related to the delay of schedule due to late filing of the flight plan compelling the crew to rush and meet the schedule demand.
- The crew's complacency by skipping required briefing item in the before take-off checklist, in this case, the considerations in the event of a malfunction before/after V1.
Final Report:

Crash of a Boeing 737-85C in Manila

Date & Time: Aug 16, 2018 at 2355 LT
Type of aircraft:
Operator:
Registration:
B-5498
Survivors:
Yes
Schedule:
Xiamen – Manila
MSN:
37574/3160
YOM:
2010
Flight number:
MF8667
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
157
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On August 16, 2018, about 1555UTC/2355H local time, a Boeing 737-800 type of aircraft with Registry No. B-5498 operating as flight CXA 8667 sustained substantial damage following a runway excursion after second approach while landing on Runway 24 of Ninoy Aquino International Airport (NAIA), Manila, Philippines. The flight was a scheduled commercial passenger from Xiamen, China and operated by Xiamen Airlines. The one hundred fifty-seven (157) passengers and two (2) pilots together with the five (5) cabin crew and one air security officer did not sustain any injuries while the aircraft was substantially damaged. An instrument flight rules flight plan was filed. Instrument Meteorological Conditions (IMC) prevailed at the time of the accident. During the first approach, the Captain who was the pilot flying aborted the landing at 30 feet Radio Altitude (RA) due to insufficient visual reference. A second approach was considered and carried out after briefing the First Officer (FO) of the possibility of another aborted landing should the flight encounter similar conditions. The briefing included a diversion to their planned alternate airfield. The flight was “stabilized” on the second approach with flaps set at 30 degrees landing position, all landing gears extended and speed brake lever appropriately set in the ARM position. On passing 1,002 feet Radio Altitude (RA), the autopilot was disengaged; followed by the disengagement of the auto-throttle, three (3) seconds later. The ILS localizer lateral path and Glide slope vertical path were accurately tracked and no deviations were recorded. The “reference” landing speed for flaps 30 for the expected aircraft gross weight at the time of landing was 145 knots and a target speed of 150 knots was set on the Mode Control Panel (MCP). The vertical descent rate recorded during the approach was commensurate with the recommended descent rate for the profile angle and ground speed; and was maintained throughout the approach passing through the Decision Altitude (DA) of 375 feet down to 50 feet radio altitude (RA). As the aircraft passed over the threshold, the localizer deviation was established around zero dot but indicated the airplane began to drift to the left of the centerline followed by the First Officer (FO) making a call out of “Go-Around” but was answered by the Captain “No”. The throttle levers for both engines were started to be reduced to idle position at 30 feet RA and became fully idle while passing five (5) feet RA. At this point, the aircraft was in de-crab position prior to flare. At 13 feet RA, the aircraft was rolling left and continuously drifting left of the runway center line. At 10 feet RA another call for go-around was made by the FO but was again answered by the Captain with “No” and “It’s Okay”. At this point, computed airspeed was approximately 6 knots above MCP selected speed and RA was approaching zero feet. Just prior to touchdown, computed airspeed decreased by 4 knots and the airplane touched down at 151 knots (VREF+6). The wind was recorded at 274.7 degrees at 8.5 knots. Data from the aircraft’s flight data recorder showed that the aircraft touched down almost on both main gears, to the left of the runway centerline, about 741 meters from the threshold of runway 24. Deployment of the speed brakes was recorded and auto brakes engagement was also recorded. The auto brakes subsequently disengaged but the cause was undetermined. Upon touchdown, the aircraft continued on its left-wards trajectory while the aircraft heading was held almost constant at 241 degrees. After the aircraft departed the left edge of the runway, all landing gears collided with several concrete electric junction boxes that were erected parallel outside the confines of the runway pavement. The aircraft was travelling at about 147 knots as it exited the paved surface of the runway and came to rest at approximately 1,500 meters from the threshold of Runway 24, with a geographical position of 14°30’23.7” N; 121°0’59.1” E and a heading of 120 degrees. Throughout the above sequence of events from touchdown until the aircraft came to a full stop, the CVR recorded 2 more calls of “GO-AROUND” made by the FO. Throughout the landing sequence, the thrust reversers for both engines were not deployed. Throttle Lever Position (TLP) were recorded and there was no evidence of reverse thrust being selected or deployment of reversers. After the aircraft came to a complete stop, the pilots carried out all memory items and the refence items in the evacuation non-normal checklist, which includes extending the flaps to a 40 degrees position. The aircraft suffered total loss of communication and a failure in passenger address system possibly due to the damage caused by the nose gear collapsing rearwards and damaging the equipment in the E/E compartment or the E-buss wires connecting the Very High Frequency (VHF) 1 radio directly to the battery was broken. The Captain then directed the FO to go out of the cockpit to announce the emergency evacuation. The cabin crew started the evacuation of the passengers utilizing the emergency slides of the left and right forward doors. There were no reported injuries sustained by the passengers, cabin crew, flight crew or the security officer.
Probable cause:
Primary causal factors:
a. The decision of the Captain to continue the landing on un-stabilized approach and insufficient visual reference.
- The Captain failed to maintain a stabilized landing approach moments before touchdown, the aircraft was rolling left and continuously drifting left of the runway centerline.
- The Captain failed to identify correctly the aircraft position and status due to insufficient visual reference caused by precipitation.
b. The Captain failed to apply sound CRM practices.
- The Captain did not heed to the First Officer call for a Go-Around.
Contributory factors:
a. Failure to apply appropriate TEM strategies. Failure of the Flight Crew to discuss and apply appropriate Threat and Error Management (TEM) strategies for the following:
- Inclement weather.
- Cross wind conditions during approach to land.
- Possibility of low-level wind shear.
- NOTAM information on unserviceable runway lights.
b. Inadequate Company Policy on Go-Around:
- Company’s Standard Operation Procedures were less than adequate in terms of providing guidance to the flight crew for call out of "Go-Around" during landing phase of the flight.
c. Runway strip inconsistent with CAAP MOS for Aerodrome and ICAO Annex 14:
- The uneven surface and concrete obstacles contributed to the damage sustained by the aircraft.
Final Report:

Crash of a Beechcraft 65-80 Queen Air in Manila: 13 killed

Date & Time: Dec 10, 2011 at 1415 LT
Type of aircraft:
Registration:
RP-C824
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Manila - San Jose
MSN:
LD-21
YOM:
1962
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
13
Circumstances:
On December 10, 2011, BE-65-80QA (Queen Air) with Registry RP-C824 took off from RWY 13, Manila Domestic Airport on/or about 0610 UTC (1410H) southbound for San Jose, Mindoro. There were three (3) persons on board, the PIC and two (2) other persons; one was seated at the right-hand cockpit seat and the other one at the passenger seat. After airborne, the ATC gave instructions to the pilot o turn right and report five (5) miles out. After performing the right turn, the pilot requested for a reland which was duly acknowledged but the ATC with instructions to cross behind traffic on short final Rwy 06 (a perpendicular international runway) and to confirm if experiencing difficulty. However, there was no more response from the pilot. From a level flight southward at about 200 feet AGL, three (3) loud sputtering/burst sounds coming from the aircraft were heard (by people on the ground) then the aircraft was observed making a left turn that progressed into a steep bank and roll-over on a dive. After about one complete roll on a dive the aircraft hit ground at point of impact (Coordinates 14.48848 N 121.025811 E), a confined area beside a creek surrounded by shaties where several people were in a huddle. Upon impact, the aircraft exploded and fire immediately spread to surrounding shanties and a nearby elementary school building. The aircraft was almost burned into ashes and several shanties were severely burned by post-crash fire. A total of thirteen (13) persons were fatality injured composed of: the 3 aircraft occupants who died due to non survivable impact and charred by post-crash fire, and ten (10) other persons on the ground, all residents at vicinity of impact point, incurred non-fatal injuries and were rushed to a nearby hospital for medical treatment. About 20 houses near the impact point were completely burnt and the adjacent Elementary School building was severely affected by fire.
Probable cause:
The Aircraft Accident Investigation and Inquiry Board determined that the probable cause of this accident was:
- Immediate Cause:
(1) Pilot’s Lack of event proficiency in emergency procedures for one (1) engine in-operative condition after-off. Pilot Error (Human Factor)
While a one engine in-operative condition during take-off after V1 is a survivable emergency event during training, the pilot failed to effectively maintain aircraft control the aircraft due to inadequate event proficiency.
- Contributing Cause:
(1) Left engine failure during take-off after V1. (Material Factor)
The left engine failed due to oil starvation as indicated by the severely burnt item 7 crankshaft assembly and frozen connecting rods 5 & 6. This triggered the series of events that led to the failure of the pilot to manage a supposedly survivable emergency event.
- Underlying Causes:
(1) Inadequate Pilot Training for Emergency Procedure. Human Factor
Emergency event such as this (one engine inoperative event – twin engine aircraft) was not actually or properly performed (discussed only) in actual training flights/check-ride and neither provided with corresponding psycho-motor training on a simulator. Hence, pilot’s motor skill/judgment recall was not effective (not free-flowing) during actual emergency event.
(2) Inadequate engine overhaul capability of AMO. Human Factor
There was no document to prove that engine parts scheduled to be overhauled aboard were complied with or included in the overhaul activity. The presence unauthorized welding spot in the left-hand engine per teardown inspection report manifested substandard overhaul activity.
(3) Inadequate regulatory oversight (airworthiness inspection) on the overhaul activity of the AMO (on engine overhaul). Human Factor
The airworthiness inspection on this major maintenance activity (engine overhaul) failed to ensure integrity and quality of replacement parts and work done (presence of welding spots).
(4) Unnecessary Deviation by ATC from the AIP provision on Runway 13 Standard VFR Departure Southbound.
The initiative of the AY+TC for an early right turn southbound after airborne was not in accord with the standard departure in the AIP which provides the safest corridor for takeoff and the ample time to stabilize aircraft parameters in case of a one engine inoperative emergency event for a successful re-land or controlled emergency landing.
Final Report:

Crash of an ATR72-212A in Manila

Date & Time: Jul 28, 2010 at 1515 LT
Type of aircraft:
Operator:
Registration:
RP-C7254
Survivors:
Yes
Schedule:
Tuguegarao – Manila
MSN:
828
YOM:
2008
Flight number:
5J509
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Cebu Pacific Air flight 5J509, an ATR 72-500, took off from Tuguegarao Airport, Philippines, bound for Manila-Ninoy Aquino International Airport. The first officer was the Pilot Flying (PF) while the captain was the Pilot Not Flying (PNF). Approaching Manila, the flight was under radar vector for a VOR/DME approach to runway 24. At 7 miles on finals the approach was stabilized. A sudden tailwind was experienced by the crew at 500 feet radio altitude (RA) which resulted in an increase in airspeed and vertical speed. The captain took over the controls and continued the approach. Suddenly, the visibility went to zero and consequently the aircraft experienced a bounced landing three times, before a go-around was initiated. During climb out the crew noticed cockpit instruments were affected including both transponders and landing gears. They requested for a priority landing and were vectored and cleared to land on runway 13. After landing the aircraft was taxied to F4 where normal deplaning was carried out. No injuries were reported on the crew and passengers.
Probable cause:
Primary Cause Factor:
- Failure of the flight crew to discontinue the approach when deteriorating weather and their associated hazards to flight operations had moved into the airport (Human Factor)
Contributory Factor:
- The adverse weather condition affected the judgment and decision-making of the PIC even prior to the approach to land. With poor weather conditions being encountered, the PIC still continued the approach and landing. (Environmental Factor)
Underlying Factor:
- As a result of the bounced landing, several cockpit instruments were affected including both transponders on board. One of the nosewheels was detached and all the landing gears could not be retracted. Further, the integrity of the structure may have been affected and chance airframe failure was imminent. With all of these conditions, the Captain still opted to request for a priority landing when emergency landing was needed.

Crash of a Douglas DC-3C in Manila: 4 killed

Date & Time: Oct 17, 2009 at 1214 LT
Type of aircraft:
Registration:
RP-C550
Flight Type:
Survivors:
No
Site:
Schedule:
Manila - Puerto Princesa
MSN:
14292/25737
YOM:
1944
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
On October 17, 2009at about 12:04 pm, RP-C550 a DC-3type of aircraft took off from Manila Domestic airport bound for Puerto Princesa, Palawan. Approximately 5 mins after airborne, the Pilot-in-Command (PIC) informed Manila Tower that they were turning back due to technical problem. The PIC was asked by the air controller whether he was declaring an “emergency” and the response was negative. The PIC was directed to proceed South Mall and wait for further instruction (a standard procedures for VFR arrivals for runway 13). At South Mall, RP-C550 was cleared to cross the end of runway 06, still without declaring an emergency. The tower controller sensed that something was wrong with the aircraft due to its very low altitude, immediately granted clearance to land runway 06. However, the aircraft was not able to make it to runway 06. At about 12:14, RP-C550 crashed at an abandoned warehouse in Villa Fidela Subd., Brgy. Elias Aldana Las Piñas City about 4 kms. from the threshold of runway 06. As a result, the aircraft was totally destroyed and all aboard suffered fatal injuries due to impact and post crash fire.
Probable cause:
The Aircraft Accident Investigation and Inquiry Board determine that the probable causes of this accident were the following:
- Non-procedural application of power during take-off and initial climb that led to left engine malfunction.
- The questionable qualifications of the flight crew.
- Low level of competence of the pilots.
- Not feathering the left engine.
- Turning towards the bad engine.
- Not declaring an emergency.
Final Report:

Crash of a NAMC YS-11A-600 in Manila

Date & Time: Nov 16, 2006 at 1425 LT
Type of aircraft:
Operator:
Registration:
RP-C3590
Survivors:
Yes
Schedule:
Tacloban - Manila
MSN:
2106
YOM:
1969
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Tacloban on a charter flight to Manila, carrying five employees of the Philippines Central Bank and four crew members. Upon landing on runway 06, the aircraft veered off runway to the right, lost its right main gear and came to rest. All 9 occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Fokker F27 Friendship 600 off Manila: 19 killed

Date & Time: Nov 11, 2002 at 0607 LT
Type of aircraft:
Registration:
RP-C6888
Flight Phase:
Survivors:
Yes
Schedule:
Manila - Laoag - Basco
MSN:
10571
YOM:
1978
Flight number:
LPN585
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
29
Pax fatalities:
Other fatalities:
Total fatalities:
19
Circumstances:
Shortly after takeoff from Manila-Ninoy Aquino Airport runway 31, while in initial climb, the captain reported technical problems and elected to return for an emergency landing. Finally, he attempted to ditch the aircraft off Manila. While contacting water, the aircraft lost its tail and sank by a depth of about 15 metres. Fifteen people were rescued while 19 others were killed, among them a crew member.
Probable cause:
Failure of the left engine during initial climb for unknown reasons. It was reported that thick black smoke was coming out from the left engine shortly after liftoff.

Crash of a De Havilland DHC-7-102 in Manila

Date & Time: Sep 5, 2002 at 1820 LT
Operator:
Registration:
RP-C2788
Survivors:
Yes
Schedule:
Manila - Caticlan
MSN:
89
YOM:
1982
Flight number:
RIT897
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
45
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine aircraft departed Manila-Ninoy Aquino Airport at 1536LT on a schedule flight to Caticlan with 45 passengers and four crew members. On approach to Caticlan, the crew encountered technical problems with the hydraulic system and could not lowered the right main gear that remained stuck in its wheel well. The captain decided to return to Manila and followed a holding pattern to burn fuel. After touchdown on runway 24, the aircraft went out of control, veered off runway to the right and came to rest in a grassy area. All 49 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The hydraulic pump on engine n°3 and 4 failed, causing a loss of hydraulic pressure on the secondary hydraulic system that dropped almost to zero.

Crash of a Beechcraft H18 off Manila

Date & Time: Nov 21, 2001 at 1715 LT
Type of aircraft:
Registration:
RP-C692
Survivors:
Yes
Schedule:
Taytay – Manila
MSN:
BA-763
YOM:
1969
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Taytay-Sandoval-Cesar Lim Rodriguez Airport on a charter flight to Manila, carrying one passenger and two pilots. While approaching Manila, the left engine failed. The crew informed ATC about his situation and continued the descent to Manila when, shortly later, the right engine lost power. Unable to maintain the assigned altitude, the crew attempted to ditch the aircraft in the bay of Manila, about 3 km offshore. The aircraft floated for few minutes, allowing all three occupants to evacuate the cabin. Few minutes later, the aircraft sank and all three occupants were rescued. The wreckage was not recovered.
Probable cause:
It was reported that white smoke was coming out from the left engine during the descent, forcing the crew to shut it down and feathering its propeller. Due to lack of evidences because the wreckage was not found, the exact cause of the engine failure could not be determined.

Crash of a Piper PA-31-350 Navajo Chieftain in Manila

Date & Time: Jan 9, 1998 at 1935 LT
Operator:
Registration:
N4111M
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Manila - Saipan
MSN:
31-8352001
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On January 9, 1998, at 1935 hours Philippines local time, a Piper PA-31, N4111M, reportedly experienced a loss of engine power and crashed at the Ninoy Aquino International Airport, Manila, Philippines. The aircraft was substantially damage the airline transport rated pilot and copilot were not injured. Visual meteorological conditions existed for the night ferry flight to Saipan in the Marianas, and an instrument flight rules (IFR) flight plan had been filed. The pilot stated that after completing a preflight they had been cleared to taxi to the active runway. The pilot requested a full length takeoff from runway 06. Approximately 75 feet after lifting off from the ground, the pilot requested that the copilot retract the landing gear. The pilot reported that shortly after the landing gear was raised the aircraft yawed sharply to the right. He lowered the nose to regain some of the airspeed that was lost due to the right yaw. He stated that they were losing airspeed and altitude quickly, and asked the copilot to extend the landing gear. The pilot reported that on landing he had the power on until they contacted the runway. The aircraft slid to the left and came to rest after striking a concrete ditch. A test flight of the accident aircraft had been conducted 2 days and on the day before the accident. The purpose of the test flights were to check the propellers that had been overhauled, and to obtain a ferry permit from the Federal Aviation Administration's Designated Airworthiness Representative (DAR). The DAR found the aircraft to be within required specifications. He made the appropriate entry into the aircraft's logbook and issued the ferry authorization.