Crash of a Cessna 208B Grand Caravan in Kampala

Date & Time: May 12, 2023 at 1219 LT
Type of aircraft:
Operator:
Registration:
5X-RBR
Flight Type:
Survivors:
Yes
Schedule:
Kampala - Mweya
MSN:
208B-1291
YOM:
2007
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Kampala-Kajjansi Airport, the crew encountered technical issues and elected to return for an emergency landing. Upon touchdown, the single engine airplane went out of control, lost its left wing and engine before coming to rest upside down in a grassy area. Both pilots were rescued, the copilot was slightly injured and the captain was seriously injured. The crew departed Kajjansi Airfield on a positioning flight to Mweya to pick up passengers to Entebbe.

Crash of a Pilatus PC-12/47E in Whitehorse

Date & Time: Apr 17, 2023 at 1039 LT
Type of aircraft:
Operator:
Registration:
C-GMPX
Flight Type:
Survivors:
Yes
Schedule:
Whitehorse – Yellowknife
MSN:
1017
YOM:
2008
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot departed Whitehorse-Erik Nielsen Airport Runway 32L on a positioning flight to Yellowknife. Shortly after takeoff, he declared an emergency and attempted to return. On short final, he lost control of the airplane that crashed within the airport boundary. The pilot was seriously injured and the airplane was destroyed.

Crash of a Cessna 750 Citation X in Monmouth

Date & Time: Apr 1, 2023 at 1935 LT
Type of aircraft:
Operator:
Registration:
N85AV
Flight Type:
Survivors:
Yes
Schedule:
Nashville - Monmouth
MSN:
750-0085
YOM:
1999
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a positioning flight from Nashville International Airport. After landing on runway 32 at Monmouth Airport, the crew started the braking procedure when the airplane deviated from the runway centerline to the left. It veered off runway to the left, crossed the parallel taxiway, lost its left main gain and nose gear and eventually came to rest perpendicular to the runway. Both pilots escaped uninjured. Referring to the photos, it appears that only the left reverser deployed.

Crash of a Cessna 401 in Tapachula: 1 killed

Date & Time: Oct 19, 2021 at 0712 LT
Type of aircraft:
Operator:
Registration:
XB-RQE
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Tapachula – Ocosingo
MSN:
401-0268
YOM:
1969
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Shortly after takeoff from Tapachula Airport Runway 05, while in initial climb, the pilot reported engine problems when control was lost. The aircraft crashed in a mango plantation. The aircraft was totally destroyed by impact forces and the pilot, sole on board, was killed.

Crash of a Cessna 208B Grand Caravan in Marsabit: 2 killed

Date & Time: Mar 20, 2021 at 1000 LT
Type of aircraft:
Operator:
Registration:
5Y-JKN
Flight Type:
Survivors:
No
Site:
Schedule:
Nairobi – Marsabit
MSN:
208B-0688
YOM:
1998
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4235
Captain / Total hours on type:
2329.00
Copilot / Total flying hours:
344
Copilot / Total hours on type:
104
Aircraft flight hours:
16343
Circumstances:
The report describes the accident to C208B type of aircraft, registration 5Y-JKN with two crew on onboard that occurred on Marsabit Hill on 20th March 2021 in which the aircraft crashed killing two crew onboard. The aircraft with 2200lbs fuel onboard was chartered to ferry Marsabit County Officials to a peace keeping mission at Illeret 156 nautical miles North West of Marsabit town. Preliminary information revealed that the aircraft departed Wilson Airport at 08.20am (0520Z) and arrived within the vicinity of Marsabit town at around 10.00a.m (0700Z). It collided with Kofia Mbaya Hill - Marsabit terrain while attempting to approach Marsabit airstrip. The aircraft first impacted the terrain with its nose-wheel and the main landing gears leaving parts of the fuselage and iron box with its content kept in the lower baggage compartment on the sport. It then ballooned and missed a house before it flipped upside down and impacted the ground and came to rest facing opposite direction. It left a trail of aircraft parts along its path before it came to rest. The nosewheel and its assembly separated and fell off and was found next to the house 110m from its first point of impact. There was no fire after impact but all the occupants received fatal injuries.

Crash of a Beechcraft 200 Super King Air in Rockford: 1 killed

Date & Time: Aug 20, 2020 at 1542 LT
Operator:
Registration:
N198DM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Rockford - DuPage
MSN:
BB-1198
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3650
Aircraft flight hours:
8018
Circumstances:
On August 20, 2020, about 1542 central daylight time, a Beech B200 airplane (marketed as a King Air 200), N198DM, was destroyed when it was involved in an accident near Rockford, Illinois. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 positioning flight. The purpose of the flight was to relocate the airplane to the pilot's home base at the DuPage Airport (DPA), West Chicago, Illinois. The airplane had been at Chronos Aviation, LLC (a 14 CFR Part 145 repair station), at the Rockford International Airport (RFD), Rockford, Illinois, for maintenance work. Multiple airport-based cameras recorded the accident sequence. The videos showed the airplane taking off from runway 19. Shortly after liftoff, the airplane started turning left, and the airplane developed a large left bank angle as it was turning. The airplane departed the runway to the left and impacted the ground. During the impact sequence, an explosion occurred, and there was a postimpact fire. A video study estimated the airplane’s maximum groundspeed during the takeoff as 105.5 knots (kts). Data recovered from an Appareo Stratus device onboard the airplane showed that about 1538, the airplane began taxing to runway 19. At 1540:34, the airplane crossed the hold short line for runway 19. At 1541:19, the airplane began a takeoff roll on runway 19. At 1541:42, the airplane began to depart the runway centerline to the left of the runway. Subsequent tracklog points showed the airplane gaining some altitude, and the tracklog terminated adjacent to a taxiway in a grassy area. The Appareo Stratus data showed the airplane began to increase groundspeed on a true heading of roughly 185° about 1541. Airplane pitch began to increase at 1541:41 as the groundspeed reached about 104 kts. The groundspeed increased to 107 kts within the next 2 seconds, and the pitch angle reached around 4° nose-up at this time. In the next few seconds, pitch lowered to around 0° as the groundspeed decayed to around 98 kts. The pitch then became 15° nose-up as the groundspeed continued to decay to about 95 kts. A right roll occurred of about 13° and changed to a rapidly increasing left roll over the next 5 seconds. The left roll reached a maximum of about 86° left as the pitch angle increasingly became negative (the airplane nosed down). The pitch angle reached a maximum nose down condition of -73°. The data became invalid after 1541:53.4. An airplane performance study based on the Appareo Stratus data showed that during the takeoff from runway 19, the airplane accelerated to a groundspeed of 98 kts and an airspeed of 105 kts before rotating and lifting off. The airplane pitched up, climbed, and gained height above the ground. Then, 4 seconds after rotation, the airplane began descending and slowing, consistent with a loss of power. A nose-left sideslip, a left side force, and a left roll were recorded, consistent with the loss or reduction in thrust of the left engine. The sideslip was reduced, likely due to opposite rudder input, and the airplane briefly rolled right. The airplane pitched up and was able to begin climbing again; however, it continued to lose speed. The sideslip then reversed, and the airplane rolled left again and impacted the ground. One witness reported that he observed the accident sequence. He did not hear any abnormal engine noises, nor did he see any smoke or flames emit from the airplane before impact. The airplane came to rest on a flat grass field to the east of runway 19 on airport property. The airplane sustained fire damage and was fragmented from impacting terrain.
Probable cause:
The pilot’s failure to maintain airplane control following a reduction of thrust in the left engine during takeoff. The reason for the reduction in thrust could not be determined based on the available evidence.
Final Report:

Crash of a Pilatus PC-12/47 in Mesquite

Date & Time: Apr 23, 2020 at 1600 LT
Type of aircraft:
Operator:
Registration:
N477SS
Flight Type:
Survivors:
Yes
Schedule:
Dallas – Muscle Shoals
MSN:
813
YOM:
2007
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2283
Captain / Total hours on type:
1137.00
Aircraft flight hours:
7018
Circumstances:
Shortly after takeoff the pilot reported to the air traffic controller that he was losing engine power. The pilot then said he was going to divert to a nearby airport and accepted headings to the airport. The pilot then reported the loss of engine power had stabilized, so he wanted to return to his departure airfield. A few moments later the pilot reported that he was losing engine power again and he needed to go back to his diversion airport. The controller reported that another airport was at the pilot’s 11 o’clock position and about 3 miles. The pilot elected to divert to that airport. The airplane was at 4,500 ft and too close to the airport, so the pilot flew a 360° turn to set up for a left base. During the turn outbound, the engine lost all power, and the pilot was not able to reach the runway. The airplane impacted a field, short of the airport. The airplane’s wings separated in the accident and a small postcrash fire developed. A review of the airplane’s maintenance records revealed maintenance was performed on the day of the accident flight to correct reported difficulty moving the Power Control Lever (PCL) into reverse position. The control cables were inspected from the pilot’s control quadrant to the engine, engine controls, and propeller governor. A static rigging check of the PCL was performed with no anomalies noted. Severe binding was observed on the beta control cable (propeller reversing cable). The cable assembly was removed from the engine, cleaned, reinstalled, and rigged in accordance with manufacturer guidance. During a post-accident examination of the engine and propeller assembly, the beta control cable was found mis-rigged and the propeller blades were found in the feathered position. The beta valve plunger was extended beyond the chamfer face of the propeller governor, consistent with a position that would shut off oil flow from the governor oil pump to the constant speed unit (CSU). A wire could be inserted through both the forward and aft beta control cable clevis inspection holes that function as check points for proper thread engagement. The forward beta control cable clevis adjustment nut was rotated full aft. The swaging ball end on the forward end of the beta control cable was not properly secured between the clevis rod end and the push-pull control terminal and was free to rotate within the assembly. Before takeoff, the beta valve was in an operational position that allowed oil flow to the CSU, resulting in normal propeller control. Vibration due to engine operation and beta valve return spring force most likely caused the improperly secured swaging ball to rotate (i.e. “unthread”) forward on the beta control cable. The resulting lengthening of the reversing cable assembly allowed the beta valve to stroke forward and shut off oil flow to the propeller CSU. Without propeller servo oil flow to maintain propeller control, the propeller faded to the high pitch/feather position due to normal leakage in the transfer bearing. The reported loss of power is consistent with a loss of thrust due to the beta control cable being mis-rigged during the most recent maintenance work.
Probable cause:
The loss of engine power due to a mis-rigged beta control cable (propeller reversing cable), which resulted in a loss of thrust inflight.
Final Report:

Crash of a Beechcraft C90GT King Air near Caieiras: 1 killed

Date & Time: Dec 2, 2019 at 0602 LT
Type of aircraft:
Operator:
Registration:
PP-BSS
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Jundiaí – Campo de Marte
MSN:
LJ-1839
YOM:
2008
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6000
Captain / Total hours on type:
211.00
Circumstances:
The pilot departed Jundiaí-Comandante Rolim Adolfo Amaro Airport at 0550LT on a short transfer flight to Campo de Marte, São Paulo. While descending to Campo de Marte Airport, he encountered poor weather conditions and was instructed by ATC to return to Jundiaí. Few minutes later, while flying in limited visibility, the twin engine airplane impacted trees and crashed in a wooded area located in Mt Cantareira, near Caieiras. The aircraft was destroyed by impact forces and a post crash fire and the pilot, sole on board, was killed.
Probable cause:
The accident was the consequence of the combination of the following factors:
- Attention – undetermined.
It is likely that the pilot has experienced a lowering of his attention in relation to the available information and the stimuli of that operational context in face of the adverse conditions faced.
- Attitude – a contributor.
It was concluded that there was no reaction to the warnings of proximity to the ground (Caution Terrain) and evasive action to avoid collision (Pull Up), a fact that revealed difficulties in thinking and acting in the face of an imminent collision condition, in which the aircraft was found.
- Adverse meteorological conditions – a contributor.
The clouds height and visibility conditions did not allow the flight to be conducted, up to SBMT, under VFR rules.
- Piloting judgment – a contributor.
The attempt to continue with the visual flight, without the minimum conditions for such, revealed an inadequate assessment, by the pilot, of parameters related to the operation of the aircraft, even though he was qualified to operate it.
- Perception – a contributor
The ability to recognize and project hazards related to continuing flight under visual rules, in marginal ceiling conditions and forward visibility, was impaired, resulting in reduced pilot situational awareness, probable geographic disorientation, and the phenomenon known as " tunnel vision''.
- Decision-making process – a contributor.
The impairment of the pilot's perception in relation to the risks related to the continuation of the flight in marginal safety conditions negatively affected his ability to perceive, analyze, choose alternatives and act appropriately due to inadequate judgments and the apparent fixation on keeping the flight under visual rules, which also contributed to this occurrence.
Final Report:

Crash of a Cessna 560XL Citation Excel in Aligarh

Date & Time: Aug 27, 2019 at 0840 LT
Operator:
Registration:
VT-AVV
Flight Type:
Survivors:
Yes
Schedule:
New Delhi - Aligarh
MSN:
560-5259
YOM:
2002
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5484
Captain / Total hours on type:
1064.00
Copilot / Total flying hours:
1365
Copilot / Total hours on type:
1060
Aircraft flight hours:
7688
Circumstances:
On 27 Aug 19, M/s Air Charter Services Pvt Ltd Cessna Citation 560 XL aircraft (VTAVV), while operating a flight from Delhi to Aligarh (Dhanipur Airstrip) was involved in an accident during landing on runway 11.The operator is having a maintenance facility at Aligarh Airport and aircraft was scheduled to undergo ADS-B modification. There were 02 cockpit crew and 04 SOD onboard the aircraft. The aircraft was under the command of a PIC, who was an ATPL holder duly qualified on type with a CPL holder co-pilot, duly qualified on type as Pilot Monitoring. This was the first flight of the day for both pilots. Both, PIC and Co-Pilot had prior experience of operating to Aligarh airport, which is an uncontrolled airport. As per the flight plan, ETD from Delhi was 0800 IST and ETA at Aligarh was 0820 IST. The crew had reported around 0630 IST at Delhi airport and underwent BA test. The MET report to operate the aircraft to Aligarh was well within the VFR conditions. The aircraft Take-off weight was within limits including 1900 Kgs of fuel on board. As per the statement of PIC, the Co-pilot was briefed about pre departure checklists including METAR before approaching the aircraft. Once at the aircraft, prefight checks were carried out by PIC before seeking clearance from Delhi delivery (121.95 MHz). Aircraft was accorded start up clearance by Delhi ground (121.75 Mhz) at 0800 IST.ATC cleared the aircraft to line up on runway 11 and was finally cleared for takeoff at 0821 IST. After takeoff, aircraft changed over to Delhi radar control from tower frequency for further departure instructions. Aircraft was initially cleared by Radar control to climb to FL090 and was given straight routing to Aligarh with final clearance to climb to FL130. Thereafter, aircraft changed to Delhi area control for further instructions. While at approximately 45 Nm from Aligarh, VT-AVV made contact with Aligarh (personnel of M/s Pioneer Flying Club manning radio) on 122.625 MHz. Ground R/T operator informed “wind 100/2-3 Kts, QNH 1005, Runway 11 in use” and that flying of Pioneer Flying Club is in progress. Further, he instructed crew to contact when at 10 Nm inbound. After obtaining initial information from ground R/T operator, VT-AVV requested Delhi area control for descent. The aircraft was cleared for initial descent to FL110 and then further to FL080. On reaching FL080, aircraft was instructed by Delhi area control to change over to Aligarh for further descent instruction in coordination with destination. At approx 10 Nm, VT-AVV contacted ground R/T operator on 122.625 MHz and requested for long finals for runway 11. In turn, ground R/T operator asked crew to report when at 5 Nm inbound. As per PIC, after reaching 5 Nm inbounds, Aligarh cleared VTAVV to descend to circuit altitude and land on runway 11. Aircraft had commenced approach at 5 Nm at an altitude of 2200 ft. Approach and landing checks briefing including wind, runway in use were carried out by PIC. During visual approach, Co-pilot called out to PIC “Slightly low on profile”. As per PIC, Co-pilot call out was duly acknowledged and ROD was corrected. Thereafter, PIC was visual with runway and took over controls on manual. Co-pilot was monitoring instruments and parameters. While PIC was focused on landing, a loud bang from left side of the aircraft was heard by PIC when the aircraft was below 100 feet AGL. Aircraft started pulling towards left and impacted the ground short of runway 11 threshold. After impact, aircraft veered off the runway and its left wing caught fire. The aircraft stopped short of airfield boundary wall. Crew carried out emergency evacuation. Co-pilot opened main exit door from inside of the aircraft for evacuation of passengers. Aircraft was destroyed due to post crash fire. The fire tender reached the crash site after 45 Minutes.
Probable cause:
While landing on runway 11, aircraft main landing gears got entangled in the powerline crossing extended portion of runway , due to which aircraft banked towards left and crash landed on extended portion of runway 11.
Contributory factors:
- It appears that there was a lack of proper pre-flight briefing, planning, preparation and assessment of risk factors.
- Non-Adherence to SOP.
- Sense of complacency seems to have prevailed.
Final Report:

Crash of a Cessna 560 Citation Encore in the Atlantic Ocean: 1 killed

Date & Time: May 24, 2019 at 1755 LT
Type of aircraft:
Operator:
Registration:
N832R
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Saint Louis - Fort Lauderdale
MSN:
560-0585
YOM:
2001
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
9016
Aircraft flight hours:
4744
Circumstances:
The airline transport pilot departed on a repositioning flight in the jet airplane. The airplane was in level cruise flight at 39,000 ft mean sea level when the pilot became unresponsive to air traffic controllers. The airplane continued over 300 miles past the destination airport before it descended and impacted the Atlantic Ocean. Neither the pilot nor the airplane were recovered, and the reason for the airplane's impact with water could not be determined based on the available information.
Probable cause:
Impact with water for reasons that could not be determined based on the available information.
Final Report: