Crash of a Socata TBM-700 in Yamazoe: 2 killed

Date & Time: Aug 14, 2017 at 1215 LT
Type of aircraft:
Registration:
N702AV
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Yao – Fukushima
MSN:
182
YOM:
2001
Location:
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3750
Captain / Total hours on type:
7.00
Aircraft flight hours:
2094
Circumstances:
The single engine aircraft departed Yao Airport at 1157LT on a leisure flight to Fukushima, carrying one passenger and one pilot. Few minutes later, the pilot reported an unexpected situation to ATC and was cleared to return to Yao. At an altitude of 17,200 feet and a speed of 150 knots, the aircraft entered an uncontrolled descent, partially disintegrated in the air and eventually crashed in a hilly and wooded terrain near the village of Yamazoe, bursting into flames. Both occupants were killed.
Probable cause:
In the accident, it is highly probable that the Aircraft lost control during flight, nose-dived while turning, and disintegrated in mid-air, resulting in the crash. It is somewhat likely that the Aircraft lost control during flight, because the captain did not have pilot skills and knowledge necessary for the operation of the Aircraft, and was not able to perform proper flight operations.
Final Report:

Crash of a Beechcraft LR-2 Hayabusa near Assabu: 4 killed

Date & Time: May 15, 2017 at 1147 LT
Operator:
Registration:
23057
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Sapporo – Hakodate
MSN:
FL-677
YOM:
2009
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The Beechcraft LR-2 Hayabusa (a version of the Beechcraft 350 Super King Air) departed Sapporo-Okadama Airport at 1123LT on a flight to Hakodate to evacuate a patient. On board were two doctors and two pilots. While descending to Hakodate at an altitude of 3,000 feet, the crew encountered poor weather conditions with low clouds and rain showers when the airplane registered 23057 (JG-3057) impacted the slope of a mountain located near Assabu, about 40 km northwest of Hakodate Airport. The aircraft disintegrated on impact and all four occupants were killed.

Crash of a BAe U-125 at Kanoya AFB: 6 killed

Date & Time: Apr 6, 2016 at 1435 LT
Type of aircraft:
Operator:
Registration:
49-3043
Flight Type:
Survivors:
No
Site:
Schedule:
Kanoya - Kanoya
MSN:
258242
YOM:
1993
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The aircraft departed Kanoya AFB at 1315LT on a calibration flight with six people on board. After he complete a counter clockwise arc, the crew started the descent to Kanoya AFB Runway 08R. The visibility was poor due to low clouds. On approach, at an altitude of 3,000 feet, the aircraft entered clouds when the GPWS alarm sounded. Two second later, the crew deactivated the alarm and continued the approach. Ten seconds later, the aircraft impacted trees and crashed on the slope of Mt Takakuma (1,182 metres high) located 10 km north of the airbase. The wreckage was found a day later and all six crew members were killed.
Probable cause:
Controlled flight into terrain after the crew continued the approach in poor visibility without visual contact with the environment. Misidentification of the environment on part of the crew was a contributing factor, as well as the fact that the crew deactivated the GPWS alarm and failed to initiate corrective maneuver.

Crash of a Piper PA-46-350P Malibu Mirage in Chofu: 3 killed

Date & Time: Jul 26, 2015 at 1058 LT
Operator:
Registration:
JA4060
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Chōfu - Amami
MSN:
46-22011
YOM:
1989
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1300
Captain / Total hours on type:
120.00
Aircraft flight hours:
2284
Circumstances:
On Sunday, July 26, 2015 at around 10:58 Japan Standard Time (JST: UTC + 9 hrs: unless otherwise stated, all times are indicated in JST using the 24-hour clock), a privately owned Piper PA-64-350P, registered JA4060, crashed into a private house at Fujimi Town in Chōfu City, right after its takeoff from Runway 17 of Chōfu Airport There were five people on board, consisting of the captain and four passengers. The captain and one passenger died and three passengers were seriously injured. In addition, one resident died and two residents had minor injuries. The aircraft was destroyed and a fire broke out. Furthermore, the house where the Aircraft crashed into were consumed in a fire, and neighboring houses sustained damage due to the fire and other factors.
Probable cause:
It is highly probable that this accident occurred as the speed of the Aircraft decreased during takeoff and climb, which led the Aircraft to stall and crashed into a residential area near Chōfu Airport. It is highly probable that decreased speed was caused by the weight of the Aircraft exceeding the maximum takeoff weight, takeoff at low speed, and continued excessive nose-up attitude. As for the fact that the Captain made the flight with the weight of the Aircraft exceeding the maximum takeoff weight, it is not possible to determine whether or not the Captain was aware of the weight of the Aircraft exceeded the maximum takeoff weight prior to the flight of the accident because the Captain is dead. However, it is somewhat likely that the Captain had insufficient understanding of the risks of making flights under such situation and safety awareness of observing relevant laws and regulations. It is somewhat likely that taking off at low speed occurred because the Captain decided to take a procedure to take off at such a speed; or because the Captain reacted and took off due to the approach of the Aircraft to the runway threshold. It is somewhat likely that excessive nose-up attitude was continued in the state that nose-up tended to occur because the position of the C.G. of the Aircraft was close to the aft limit, or the Captain maintained the nose-up attitude as he prioritized climbing over speed. Adding to these factors, exceeding maximum takeoff weight, takeoff at low speed and continued excessive nose-up attitude, as the result of analysis using mathematical models, it is somewhat likely that the decreased speed was caused by the decreased engine power of the Aircraft; however, as there was no evidence of showing the engine malfunction, it was not possible to determine this.
Final Report:

