Serious incident Saab 340B JA03HC, Saturday 4 June 2011
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:Saturday 4 June 2011
Time:11:38
Type:Silhouette image of generic SF34 model; specific model in this crash may look slightly different    
Saab 340B
Owner/operator:Hokkaido Air System
Registration: JA03HC
MSN: 340B-458
Fatalities:Fatalities: 0 / Occupants: 13
Other fatalities:0
Aircraft damage: None
Category:Serious incident
Location:Okushiri Airport (OIR/RJEO) -   Japan
Phase: Initial climb
Nature:Passenger - Scheduled
Departure airport:Hakodate Airport (HKD/RJCH)
Destination airport:Okushiri Airport (OIR/RJEO)
Investigating agency: JTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
A Saab 340B, registered JA03HC, operated by Hokkaido Air System, took off from Hakodate Airport as a scheduled Flight 2891. During the approach to runway 31 of Okushiri Airport, the aircraft executed a go-around and once started climbing, reaching an altitude of 750 feet. The airplane then began to descend.
When flight crew became aware of the situation they executed an emergency climb from a radio altitude of 90 feet.
The aircraft flew back to Hakodate Airport, following some holdings over Okushiri Airport.
No one was injured and there was no damage to the aircraft.

Probable Causes:
In this serious incident, during the approach to Runway 31 of Okushiri Airport, the Aircraft executed a go-around and once started climbing but it soon reverted to descend and came close to the ground. Consequently, flight crewmembers came to realize the situation and executed an emergency operation to avoid crash to the ground.
It is highly probable that the Aircraft’s descent and approach to the ground was caused by the following factors:
(1) The PIC followed the Flight Director command bar instructions, which indicated the descent because the altitude setting was not changed to the initial go around altitude, and subsequently the PIC made the Aircraft descend even lower than the FD command bar instructions.
(2) The PIC and the FO could not notice descending of the Aircraft and their recovery maneuvers got delayed.
It is highly probable that these findings resulted from the fact that the PIC could not perform a fundamental instrument flight, the PIC and the FO used the Autopilot/Flight Director System in an inappropriate manner without confirming the flight instruments and the flight modes, and the FO could not transiently carry out closer monitor of the flight instruments because of the other operations to be done.
Moreover, it is probable that the FO’s operation of engaging an autopilot and changing the vertical mode to make the Aircraft climb by using the Autopilot/Flight Director System eventually became a factor to delay avoiding maneuvers against ground proximity.
It is probable that the Company didn’t create a standard procedure, reflecting the contents of Aircraft Operating Manual, for its crewmembers to confirm and call out the changes mode, without noticing its importance and didn’t carry out adequate training. Furthermore, it is probable that the PIC and the FO excessively relied on the autoflight system.

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

Sources:

http://www.mlit.go.jp/jtsb/eng-air_report/JA03HC.pdf

Revision history:

Date/timeContributorUpdates
27-Nov-2014 18:59 harro Added

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
www.FlightSafety.org