Wirestrike Accident Aerospatiale AS 332L Super Puma JA9672, Wednesday 8 November 2017
ASN logo
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Wednesday 8 November 2017
Time:14:29 LT
Type:Silhouette image of generic AS32 model; specific model in this crash may look slightly different    
Aerospatiale AS 332L Super Puma
Owner/operator:Toho Air Service
Registration: JA9672
MSN: 2173
Fatalities:Fatalities: 4 / Occupants: 4
Other fatalities:0
Aircraft damage: Destroyed
Location:Ueno, Gunma Prefecture -   Japan
Phase: En route
Departure airport:Hayakawa town, Yamanashi prefecture
Destination airport:Tochigi Heliport, Haga town, Tochigi prefecture
Investigating agency: JTSB
Confidence Rating: Information verified through data from accident investigation authorities
The helicopter crashed on a road bridge. According to local media all four occupants, flight crew and rear crew, died in the crash. The helicopter was consumed by post impact fire.

Local press reports mention the aircraft flying low down a valley and a local power outage suggesting a possible wire strike. Eyewitness reports that the helicopter was initially bound northeast, but returned back in a low altitude, which is suspected an attempt of precaution landing. Thereafter, some parts of the tail section were separated, and the Super Puma enter a steep dive.

On 21st November 2017, JTSB released an interim report. It reveals that a pin to attach the rail rotor was fractured and found several ten meters away from the main fuselage, at the other side of the river. EASA issued an Airworthiness Directive which requires to inspect these pins of AS 332L and AS 332L1 helicopters.

The failure followed incorrect maintenance and the degradation of the white TR blade flapping hinge bearing

Accident investigation:
Investigating agency: JTSB
Report number: 
Status: Investigation completed
Download report: Final report





Revision history:

08-Nov-2017 07:34 gerard57 Added
08-Nov-2017 07:43 gerard57 Updated [Time, Total fatalities, Source, Narrative]
08-Nov-2017 08:01 L1011tristar Updated [Aircraft type, Registration, Cn, Location, Nature, Source]
08-Nov-2017 08:48 TB Updated [Time, Aircraft type]
08-Nov-2017 13:27 isamuel Updated [Time, Departure airport, Destination airport, Source, Narrative]
08-Nov-2017 13:58 Aerossurance Updated [Source, Narrative]
08-Nov-2017 14:00 Aerossurance Updated [Narrative]
08-Nov-2017 14:33 Aerossurance Updated [Source, Narrative]
08-Nov-2017 14:34 Aerossurance Updated [Embed code]
09-Nov-2017 09:28 Aerossurance Updated [Source]
10-Nov-2017 09:21 Aerossurance Updated [Location]
23-Nov-2017 07:21 isamuel Updated [Source, Narrative]
06-May-2020 15:08 Aerossurance Updated [Source, Embed code]
09-May-2020 09:56 Aerossurance Updated [Source, Narrative]
09-May-2020 10:12 Aerossurance Updated [Embed code]
30-Sep-2022 19:18 harro Updated [Date, Time, Embed code, Accident report]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314