Crash of a Shin Meiwa US-2 off Cape Ashizuri

Date & Time: Apr 28, 2015 at 1455 LT
Type of aircraft:
Operator:
Registration:
9905
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Iwakuni - Iwakuni
MSN:
4005
Country:
Region:
Crew on board:
19
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine seaplane departed Iwakuni AFB to conduct a training mission over the sea, carrying 19 crew members from the 31st Squadron. For unknown reasons, the crew was apparently forced to attempt an emergency landing when the aircraft crashed in the sea some 40 km northeast of Cape Ashizuri. The aircraft lost an engine and a float and came to rest partially submerged. All 19 occupants were rescued, among them four were injured. The aircraft was damaged beyond repair.

Crash of an Airbus A320-232 in Hiroshima

Date & Time: Apr 14, 2015 at 2005 LT
Type of aircraft:
Operator:
Registration:
HL7762
Survivors:
Yes
Schedule:
Seoul – Hiroshima
MSN:
3244
YOM:
2007
Flight number:
OZ162
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
74
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8242
Captain / Total hours on type:
1318.00
Copilot / Total flying hours:
1588
Copilot / Total hours on type:
1298
Aircraft flight hours:
23595
Circumstances:
The approach to Hiroshima Airport was completed in marginal weather conditions. The autopilot was disengaged at 2,100 feet MSL when the aircraft descended below the glide path and hit approach lights and the localiser antenna located 325 meters short of runway 28. The aircraft continued the descent, hit the soft ground short of runway. Then it rolled on runway for some 1,154 meters, veered to the left, went off runway and came to rest 130 meters to the left of the concrete runway, some 1,477 meters past the runway threshold. All 82 occupants were evacuated, among them 27 (25 passengers and 2 crew members) were injured. The aircraft was considered as written off due to severe damages on both engines, ailerons, wings and the bottom of the fuselage. At the time of the accident, weather conditions were difficult with visibility up to 4 km, RVR on runway 28 variable from 300 to 1,800 meters, light rain, partial fog, one octa cloud at 0 feet, 4 octas at 500 feet, 6 octas at 1,200 feet.
Probable cause:
It is certain that when landing on RWY 28 at the Airport, the Aircraft undershot and the PIC commenced executing a go-around; however, it collided with the Aeronautical Radio Navigation Aids located in front of RWY 28 threshold, just before turning to climb. Regarding the fact that the Aircraft undershot, it is probable that there might be following aspects in causes: The PIC continued approaching without executing a go around while the position of the Aircraft could not be identified by visual references which should have been in view and identified continuously at or below the approach height threshold (Decision Altitude: DA); and as well, the FO, as pilot-monitoring who should have monitored meteorological conditions and flight operations, did not make a call-out of go-around immediately when he could not see the runway at DA. Regarding the fact that the PIC continued approaching without executing a go around while the position of the Aircraft could not be identified by visual references which should have been in view and identified continuously at or below DA, he did not comply with the regulations and SOP, and it is probable that there was a background factor that the education and trainings for compliance of rules in the Company was insufficient. In addition, regarding the fact that the FO did not make an assertion of go around, it is probable that the CRM did not function appropriately.
Final Report:

Crash of a Piper PA-46-350P Malibu Mirage in Kumamoto: 2 killed

Date & Time: Jan 3, 2011 at 1714 LT
Operator:
Registration:
JA701M
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Kumamoto – Kitakyūshū
MSN:
46-36188
YOM:
1999
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1537
Captain / Total hours on type:
119.00
Aircraft flight hours:
1497
Circumstances:
The single engine aircraft departed Kumamoto Airport runway 07 at 1711LT on a private flight to Kitakyūshū, with two persons on board: a PIC in the left seat and a passenger in the right seat. At 17:12:11, the radar of the Kumamoto aerodrome station C captured the aircraft. The pilot made a position report at 6 nm north of the airport at 2,300 feet. While climbing to the altitude of 6,500 feet, the pilot was instructed to change the frequency. About three minutes after takeoff, the aircraft collided with trees and crashed in a wooded area located on the southeast slope of Mt Yago, about 14 km northeast of Kumamoto Airport. The wreckage was found in the afternoon of the following day at an altitude of 850 metres. The aircraft was destroyed and both occupants were killed, Mr. & Mrs. Hiroshi and Hiromi Kanda.
Probable cause:
It is highly probable that the aircraft collided with the mountain slope during its in-cloud post-takeoff climb with low climb rate on its VFR flight to Kitakyushu Airport from Kumamoto Airport, resulting in the aircraft destruction and fatal injuries of two persons on board–the PIC and the passenger. It is somewhat likely that the contributing factor to in-cloud flight toward mountain slope with low climb rate is the PIC’s lack of familiarization with terrain features near Kumamoto Airport; however, the JTSB was unable to clarify the reason.
Final Report:

Crash of a NAMC YS-11M-A-624 at Ozuki AFB

Date & Time: Sep 28, 2009 at 1240 LT
Type of aircraft:
Operator:
Registration:
9044
Flight Type:
Survivors:
Yes
Schedule:
Atsugi AFB - Tokushima AFB - Iwakuni AFB - Ozuki AFB
MSN:
2182
YOM:
1973
Country:
Region:
Crew on board:
11
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6900
Captain / Total hours on type:
3000.00
Circumstances:
Crew was completing a training mission from Atsugi AFB with intermediate stops at Tokushima AFB and Iwakuni AFB. After landing on runway 35 (1,200 meters long) at Ozuki AFB, the aircraft was unable to stop within the remaining distance. It overran, went through a fence, lost its nose gear and came to rest 150 meters further in a rice paddy field. All 11 occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a McDonnell Douglas MD-11F in Tokyo: 2 killed

Date & Time: Mar 23, 2009 at 0649 LT
Type of aircraft:
Operator:
Registration:
N526FE
Flight Type:
Survivors:
No
Schedule:
Guangzhou - Tokyo
MSN:
48600/560
YOM:
1993
Flight number:
FDX080
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
8132
Captain / Total hours on type:
3648.00
Copilot / Total flying hours:
5248
Copilot / Total hours on type:
879
Aircraft flight hours:
40767
Aircraft flight cycles:
7131
Circumstances:
Aircraft bounced repeatedly during landing on Runway 34L at Narita International Airport. During the course of bouncing, its left wing was broken and separated from the fuselage attaching point and the airplane caught fire. The airplane rolled over to the left being engulfed in flames, swerved off the runway to the left and came to rest inverted in a grass area. The Pilot in Command (PIC) and the First Officer (FO) were on board the airplane, and both of them suffered fatal injuries. The airplane was destroyed and the post-crash fire consumed most parts.
Probable cause:
In this accident, when the airplane landed on Runway 34L at Narita International Airport, it fell into porpoising. It is highly probable that the left wing fractured as the load transferred from the left MLG to the left wing structure on the third touchdown surpassed the design limit (ultimate load). It is highly probable that a fire broke out as the fuel spillage from the left wing caught fire, and the airplane swerved left off the runway rolling to the left and came to rest inverted on the grass area. The direct causes which the airplane fell into the porpoise phenomenon are as follows:
a. Large nose-down elevator input at the first touchdown resulted in a rapid nose down motion during the first bounce, followed by the second touchdown on the NLG with negative pitch attitude. Then the pitch angle rapidly increased by the ground reaction force, causing the larger second bounce, and
b. The PF‘s large elevator input in an attempt to control the airplane without thrust during the second bounce. In addition, the indirect causes are as follows:
a. Fluctuating airspeed, pitch attitude due to gusty wind resulted in an approach with a large sink rate,
b. Late flare with large nose-up elevator input resulted in the first bounce and
c. Large pitch attitude change during the bounce possibly made it difficult for the crewmembers to judge airplane pitch attitude and airplane height relative to the ground (MLG height above the runway).
d. The PM‘s advice, override and takeover were not conducted adequately. It is somewhat likely that, if the fuse pin in the MLG support structure had failed and the MLG had been separated in the overload condition in which the vertical load is the primary component, the damage to the fuel tanks would have been reduced to prevent the fire from developing rapidly. It is probable that the fuse pin did not fail because the failure mode was not assumed under an overload condition in which the vertical load is the primary component due to the interpretation of the requirement at the time of type certification for the MD-11 series airplanes.
Final Report:

Crash of a Cessna 404 Titan near Nakatsugawa: 2 killed

Date & Time: Nov 15, 2007 at 1036 LT
Type of aircraft:
Operator:
Registration:
JA5257
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Nagoya - Nagoya
MSN:
404-0041
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
16512
Captain / Total hours on type:
837.00
Aircraft flight hours:
5671
Circumstances:
The twin engine aircraft departed Nagoya Airport at 0846LT on an aerial photography mission over the Mt Ena and Gifu district. Several circuits were completed over the area of Mt Ena at various altitudes and in good weather conditions. Approaching Mt Ena at an altitude of about 2,000 metres, weather conditions worsened as the mountain was shrouded in clouds. While flying under VFR mode, the aircraft entered clouds, collided with a tree and crashed in a wooded area. The copilot (a mechanic) was seriously injured while both other occupants were killed. The aircraft was destroyed.
Probable cause:
Controlled flight into terrain after the pilot decided to continue under VFR mode in IMC conditions.
Final Report: