Crash of a Cessna 207 Skywagon near Playa del Carmen

Date & Time: Dec 21, 2017 at 0950 LT
Operator:
Registration:
XA-UHL
Flight Phase:
Survivors:
Yes
Schedule:
Playa del Carmen – Chichén Itzá
MSN:
207-0261
YOM:
1974
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1506
Captain / Total hours on type:
37.00
Aircraft flight hours:
5090
Circumstances:
Few minutes after takeoff from Playa del Carmen, while flying at an altitude of 1,500 feet, the engine lost power and failed. The pilot attempted to make an emergency landing when the aircraft collided with trees and crashed in a wooded area located 18 km from its departure point. The pilot and all four passengers, a British family on vacations, were uninjured. The aircraft was damaged beyond repair.
Probable cause:
Engine failure caused by an oil leak following the failure of the 5th cylinder.
Final Report:

Crash of a Cessna 208B Grand Caravan off Placencia

Date & Time: Nov 17, 2017 at 0846 LT
Type of aircraft:
Operator:
Registration:
V3-HGX
Flight Phase:
Survivors:
Yes
Schedule:
Placencia – Punta Gorda
MSN:
208B-1162
YOM:
2005
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
19040
Captain / Total hours on type:
12092.00
Aircraft flight hours:
2106
Circumstances:
On 17 November, 2017, a Tropic Air Cessna 208B Grand Caravan with registration V3-HGX, departed from the Sir Barry Bowen Municipal Airport at approximately 7:15 a.m. local time with one aircraft captain, 11 passengers and 1 crew on board. The flight was a regular operated commercial passenger flight with scheduled stops in Dangriga, Placencia and with the final destination being Punta Gorda. The pilot reported that the portion of the flight from Belize City to Dangriga was uneventful and normal and so was the landing at Placencia. At approximately 8:40 a.m. local time the airplane taxied from the Tropic Air ramp and taxied towards the west on runway 25. The pilot did a turnaround using all the available runway at normal speed and started his takeoff run to the east on runway 07. The pilot proceeded down the runway in a normal takeoff roll with normal takeoff speed and prior to reaching the end of the runway, he rotated the aircraft and lifted the nose wheel to get airborne. At exactly 28 feet past the end of runway 07 and during the initial climb phase, a part of the aircraft landing gear made contact with the upper part of the front righthand passenger door frame of a vehicle that had breached the area in front of the runway which is normally protected by traffic barriers. The impact caused the aircraft to deviate from its initial climb profile, and the pilot reported that the engine was working for a couple seconds and it abruptly shut down shortly after. The pilot realized that he was unable to return to the airport. The pilot carried out emergency drills for engine loss after take-off over water and decided to ditch the aircraft in the sea, which was approximately 200-300 feet from the main shoreline in front of the Placencia airport. The flight crew and all passengers were safely evacuated from the fuselage with the assistance of witnesses and passing boats which provided an impromptu rescue for the passengers. All passengers received only minor injuries.
Probable cause:
The following are factors that are derived from the failures in the areas mentioned in section 3.00 (conclusions):
a. There is a lack of traffic surveillance to ensure that drivers comply with the warning signs of low flying aircraft and do not breach the barriers when they are down or inoperative. The left barrier at Placencia was reportedly inoperative and the right barrier was said to be working. As a result, this removed a significant level of protection for vehicles which operate on the portion of the road which intersects the departure path of aircraft. The purpose of the barriers is to protect vehicles from coming in close contact with low flying aircraft. The driver of the vehicle failed to adhere to traffic warning signs regarding low flying aircraft and drove his vehicle directly into the departure path of an aircraft (Probable cause).
b. ADAS data calculations showed that the pilot had a period of 13.33 seconds when he achieved take off performance, but he did not rotate the aircraft. Although the aircraft engine performance was normal, the actual take-off weight was within limits and the distance available to the pilot to abort the take-off was 872 feet; the pilot still flew the aircraft at a dangerously low altitude over the road and did not properly assess the risk at hand which was a vehicle advancing into the aircraft’s departure path which could cause a collision. (Probable cause).
c. The angle at which the aircraft made contact with the vehicle was not a direct head on angle, but the contact was made when the vehicle was off to the right-hand side of the extended centerline of runway 07. The aircraft did not follow the direct path of the extended center line of runway 07 prior to making contact, but instead it made a slight right turn shortly after the wheels left the ground. The pilot did not take collision avoidance (evasive) measures in a timely manner (probable cause).
d. The pilot did not demonstrate adequate knowledge of proper ditching procedures which led to an inadequate response to the emergency at hand. The operator did not provide the flight crew with the proper ditching training.

Probable causes:
1. The driver of the vehicle failed to adhere to traffic warning signs regarding low flying aircraft and drove his vehicle directly into the departure path of an aircraft.
2. The pilot flew the aircraft at a dangerously low altitude over the road and did not properly assess the risk at hand which was a vehicle advancing into the aircraft’s departure path which could cause a collision.
3. The pilot did not take collision avoidance (evasive) measures in a timely manner.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain near San Vicente: 2 killed

Date & Time: Sep 13, 2017 at 1500 LT
Operator:
Registration:
XB-OUE
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Toluca – Acapulco
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
En route from Toluca to Acapulco, the pilot encountered poor weather conditions. In limited visibility, the twin engine airplane struck hilly and wooded terrain in the Sierra de Chilpancingo, near San Vicente. The aircraft was destroyed by impact forces and a post crash fire and both occupants were killed.

Crash of a Let L-410UVP-E3 in Comayagua: 1 killed

Date & Time: Aug 16, 2017 at 0940 LT
Type of aircraft:
Operator:
Registration:
FAH-322
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Comayagua - Comayagua
MSN:
87 18 27
YOM:
1987
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew was completing a local training flight at Comayagua-Palmerola AFB when the twin engine aircraft crashed in unknown circumstances onto a building. The captain was killed while the copilot and the flight engineer were injured. The aircraft was destroyed.
Crew:
Cpt Olvin Emanuel Florez Meraz, pilot, †
Lt Cesar Augusto Banegas Corea, copilot,
Cdt Brayan Daniel Zavala Amaya, flight mechanic.

Crash of a Swearingen SA227AC Metro III in Tampico

Date & Time: Jun 2, 2017 at 2245 LT
Type of aircraft:
Operator:
Registration:
XA-UAJ
Flight Type:
Survivors:
Yes
Schedule:
Saltillo – Puebla
MSN:
AC-586
YOM:
1984
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3280
Copilot / Total flying hours:
1144
Aircraft flight hours:
35318
Aircraft flight cycles:
43028
Circumstances:
The twin engine aircraft departed Saltillo Airport on a night cargo flight to Puebla, carrying two pilots and a load of 550 kilos of various goods. En route, the crew declared an emergency and reported a low fuel condition before being cleared to divert to Tampico-General Francisco Javier Mina Airport. On final approach, both engines stopped and the aircraft descended into trees and crashed in a wooded area located 850 metres short of runway 31. Both pilots were slightly injured and the aircraft was damaged beyond repair.
Probable cause:
Emergency landing due to an inadequate pre-flight of the aircraft which resulted in the loss of power of both engines during the cruise flight due to exhaustion of fuel on board.
Contributing factors:
- Lack of adherence to flight planning procedures.
- Lack of coordination between captain and operations officer during pre-flight preparation.
- Lack of supervision of dispatcher activities.
Final Report:

Crash of a Learjet 25B in Toluca: 2 killed

Date & Time: May 17, 2017 at 1525 LT
Type of aircraft:
Operator:
Registration:
XA-VMC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Toluca - Durango
MSN:
25-114
YOM:
1973
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Aircraft flight hours:
14654
Aircraft flight cycles:
13449
Circumstances:
During the takeoff roll on runway 15 at Toluca-Licendiado Adolfo López Mateos, after the airplane passed the V1 speed, the warning light came on in the cockpit panel, informing the crew about the deployment of the reverse on the left engine. According to published procedures, the crew continued the takeoff and shortly after rotation, during initiale climb, the aircraft rolled to the left and crashed in an open field, bursting into flames. The wreckage was found about 200 metres past the runway end. The aircraft was destroyed and both pilots were killed.
Probable cause:
Probable Cause:
Loss of control of the aircraft during the emergency procedure of indication of the deployment of the reverse of the engine number one during the takeoff roll above V1, which was consistent with the training and standard operating procedures that call to continue the takeoff, causing the collapse of the aircraft, by low speed and the operation of abrupt maneuvers and turns towards the engine side in idle position and commanded opening of the Drag Shut due to poor CRM.
Contributing factors:
- False indication of reverse display of dwelling position number one.
- Failure of pilots of previous flights not to refer failures to indicate the deployment of reverses for maintenance actions.
Final Report: