Crash of a Gulfstream G200 in Tegucigalpa

Date & Time: May 22, 2018 at 1119 LT
Type of aircraft:
Operator:
Registration:
N813WM
Survivors:
Yes
Schedule:
Austin – Tegucigalpa
MSN:
54
YOM:
2001
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5400
Aircraft flight hours:
5299
Circumstances:
On final approach to runway 02, the copilot informed the captain about the fact that the approach speed was too high by 20 knots to the reference speed. The captain replied he would correct this but the airplane landed too far down runway 02, about 993 metres before the end of the runway which is 2,010 metres long but with a displaced threshold, giving a landing distance available of 1,700 metres. Upon touchdown, the aircraft's speed was 142 knots, about 14 knots above the speed reference according to existing conditions and weight and balance. Unable to stop within the remaining distance, the airplane overran, went down an embankment, crossed a road and came to rest against a second embankment, broken in two. All six occupants were slightly injured and the aircraft was destroyed. Owned by TVPX, it was operated by Silver Air.
Probable cause:
The accident was the consequence of the followings:
- The crew completed an approach at a speed higher than the reference speed for weight and balance specified in the aircraft checklist,
- Lack of specific information on the length of the runway at Toncontín International Airport by the crew for the approach to runway 02, when landing almost halfway down the runway leaving little distance for effective braking of the systems,
- A late activation of the thrust reverser systems about 0:13 seconds after touchdown was considered as a contributing factor,
- Existing weather conditions were not considered as a contributing factor.
Final Report:

Crash of a Cessna 525 Citation CJ4 in Marion

Date & Time: Apr 2, 2018 at 1709 LT
Type of aircraft:
Operator:
Registration:
N511AC
Survivors:
Yes
Schedule:
Jackson - Marion
MSN:
525C-0081
YOM:
2012
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
35437
Captain / Total hours on type:
2537.00
Aircraft flight hours:
2537
Circumstances:
A single-engine airplane was taking off from runway 15 about the same time that a multi-engine business jet landed on a nearly perpendicular runway (runway 22). The single-engine airplane, piloted by a private pilot, was departing on a local flight. The jet, piloted by an airline transport pilot, was rolling down the runway following a straight-in visual approach and landing. The single-engine airplane collided with the empennage of the jet at the intersection of the two runways. Witnesses in the airport lounge area heard the pilot of the single-engine airplane announce on the airport's universal communications (UNICOM) traffic advisory frequency a few minutes before the accident that the airplane was back-taxiing on the runway. The pilot of the jet did not recall making any radio transmissions on the UNICOM frequency and review of the jet's cockpit voice recorder did not reveal any incoming or outgoing calls on the frequency. The pilots of both airplanes were familiar with the airport, and the airport was not tower controlled. The airport had signage posted on all runways indicating that traffic using the nearly perpendicular runway could not be seen and instructed pilots to monitor the UNICOM. A visibility assessment confirmed reduced visibility of traffic operating from the nearly perpendicular runways. The reported weather conditions about the time of the accident included clear skies with 4 miles visibility due to haze. Both airplanes were painted white. It is likely that the pilot of the jet would have been aware of the departing traffic if he was monitoring the UNICOM frequency. Although the jet was equipped with a traffic collision avoidance system (TCAS), he reported that the system did not depict any conflicting traffic during the approach to the airport. Although the visibility assessment showed reduced visibility from the departing and arrival runways, it could not be determined if or at what point during their respective landing and takeoff the pilot of each airplane may have been able to see the other airplane. In addition to the known reduced visibility of the intersecting runways, both airplanes were painted white and there was reported haze in the area, which could have affected the pilots' ability to see each other.
Probable cause:
The failure of both pilots to see and avoid the other airplane as they converged on intersecting runways. Contributing to the accident was the jet pilot's not monitoring the airport's traffic advisory frequency, known reduced visibility of the intersecting runways, and hazy weather condition.
Final Report:

Crash of a Canadair CL-600-2B16 Challenger 604 near Shahr-e-Kord: 11 killed

Date & Time: Mar 11, 2018 at 1840 LT
Type of aircraft:
Operator:
Registration:
TC-TRB
Flight Phase:
Survivors:
No
Site:
Schedule:
Sharjah – Istanbul
MSN:
5494
YOM:
2001
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
11
Captain / Total flying hours:
4880
Captain / Total hours on type:
1600.00
Copilot / Total flying hours:
1132
Copilot / Total hours on type:
114
Aircraft flight hours:
7935
Aircraft flight cycles:
3807
Circumstances:
A Turkish Challenger 604 corporate jet impacted a mountain near Shahr-e Kurd in Iran, killing all 11 on board. The aircraft departed Sharjah, UAE at 13:11 UTC on a flight to Istanbul, Turkey. The aircraft entered Tehran FIR fifteen minutes later and the Tehran ACC controller cleared the flight to climb to FL360 according to its flight plan. About 14:32, the pilot requested FL380, which was approved. Before reaching that altitude, the left and right airspeeds began to diverge by more than 10 knots. The left (captain's) airspeed indicator showed an increase while the right hand (copilot's) airspeed indicator showed a decrease. A caution aural alert notified the flight crew of the difference. Remarks by the flight crew suggested that an 'EFIS COMP MON' caution message appeared on the EICAS. As the aircraft was climbing, the crew reduced thrust to idle. Approximately 63 seconds later, while approaching FL380, the overspeed aural warning (clacker) began to sound, indicating that the indicated Mach had exceeded M 0.85. Based on the Quick Reference Handbook (QRH) of the aircraft, the pilot flying should validate the IAS based on the aircraft flight manual and define the reliable Air Data Computer (ADC) and select the reliable Air Data source. The pilot did not follow this procedure and directly reduced engine power to decrease the IAS after hearing the clacker. The actual airspeed thus reached a stall condition. The copilot tried to begin reading of the 'EFIS COMP MON' abnormal procedure for three times but due to pilot interruption, she could not complete it. Due to decreasing speed, the stall aural warning began to sound, in addition to stick shaker and stick pusher activating repeatedly. The crew then should have referred to another emergency procedure to recover from the stall condition. While the stick pusher acted to pitch down the aircraft to prevent a stall condition, the captain was mistakenly assumed an overspeed situation due to the previous erroneous overspeed warning and pulled on the control column. The aircraft entered a series of pitch and roll oscillations. The autopilot was disengaged by the crew before stall warning, which ended the oscillations. Engine power began to decrease on both sides until both engines flamed out in a stall condition. From that point on FDR data was lost because the electric bus did not continue to receive power from the engine generators. The CVR recording continued for a further approximately 1 minute and 20 seconds on emergency battery power. Stall warnings, stick shaker and stick pusher activations continued until the end of the recording. The aircraft then impacted mountainous terrain. Unstable weather conditions were present along the flight route over Iran, which included moderate up to severe turbulence and icing conditions up to 45000ft. These conditions could have caused ice crystals to block the left-hand pitot tube. It was also reported that the aircraft was parked at Sharjah Airport for three days in dusty weather condition. Initially the pitot covers had not been applied. The formation of dust inside the pitot tube was considered another possibility.
Probable cause:
The accident was caused by insufficient operational prerequisites for the management of erratic airspeed indication failure by the cockpit crew. The following contributing factors were identified:
- The aircraft designer/manufacturer provided insufficient technical and operational guidance about airspeed malfunctions that previously occurred.
- Lack of effective CRM.
Final Report:

Crash of a Gulfstream G200 in Abuja

Date & Time: Jan 29, 2018 at 1520 LT
Type of aircraft:
Operator:
Registration:
5N-BTF
Survivors:
Yes
Schedule:
Lagos - Abuja
MSN:
180
YOM:
2007
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5300
Captain / Total hours on type:
280.00
Copilot / Total flying hours:
5700
Copilot / Total hours on type:
93
Aircraft flight hours:
1421
Aircraft flight cycles:
921
Circumstances:
On 25th January 2018 at 14:28 h, a Gulfstream 200 (G200) aircraft with nationality and registration marks 5N-BTF operated by Nestoil Plc, departed Murtala Mohammed International Airport, Lagos (DNMM) as a charter flight to Nnamdi Azikiwe International Airport, Abuja (DNAA) on an Instrument Flight Rules (IFR) flight plan. Onboard were four passengers and three flight crew members. The Pilot in command (PIC) was the Pilot Monitoring (PM) and the Co-pilot was the Pilot Flying (PF). The departure, cruise and approach to Nnamdi Azikiwe International Airport were normal. At 14:45 h, 5N-BTF contacted Abuja radar and was subsequently cleared for Radar vectors ILS approach Runway 22. Abuja Airport Automatic Terminal Information Service (ATIS) Papa for time 14:20 h was monitored as follows; “Main landing runway 22, wind 110/07 kt, Visibility 3,500 m in Haze, No Significant Clouds, Temperature/Dew point 33/- 01°C, QNH 1010 hPa, Trend No Significant Change, End of Information Papa”. At 15:17 h, 5N-BTF reported 4 NM on Instrument approach (ILS) and was requested to report 2 NM because there was a preceding aircraft (Gulfstream 5) on landing roll. Thereafter, 5N-BTF was cleared to land runway 22 with reported wind of 070°/07 kt. At 15:18 h, the aircraft touched down slightly left of the runway centre line. According to the PF, in the process of controlling the aircraft to the centre line, the aircraft skidded left and right and eventually went partly off the runway to the right where it came to a stop. In his report, the PM stated that on touchdown, he noticed the aircraft oscillating left and right as brakes were applied. The oscillation continued to increase and [the aircraft] eventually went off the runway to the right where the aircraft came to a stop, partially on the runway. During the post-crash inspection, the investigation determined that the skid marks on the runway indicated that the aircraft steered in an S-pattern continuously with increasing amplitude, down the runway. On the last right turn, the aircraft exited the right shoulderof the runway, the right main wheel went into the grass and on the final left turn, the right main landing gear strut detached from its main attachment point after which the aircraft finally came to a complete stop on a magnetic heading of 160°. The ATC immediately notified the Aircraft Rescue and Fire Fighting Services (ARFFS), Approach Radar Control, and other relevant agencies about the occurrence. All persons on board disembarked with no injuries. Instrument Meteorological Conditions (IMC) prevailed at the time of the occurrence. The serious incident occcurred in daylight.
Probable cause:
Causal Factor:
The use of improper directional control techniques to maintain the aircraft on the runway.
Contributory Factor:
Improper coordination in taking over control of the aircraft by the PM which was inconsistent with Nestoil SOP.
Final Report:

Crash of a Piper PA-31T1 Cheyenne in Tyler: 2 killed

Date & Time: Jul 13, 2017 at 0810 LT
Type of aircraft:
Operator:
Registration:
N47GW
Flight Phase:
Survivors:
No
Schedule:
Tyler - Midland
MSN:
31T-8104030
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
17590
Aircraft flight hours:
5685
Circumstances:
The airline transport rated pilot and passenger departed on a cross-country business flight in a twin-engine, turbo-propeller-equipped airplane in day, visual meteorological conditions. Shortly after takeoff, the airplane banked left, descended, and impacted terrain about 1/2 mile from the end of the runway. There was not a post-crash fire and fuel was present on site. A postaccident airframe examination did not reveal any anomalies that would have precluded normal operation. Examination of the left engine found signatures consistent with the engine producing power at impact. Examination of the right engine revealed rotational scoring on the compressor turbine disc/blades, and rotational scoring on the upstream side of the power vane and baffle, which indicated that the compressor section was rotating at impact; however, the lack of rotational scoring on the power turbine disc assembly, indicated the engine was not producing power at impact. Testing of the right engine's fuel control unit, fuel pump, propeller governor, and overspeed governor did not reveal any abnormities that would have accounted for the loss of power. The reason for the loss of right engine power could not be determined based on the available information.
Probable cause:
The loss of engine power and the subsequent pilot's loss of control for reasons that could not be determined because post-accident engine examination revealed no anomalies.
Final Report:

Crash of a Beechcraft C90GT King Air off Paraty: 5 killed

Date & Time: Jan 19, 2017 at 1244 LT
Type of aircraft:
Operator:
Registration:
PR-SOM
Survivors:
No
Schedule:
Campo de Marte - Paraty
MSN:
LJ-1809
YOM:
2007
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
7464
Captain / Total hours on type:
2924.00
Circumstances:
The twin engine aircraft departed Campo de Marte Airport at 1301LT bound for Paraty. With a distance of about 200 km, the flight should take half an hour. The approach to Paraty Airport was completed in poor weather conditions with heavy rain falls reducing the visibility to 1,500 metres. While descending to Paraty, the pilot lost visual contact with the airport and initiated a go-around. Few minutes later, while completing a second approach, he lost visual references with the environement then lost control of the aircraft that crashed in the sea near the island of Rasa, about 4 km short of runway 28. Quickly on site, rescuers found a passenger alive but it was impossible to enter the cabin that was submerged. The aircraft quickly sank by a depth of few metres and all five occupants were killed, among them Carlos Alberto, founder of Hotel Emiliano and the Supreme Court Justice Teori Zavascki who had a central role overseeing a massive corruption investigation about the Brazilian oil Group Petrobras.
Probable cause:
Contributing factors:
- Adverse meteorological conditions - a contributor
At the moment of the impact of the aircraft, there was rain with rainfall potential of 25mm/h, covering the Paraty Bay region, and the horizontal visibility was 1,500m. Such horizontal visibility was below the minimum required for VFR landing and take-off operations. Since the SDTK aerodrome allowed only operations under VFR flight rules, the weather conditions proved to be impeding the operation within the required minimum safety limits.
- Decision-making process - a contributor
The weather conditions present in SDTK resulted in visibility restrictions that were impeding flight under VFR rules. In this context, the accomplishment of two attempts to approach and land procedures denoted an inadequate evaluation of the minimum conditions required for the operation at the Aerodrome.
- Disorientation - undetermined
The conditions of low visibility, of low height curve on the water, added to the pilot stress and also to the conditions of the wreckage, which did not show any fault that could have compromised the performance and/or controllability of the aircraft, indicate that the pilot most likely had a spatial disorientation that caused the loss of control of the aircraft.
- Emotional state - undetermined
Through the analysis of voice, speech and language parameters, variations in the emotional state of the pilot were identified that showed evidence of stress in the final moments of the flight. The pilot's high level of anxiety may have influenced his decision to make another attempt of landing even under adverse weather conditions and may have contributed to his disorientation.
- Tasks characteristics - undetermined
The operations in Paraty, RJ, demanded that pilots adapt to the routine of the operators, which was characteristic of the executive aviation. In addition, among operators, possibly because of the lack of minimum operational requirements in SDTK, the pilots who landed even in adverse weather conditions were recognized and valued by the others. Although there were no indications of external pressure on the part of the operator, these characteristics present in the operation in Paraty, RJ, may have favored the pilot's self-imposed pressure, leading him to operate with reduced safety margins.
- Visual illusions - undetermined
The flight conditions faced by the pilot favored the occurrence of the vestibular illusion due to the excess of "G" and the visual illusion of homogeneous terrain. Such illusions probably had, consequently, the pilot's sense that the bank angle was decreasing and that he was at a height above the real. These sensations may have led the pilot to erroneously correct the conditions he was experiencing. Thus, the great bank angle and the downward movement, observed at the moment of the impact of the aircraft, are probably a consequence of the phenomena of illusions.
- Work-group culture - a contributor
Among the members of the pilot group that performed routine flights to the region of Paraty, RJ, there was a culture of recognition and appreciation of those operating under adverse conditions, to the detriment of the requirements established for the VFR operation. These shared values promoted the adherence to informal practices and interfered in the perception and the adequate analysis of the risks present in the operation in SDTK.
Final Report:

Crash of a Rockwell Aero Commander 700 in Beaverdell

Date & Time: May 31, 2016 at 2125 LT
Operator:
Registration:
C-GBCM
Flight Phase:
Survivors:
Yes
Schedule:
Boise – Kelowna
MSN:
700-27
YOM:
1980
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft performed a technical stop in Boise, Idaho, enroute from Arizona to Kelowna. While flying at an altitude of 8,500 feet, both engines failed simultaneously. The pilot reduced his altitude and attempted an emergency landing in a flat area located near Beaverdell, about 37 miles south of Kelowna. By night, the airplane crash landed in a Christmas tree plantation, hit several trees and a fence and eventually came to rest. All six occupants evacuated safely while the aircraft was damaged beyond repair. According to preliminary information, there was still enough fuel in the tanks, and investigations will have to determine the cause of the double engine failure.

Crash of a Beechcraft C90 King Air in Oeiras

Date & Time: Mar 18, 2016 at 1630 LT
Type of aircraft:
Registration:
PP-JBL
Survivors:
Yes
Schedule:
Teresina - Oeiras
MSN:
LJ-861
YOM:
1979
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine airplane departed Teresina on a business flight to Floriano, carrying seven passengers and one pilot, among them Ciro Nogueira, Senator of the State of Piauí and Margarete Coelho, Vice-Governor of the State of Piauí. En route to Floriano, the pilot was informed about the deterioration of the weather conditions at destination and decided to divert to Oeiras Airfield. After touchdown on runway 11 that was wet due to recent rain falls, the aircraft started to skid. Control was lost and the aircraft veered off runway to the left and came to rest in a wooded area, some 10 metres from the runway. All eight occupants were rescued, among them one passenger was slightly injured. The aircraft was damaged beyond repair.
Probable cause:
Contributing factors:
- Application of commands - undetermined
It is possible that the pilot has not acted properly in the controls after touchdown to avoid a runway excursion.
- Flight indiscipline - contributed
Having landed on a non-approved runway, without justifiable reason, the crew member did not comply with the provisions of civil aviation regulations.
- Influence of the environment - undetermined
The wet and puddled runway may have affected directional control and aircraft braking performances during the landing roll.
- Pilot judgment - contributed
The crew member had not correctly assessed the risks involved in the operation in an unapproved runway, without justifiable reason. In addition, the pilot had no considering that the wet and puddle conditions of the runway could affect the directional control and braking performances of the aircraft.
- Decision-making process - contributed
The decision to land at an unapproved aerodrome, as well as having used a wet runway and the presence of puddles denoted an inadequate assessment of the risks present in the context. Failures related to decisions assumed by the pilot contributed to the occurrence insofar as they resulted in the entry of the aircraft into a critical condition, affecting its control.
Final Report:

Crash of an Embraer EMB-820C Navajo in Santa Isabel

Date & Time: Feb 16, 2016 at 1430 LT
Operator:
Registration:
PT-WZA
Flight Phase:
Survivors:
Yes
Schedule:
Jacarepaguá – Campinas
MSN:
820-020
YOM:
1976
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route, the pilot encountered an unexpected situation and attempted an emergency landing. After landing on a road in Santa Isabel, the airplane collided with various obstacles and came to rest. All three occupants evacuated safely and the airplane was damaged beyond repair.

Crash of a Cessna 650 Citation VII in Guarda-Mor: 4 killed

Date & Time: Nov 10, 2015 at 1904 LT
Type of aircraft:
Operator:
Registration:
PT-WQH
Flight Phase:
Survivors:
No
Schedule:
Brasília – São Paulo
MSN:
650-7083
YOM:
1998
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
13143
Copilot / Total flying hours:
2527
Copilot / Total hours on type:
1633
Circumstances:
The aircraft took off from the Presidente Juscelino Kubitschek (SBBR) Aerodrome, Brasília - DF, to the Congonhas Aerodrome (SBSP), São Paulo - SP, at 2039 (UTC), to carry out a personnel transportation flight with two crewmembers and two passengers on board. During the cockpit preparation procedure, the crew members commented about the operation of the Pitch Trim System. The first flight of the day, that occurred in the morning, was from São Paulo to Brasilia and with no abnormalities. About thirty minutes after take-off from Brasília, still during the climb, near the FL370, the cabin voice recorder recorded a characteristic sound of the aircraft’s horizontal stabilizer moving. Then, the aircraft made a downward trajectory with high speed and a big rate of descent until the impact against the ground. The aircraft was destroyed. All occupants perished at the site, among them Lúcio Flávio de Oliveira and Marco Antonio Rossi, two Directors of Banco Brasdesco.
Probable cause:
Contributing factors:
- Control skills – undetermined
It is possible that, after inadvertent movement of the horizontal stabilizer, the crewmembers did not operate on the control switches of the secondary pitch trim system, since no other warning sound (Clacker) was recorded on the CVR recordings. The action prevised in the emergency procedures Pitch Trim Runaway or Failure, item 3, regarding trimming of the aircraft through the secondary system, possibly, was not performed. The performance of the crew may have been restricted only to the elevator control on the aircraft controls or to the control of the stabilizer associated with the primary trimming mode.
- Attitude – undetermined
The decision to make the flight without the proper functioning of the primary pitch trim and autopilot system may have been the result of the pilot's self-confidence because of the successful previous flight under similar operating conditions. Considering the hypothesis that the updated Shutdown Checklist, which should incorporate the Stabilizer Trim Backdrive Monitor - TEST, was not performed after the precrash flight, one could consider that there was a lack of adhesion to the aircraft operating procedures. Such an attitude could be associated with the pilot's self-confidence about the aircraft's operating routine, whose acquired experience could have given him the habit of ignoring some of the procedures deemed less important during the flight completion phase.
- Crew Resource Management – a contributor
Throughout the flight, there was an absence of verbalization and communication of the actions on the checklist. Similarly, in the face of the emergency situation of the horizontal stabilizer (Pitch Trim Runaway or Failure), no statements were identified regarding the actions required to manage this situation among the crew. These characteristics denote inefficiency in the use of human resources available for the aircraft operation.
- Training – undetermined
It is possible that the absence of a periodic training in simulator, especially the emergency Pitch Trim Runway or Failure, has affected the performance of the crew, as far as the CVR did not record statements related to the actions required by the abnormal condition experienced.
- Organizational culture – undetermined
The operator did not usually properly fill out the PT-WQH flight logbook. This condition evidenced the existence of informal rules regarding the monitoring of the operational conditions of the aircraft. In this context, it is possible that the history of failures related to the pitch trim system has not been registered.
- Piloting judgment – undetermined
Moments prior to takeoff, it was recorded in the CVR speeches related to the flight without the autopilot, possibly related to a failure or inoperativeness of the primary pitch trim system. The takeoff with a possible failure in the pitch trim system of the aircraft, showed an inadequate assessment of the risks involved in the operation under those conditions.
- Aircraft maintenance – undetermined
It was not possible to establish a link between the maintenance services performed on the aircraft in September 2015 and the events that resulted in the accident occurred on 10NOV2015. However, it was not ruled out that an incomplete crash survey was carried out in the pitch trim system of the aircraft, due to the lack of detail of the service orders.
- Decision-making process – a contributor
The sounds related to the test positions of the Rotary Test Switch have not been recorded in the CVR recording, so it is possible to conclude that the Warning Systems - Check item of the Cockpit Preparation Checklist has not been performed. The decision to perform the flight without the complete execution of all items of the Cockpit Preparation Checklist, prevented the correct verification of the primary longitudinal Trim system of the aircraft and reflected an inadequate judgment about the risks involved in that operation.
- Interpersonal relationship – undetermined
According to the CVR data, there was a possible rush of the crew to take-off, even though it was verified that the aircraft's pitch trim system did not work properly. It was not possible to determine if this rush was motivated by passengers’ pressure or self-imposed by the pilot.
- Support systems – undetermined
It is possible that the Pilots' Abbreviated Checklist - NORMAL PROCEDURES, aboard the aircraft, was outdated, without the incorporation of the Stabilizer Trim Backdrive Monitor - TEST procedure in the Shutdown Checklist. The possible completion of Shutdown Checklist with outdated procedures would have hampered the manufacturer's suggested verification for identification of abnormalities in the aircraft's pitch trim system.
- Managerial oversight – undetermined
The records and control of the operational check flights, both by the maintenance shop and by the operator, prevised in documentation issued by the manufacturer (SB650- 27-53 and ASL650-55-04) were not performed in an adequate manner, indicating possible weaknesses in the supervision of the maintenance activities.
Final Report: