Zone

Crash of a Basler BT-67 in Villavicencio

Date & Time: Apr 13, 2022 at 1303 LT
Type of aircraft:
Operator:
Registration:
PNC-0257
Flight Type:
Survivors:
Yes
Schedule:
Florencia – Villavicencio
MSN:
9670
YOM:
1943
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 23 at Villavicencio-La Vanguardia Airport, the airplane veered off runway to the left and entered a grassy area. It rolled for few hundred metres then the pilot attempted to takeoff when the left wing dropped. The aircraft stalled, impacted trees and crashed about 200 metres to the right of the runway 05 threshold. All 14 occupants were rescued, among them few were injured.

Crash of a Douglas DC-3C near Restrepo: 3 killed

Date & Time: Jul 8, 2021 at 0709 LT
Type of aircraft:
Operator:
Registration:
HK-2820
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Villavicencio - Villavicencio
MSN:
20171
YOM:
1944
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
16923
Captain / Total hours on type:
16680.00
Copilot / Total flying hours:
9387
Copilot / Total hours on type:
8170
Aircraft flight hours:
18472
Circumstances:
The twin engine airplane departed Villavicencio-La Vanguardia Airport Runway 05 at 0659LT on a training flight consisting with a proficiency check of the captain. On board were one instructor, one captain and one mechanic. About 10 minutes into the flight, while cruising at an altitude of 6,000 feet over mountainous terrain in Instrument Meteorological Conditions, the airplane impacted trees and crashed on the slope of a hilly terrain located in the region of Restrepo. The wreckage was found three days later. All three crew members were killed.
Probable cause:
Probable causes:
- Controlled flight into terrain during the execution of the IFR departure procedure VVC2A, during which the crew mistakenly turned left, contrary to the procedure, heading towards the mountainous area at the foothills of the eastern range, where the impact occurred.
- Loss of situational awareness by the crew, which, for reasons that could not be determined, apparently made a controlled left turn, contrary to the indications of the VVC2A departure procedure, even though it was an experienced crew familiar with the operating area.

The following contributing factors were identified:
- Lack of operator standards, as there was no detailed, organized, and sequential instructional plan and syllabus for the crew to follow during each maneuver, such as the VVC2A instrument departure.
- Lack of operator standards, as there was no specific syllabus for the planning and execution of the Recurrent Check, taking into account, among other aspects, the composition of the aircraft crew, consisting of two instructor pilots, one of whom was conducting the check on the other.
- Inadequate planning and supervision of the training flight by the operator, as they did not conduct a specific risk analysis of the flight, did not monitor its preparation and execution, did not provide details in a flight order or other document, considering especially the composition of the aircraft crew, consisting of two instructor pilots, one of whom was conducting the check on the other.
- Deficient planning and preparation of the flight by the crew, as they informally changed the VFR Flight Plan to IFR, apparently did not conduct a complete and adequate briefing, were unaware of or did not consider the VVC2A SID for the start of the IFR flight, and omitted several IFR flight procedures.
- Crew's neglect of the following IFR flight procedures:
- Not specifying a route and an IFR departure procedure in the IFR Flight Plan.
- Not requesting complete authorization from ATC to initiate an IFR flight. At no time did they mention the VVC2A departure, which was key to the verbally proposed plan before takeoff.
- Not defining or requesting from ATS which standard departure procedure or other they would use to initiate the IFR flight, in which they would encounter IMC shortly after takeoff.
- Not requiring ATC to assign a transponder code before takeoff or at any other phase of the flight, or selecting code 2000 as they did not receive instructions from ATS to activate the transponder.
- Likely not activating the transponder before takeoff and/or not verifying its correct operation before takeoff or immediately once the aircraft was in the air.
- Inaccurate use of phraseology with non-standard terminology in their transmissions with ATC.
- Insufficient experience and training in IFR flights by the crew, despite their extensive experience with the equipment. Much of this experience had been gained in the eastern region of the country, where the majority of DC3 flights are conducted in VMC and under VFR, with no opportunity for the practical execution of IFR procedures.
- Overconfidence of the crew, influenced by factors such as the high flight experience and DC3 equipment experience of the two pilots in the crew, their status as instructor pilots, the relatively low operational demand of the flight mission, and the knowledge, familiarity, and confidence of both crew members with the aerodrome's characteristics, the surrounding area, and especially the peculiarities and risks of the terrain to the west of the takeoff path.
- Non-observance by air traffic control of the following IFR flight procedures initiated by HK2820:
- Failure to issue complete authorization to the aircraft for the IFR flight before initiating the flight or at any other time.
- Failure to issue a standardized instrument departure, SID, or any other safe departure procedure to the aircraft. At no time did ATC mention the VVC2A departure, which was crucial for carrying out the plan verbally proposed by the crew.
- Failure to provide the aircraft with a transponder code before takeoff or at another appropriate time, or to verify its response. This process started only 03:11 minutes after the aircraft took off, so positive radar contact verification was only achieved 04:58 minutes after takeoff, delaying radar presentation and limiting positive flight control.
- Late transfer of aircraft control from the Control Tower to Approach Control (03:35 minutes after takeoff), not immediately after the aircraft was airborne as it should have been, considering prevailing IMC flight conditions in the vicinity of the aerodrome.
- Operating with an incomplete radar display configuration in Approach Control, with insufficient symbology, depriving control of references and judgment elements for an accurate location of the aircraft and its left turn from the path.
- Failure to observe radar surveillance techniques and procedures.
- Inaccurate use of phraseology with non-standard terminology in their transmissions with the aircraft.
- Lack of situational awareness by both the crew and ATC during a flight that, perhaps because it seemed routine, led both parties to omit elementary IFR flight procedures, disregarding the inherent risks of an operation in IMC conditions, with strict IFR procedures that needed to be followed, considering, among other things, the aerodrome's proximity to a mountainous area.
Final Report:

Crash of a Douglas DC-3 in Finca La Bendición: 14 killed

Date & Time: Mar 9, 2019 at 1036 LT
Type of aircraft:
Operator:
Registration:
HK-2494
Flight Phase:
Survivors:
No
Schedule:
San Jose del Guaviare – Villavicencio
MSN:
33105/16357
YOM:
1945
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
14
Captain / Total flying hours:
12710
Captain / Total hours on type:
7044.00
Copilot / Total flying hours:
12710
Copilot / Total hours on type:
7044
Aircraft flight hours:
23000
Circumstances:
The twin engine airplane departed San José del Guaviare on a charter flight to Villavicencio, carrying 11 passengers and three crew members. While cruising at an altitude of 8,500 feet in good weather conditions, the left engine failed due to an important fuel leak. The crew elected to secure the engine but was unable to feather the propeller. The airplane lost speed and height, and while attempting an emergency landing, the crew lost control of the airplane that stalled and crashed in a palm plantation, bursting into flames. The aircraft was totally destroyed by a post crash fire and all 14 occupants were killed.
Probable cause:
The investigation determined that the accident was caused by the following probable causes:
- Loss of control in-flight as a consequence of the decrease in minimum in-flight control speed and drag generated by the impossibility of performing the No. 1 engine propeller feathering in the face of engine failure.
- Malfunction of the lubrication system of engine No. 1, evident in the abundant oil leakage from the engine, in flight, and in the governor of the left propeller; although discrepancies were found in the maintenance of the propeller feathering pressure line, it was not possible to determine the origin of the oil leakage.
- Weaknesses in the aircraft Operator's operational procedures, lacking a standard that would facilitate a crew's decision making to act in the event of critical failures, in matters such as making an emergency landing on unprepared field or the selection of an alternate airfield.

Contributing Factors:
- Deficiencies in standard maintenance practices during repairs performed on the No. 1 engine's propeller propeller feathering oil pressure line.
- Non-compliance with an effective and reliable maintenance program, which did not verify the operating conditions of the aircraft components; it was not possible to determine compliance with the last 50-hour service, Phase A, to engine No. 1 according to the company's maintenance program, since there are no records of that service in the Flight Log.
- Inefficient safety management system of the Operator for not detecting errors in the maintenance processes and in the conduct and control of operations.
Final Report:

Crash of a Douglas DC-3C in Puerto Gaitán

Date & Time: Apr 6, 2016 at 0625 LT
Type of aircraft:
Operator:
Registration:
HK-2663
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Puerto Gaitán – Villavicencio
MSN:
10210
YOM:
1945
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4058
Copilot / Total flying hours:
7934
Aircraft flight hours:
23291
Circumstances:
Shortly after takeoff from Puerto Gaitán Airport Runway 04, while on a cargo flight to Villavicencio, the left engine exploded and caught fire. As the aircraft was losing speed and height, the crew attempted an emergency landing when the aircraft crash landed in an open field located 2,6 km southwest from the airport, bursting into flames. All three crew members escaped with minor injuries and the aircraft was destroyed by a post crash fire.
Probable cause:
Failure of the left engine following the detachment of the head of a cylinder shortly after takeoff. Deficiencies in maintenance processes contributed to this situation. The crew failed to follow the emergency procedures when the left engine caught fire and exploded, reducing the power on the right engine. In such conditions, the aircraft was unable to maintain a safe altitude and the crew was forced to attempt an emergency landing.
Final Report:

Crash of a Douglas DC-3C near San Vincente del Caguán: 5 killed

Date & Time: May 8, 2014 at 1202 LT
Type of aircraft:
Operator:
Registration:
HK-4700
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Villavicencio – Florencia
MSN:
9700
YOM:
1943
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
10233
Captain / Total hours on type:
9950.00
Copilot / Total flying hours:
4417
Copilot / Total hours on type:
3812
Aircraft flight hours:
27771
Circumstances:
The aircraft departed Villavicencio on a cargo flight to Florencia, carrying three passengers, two pilots and a load consisting of 2,540 kg of various goods. While cruising under VFR mode at an altitude of 6,500 feet, weather conditions worsened and the crew attempted to modify his route when the aircraft impacted ground and crashed in a wooded and mountainous area located some 45 km north of San Vincente del Caguán, near Uribe. The aircraft was destroyed by impact forces and all five occupants were killed.
Probable cause:
It was determined that the accident was the consequence of a controlled flight into terrain. The crew failed to evaluate properly the risks and the danger of poor weather conditions and decided to perform the flight in VFR mode. While cruising in IMC and failing to check the minimum prescribed altitude, the crew suffered a loss of situational awareness, causing the aircraft to hit he mountainous terrain.
Final Report:

Crash of a Beechcraft C90 King Air in Villavicencio: 5 killed

Date & Time: Mar 12, 2014 at 0633 LT
Type of aircraft:
Operator:
Registration:
HK-4921
Flight Type:
Survivors:
No
Schedule:
Bogotá – Araracuara
MSN:
LJ-721
YOM:
1977
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
3013
Captain / Total hours on type:
538.00
Copilot / Total flying hours:
1341
Copilot / Total hours on type:
483
Aircraft flight hours:
9656
Circumstances:
The twin engine aircraft departed Bogotá-El Dorado Airport at 0600LT on an ambulance flight to Araracuara, State of Caquetá, carrying two doctors, one patient and two pilots. Fifteen minutes into the flight, the crew contacted ATC, reported problems and was cleared to divert to Villavicencio. On approach to Villavicencio-La Vanguardia Airport, the aircraft stalled and crashed in a wooded area parallel to a road, bursting into flames. The aircraft was destroyed by a post crash fire and all five occupants were killed.
Probable cause:
The following factors were identified:
- The lack of technical knowledge published in the POH for the execution of the pertinent actions during the failure of the engine in flight, together with the unwise decisions made by the crew in that situation.
- The haste of the crew members to land caused them to act in an uncoordinated manner and without the assertiveness required for the execution of the procedures contemplated by the manufacturer, the navigation charts and the published approach procedures.
- The omissions, reactions and deviations inappropriate to conduct the flight safely to the runway.
- The turning to the runway on the same side of the inoperative (critical) engine and maximum power on the operational engine during the unstabilized approach to the runway threshold which led to loss of control of the aircraft in low altitude flight.
Final Report:

Crash of an Embraer ERJ-145LR in Mitú

Date & Time: May 5, 2010 at 1049 LT
Type of aircraft:
Operator:
Registration:
FAC-1173
Survivors:
Yes
Schedule:
Villavicencio - Mitú
MSN:
145-879
YOM:
2005
Flight number:
NSE9634
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
37
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10254
Captain / Total hours on type:
1060.00
Copilot / Total flying hours:
1061
Copilot / Total hours on type:
806
Aircraft flight hours:
9095
Circumstances:
After landing on runway 20 (1,760 meters long) at Mitú-Fabio Alberto León Bentley Airport, the aircraft encountered difficulties and was unable to stop within the remaining distance. It overran at a speed of 52 knots, went through a fence, lost its undercarriage and came to rest in a prairie some 163 metres further. All 41 occupants were uninjured while the aircraft was damaged beyond repair. It was registered FAC-1173 (military) and HK-4536 (civil).
Probable cause:
Wrong approach configuration on part of the crew. Execution of the landing procedure on runway 20 despite the fact that aircraft was unstable on approach. At runway threshold, the aircraft altitude was too high and its speed upon touchdown was excessive (132 knots). The airplane touched down 562 metres past the runway threshold, well beyond the touchdown zone. All brakes systems were activated but the upper right thrust reverser deployed and retracted shortly later due to technical reasons, which was considered as a contributory factor. The following factors also contributed to the mishap:
- Poor techniques used by the pilot-in-command on approach and after touchdown,
- Deviation from standard operating procedures (SOP),
- Non-adherence to published procedures,
- No reaction or corrective action to the EGPWS alarm.
Final Report:

Crash of a Let L-410UVP-E10A near Cubarral: 17 killed

Date & Time: Oct 8, 2007 at 1550 LT
Type of aircraft:
Operator:
Registration:
HK-4055
Flight Phase:
Survivors:
No
Site:
Schedule:
Villavicencio - Uribe
MSN:
90 25 21
YOM:
1991
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
17
Captain / Total flying hours:
5550
Captain / Total hours on type:
432.00
Copilot / Total flying hours:
287
Copilot / Total hours on type:
134
Aircraft flight hours:
2435
Circumstances:
The twin engine aircraft departed Villavicencio-La Vanguardia Airport at 1530LT on a flight to Uribe with 15 passengers and 2 pilots on board. En route, while cruising in poor weather conditions, the crew reported his ETA in Uribe at 1550LT. At an altitude of 11,800 feet, the aircraft struck the slope of a mountain and disintegrated on impact. The wreckage was found 3 days later on Mt Páramo El Nevado, about 33 km northeast of Cubarral. The aircraft was totally destroyed upon impact and all 17 occupants were killed.
Probable cause:
Controlled flight into terrain after the crew decided to continue the flight under VFR mode in IMC conditions. The following contributing factors were identified:
- Erroneous navigation,
- Low situational awareness regarding the geographical orientation at the beginning and during the flight,
- Failure to observe the warnings of closeness with terrain for three minutes, issued by the TAWS equipment.
Final Report:

Ground fire of an Antonov AN-32B in Mitú

Date & Time: Aug 27, 2007 at 0950 LT
Type of aircraft:
Operator:
Registration:
HK-4117
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Villavicencio – Mitú
MSN:
29 09
YOM:
1992
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft completed a cargo flight from Villavicencio to Mitú, carrying four crew members and a load consisting of fuel drums. After all fuel drums were offloaded by ground crew, the pilot contacted the fire brigade because fuel leaked on the cabin floor and around the aircraft. Airport firefighters approached to attend the event but were not allowed the use or foam or water due to electrical and electronic equipment that could be affected by the liquid. After starting the APU and the right engine for the flight back to Villavicencio, an explosion occurred. The crew shut down the engines and evacuated the aircraft. Firefighters were unable to extinguish the rapidly developing fire and the aircraft was totally destroyed.
Probable cause:
Lack of adequate and effective procedures for fuel handling by the company and crew. Non-compliance by the crew of the aircraft, of the recommendations made by the Fire Fighting Service Airport and Control Tower.
Final Report:

Crash of a Douglas DC-3C in Medellín: 3 killed

Date & Time: Oct 15, 2004 at 0750 LT
Type of aircraft:
Operator:
Registration:
HK-1503
Flight Type:
Survivors:
No
Site:
Schedule:
Villavicencio - Medellín
MSN:
17064/34331
YOM:
1945
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
21490
Captain / Total hours on type:
370.00
Copilot / Total flying hours:
305
Copilot / Total hours on type:
91
Aircraft flight hours:
27592
Circumstances:
The aircraft departed Villavicencio on a cargo flight to Medellin-José María Córdova Airport with one passenger and two pilots on board. While descending to Medellín, the crew was informed about the poor weather conditions at destination (poor visibility due to fog) and decided to divert to Medellín-Enrique Olaya Herrera Airport. On final approach, the aircraft descended too low when it struck a mountain located 13 km short of runway. The aircraft was destroyed and all three occupants were killed.
Probable cause:
Controlled flight into terrain after the crew took the decision to continue the approach under VFR mode in IMC conditions until the aircraft impacted terrain. Poor CRM and lack of situational awareness were considered as contributing factors.
Final Report: