ASN logo
ASN Wikibase Occurrence # 196871
Last updated: 10 October 2019
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.

Type:Silhouette image of generic MU2 model; specific model in this crash may look slightly different
Mitsubishi MU-2B-26A
Owner/operator:Aibal SA
Registration: LV-MCV
C/n / msn: 361SA
Fatalities:Fatalities: 3 / Occupants: 3
Other fatalities:0
Aircraft damage: Written off (damaged beyond repair)
Location:Delta del Parana -   Argentina
Phase: En route
Departure airport:San Fernando
Destination airport:Las Lomitas
The airplane began to have problems with XPDR, which didn´t report to ATC.
ATC called him back to the origin airport. The crew argue that the XPDR was working fine before takeoff and refuses to come back. Six minutes after takeoff the aircraft dissapeared from radar screens somewhere over San Fernando.

Witnesses declared they heard two explosions during afternoon in the region of the Delta (17 kms from San Fernando). The sound would have occurred at the same time of the last cellphone signal was recorded of one occupant.

The accident place was found on August, 19 in the marshy area of the Parana's Delta (S34º1.403′

Conclusions of the Analysis:
On a private general aviation flight, during the climb phase, the aircraft experienced an in-flight loss of control condition (LOC-I) as a result of from which it hit the ground.
The circumstances and conditions present in the accident suggest a situation of high cockpit workload due to the prevailing operating conditions, with the potential to cause loss of flight control. This situation is attributable to the combination of the following factors:
- The particular characteristics of the aircraft;
- The attention required by the transponder as it is not displayed by air traffic control;
- The detour of the planned flight at the request of the inspection department of air traffic;
- Aircraft trajectory management with autopilot switched off;
- The pilot's limited experience in instrument flight conditions.
In addition, the absence of additional instruction in the aircraft type (due to the lack of specific regulations) can be considered a contributing factor, according to the probable scenario described above.
In addition, the research identified the following elements with potential impact in operational safety:
- Absence of the TAWS system on the aircraft in non-conformity with the established RAAC 91;
- Lack of effective means to enable the flight plan office to quickly determine whether an aircraft has operating restrictions;
- Shortcomings in the training of staff in the units ATS and SAR in search and rescue.

Final Report of JIAAC:

Revision history:

25-Jul-2017 06:50 gerard57 Added
25-Jul-2017 06:51 harro Updated [Aircraft type, Cn]
25-Jul-2017 10:25 RobertMB Updated [Source]
25-Jul-2017 11:43 Iceman 29 Updated [Operator, Source, Embed code, Narrative]
27-Jul-2017 05:25 gerard57 Updated [Total fatalities, Location, Source, Embed code, Damage, Narrative]
27-Jul-2017 16:05 alfredoristol Updated [Total fatalities, Narrative]
20-Aug-2017 06:56 Anon. Updated [Source, Narrative]
20-Aug-2017 06:56 lefg Updated [Total fatalities, Source, Narrative]
20-Aug-2017 06:58 Dmitriy Updated [Narrative]
22-Aug-2017 15:46 Elsus Updated [Narrative]
14-Dec-2017 18:51 nupa Updated [Time, Narrative]
31-Jul-2018 20:14 Captain Adam Updated [Embed code]
31-Jul-2018 20:18 harro Updated [Narrative]
02-Aug-2018 19:39 Iceman 29 Updated [Source, Embed code]

Corrections or additions? ... Edit this accident description