Crash of a Cessna T303 Crusader in Bojacá: 1 killed

Date & Time: Jan 8, 2021 at 1320 LT
Type of aircraft:
Operator:
Registration:
HK-3856-G
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Girardot – Bogotá
MSN:
303-00010
YOM:
1981
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
En route from Girardot to Bogotá-Guaymaral Airport, the twin engine aircraft crashed in unknown circumstances in a wooded and hilly terrain near Bojacá. The pilot, sole on board, was killed.

Crash of a Cessna T303 Crusader in Annecy

Date & Time: Dec 4, 2020 at 1555 LT
Type of aircraft:
Operator:
Registration:
HB-LUV
Flight Type:
Survivors:
Yes
Schedule:
Marseille - Annecy
MSN:
303-00058
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft landed at Annecy-Meythet in poor weather conditions with snow falls. After touchdown, the aircraft was unable to stop within the remaining distance, overran, crossed a road, went through a wooded fence and came to rest. While both passengers aged 26 and 28 were slightly injured, the pilot aged 60 was seriously injured.

Crash of a Cessna T303 Crusader in Lagrangeville: 2 killed

Date & Time: Aug 17, 2019 at 1613 LT
Type of aircraft:
Registration:
N303TL
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Sky Acres - Farmingdale
MSN:
303-00286
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1586
Captain / Total hours on type:
358.00
Aircraft flight hours:
2932
Circumstances:
On August 17, 2019, about 1613 eastern daylight time, a Cessna T303, N303TL, was destroyed when it was involved in an accident in Lagrangeville, New York. The private pilot and one person on the ground were fatally injured. Two passengers and one person on the ground sustained serious injuries, and one person on the ground sustained minor injuries. The airplane was operated as a 14 Code of Federal Regulations Part 91 personal flight. According to the passenger seated in the copilot’s seat, on the morning of the accident the pilot and two passengers departed Republic Airport (FRG) and flew to Orange County Airport (MGJ), Montgomery, New York, where the pilot had a business meeting. After the meeting, they departed MGJ for the return flight to FRG, which included a stop at Sky Acres Airport (44N) in Lagrangeville, New York, to purchase fuel. The passenger reported that the flight from FRG to MGJ and the flight from MGJ to 44N were uneventful. He recalled that the pilot performed an engine runup prior to departing FRG; he did not recall if one was performed prior to the departure from MGJ or prior to the accident flight. The pilot fueled the airplane at 44N, where fuel records indicated he purchased 100 gallons of 100LL aviation fuel. A review of surveillance video revealed that the airplane engines were shut down for about 10 minutes while the pilot and one of the passengers added fuel to both wing tanks. After the fueling, they did not take any fuel samples from the airplane’s sump drains. After the pilot and both passengers boarded the airplane, the pilot made several unsuccessful attempts to start the left engine for about 30 seconds. Next, the pilot attempted to start the right engine several times over a period of about 30 seconds. During the last attempt, the engine started. The left engine was then started after about 10 seconds of engine cranking. No smoke was visible at any time during the engine start attempts. The airplane remained in position with the engines idling for about 2 minutes before it taxied around to the opposite side of the fuel pump and stopped for about 45 seconds with the engines at or near idle. The pilot then taxied from the fuel pump to runway 17 and did not appear to stop for an engine run-up (although the airplane was out of the camera view for about 14 seconds near the end of the taxiway). The pilot performed a rolling takeoff, and the airplane lifted off the runway in the vicinity of the windsock, which was located on the left side of the runway about 2,100 ft from the runway 17 threshold. According to the passenger in the copilot’s seat, shortly after liftoff at an altitude of less than 50 to100 ft, both engines lost partial power. They did not stop completely but sounded as though they were “not getting full RPM.” The engines began “stuttering,” which continued until impact with the house. As the airplane proceeded down the runway, it began to drift toward the left until they were over the grass next to the runway. The pilot corrected the drift and the airplane then tracked straight and remained over the grass. As the airplane continued beyond the end of the runway, it was not climbing, and the passenger noticed obstacles that he described as trees and a structure or building. The pilot pitched the airplane up to clear those obstacles. The airplane then began a left turn and as it reached the house the left wing struck the ground, and the right wing struck a tree and the house. The airplane had “very little forward motion” after the initial impact. The passenger estimated that the airplane remained below 100 ft of altitude for the entire flight. He reported that the pilot continued to fly the airplane until impact and did not make any radio calls or say anything to the passengers. He did not hear any warning bells or alarms during the flight. The pilot and both passengers wore their seatbelts and shoulder harnesses. The airport manager who was mowing the grass at the airport described the airplane’s rotation as “very abrupt” compared to other light twin airplanes he has observed taking off at the airport. Immediately after rotation, he noticed the airplane maintained very shallow bank angles; however, the nose was “high”, and the airplane appeared to yaw slightly to the left. The airplane appeared to correct toward the right before he lost sight of it behind the airport fuel tank. When the airplane emerged from the other side of the tank, the nose was initially lower, but then it pitched up again near the end of the runway before it disappeared behind some trees. The airport manager was wearing ear protection and listening to music and did not hear any engine noise. Another witness reported that the airplane was “went in a straight line for a short distance and then quickly turned left about 40-45°” which she described as appearing “deliberate and controlled.” She added that she was “surprised the left wing didn’t dip down as the airplane turned. The wings looked like they were steady and pretty parallel to the ground during and after the turn.” A review of Federal Aviation Administration (FAA) recorded automatic dependent surveillance – broadcast data revealed that after the airplane reached the end of the runway, it climbed from about 675 ft to 775 ft pressure altitude (about 20 to 120 ft above ground level [agl]) in a gradual left turn. During this time the calculated groundspeed decreased from about 80 knots to about 69 knots. The pressure altitude then decreased to 725 ft (about 50 ft agl), the calculated groundspeed decreased to about 66 knots, and the left turn decreased in radius until the recorded data ended about 100 ft west of the accident site.
Final Report:

Crash of a Cessna T303 Crusader in Batesland

Date & Time: Apr 24, 2018 at 1000 LT
Type of aircraft:
Operator:
Registration:
N9746C
Flight Phase:
Survivors:
Yes
Schedule:
Aberdeen - Pine Ridge
MSN:
303-00210
YOM:
1983
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5655
Captain / Total hours on type:
4403.00
Aircraft flight hours:
8929
Circumstances:
Before the air taxi flight, the commercial pilot obtained a weather briefing via the company computer system and reviewed the weather information with the company chief pilot. The pilot stated that based on the computer briefing, which did not include icing conditions, he was aware of the forecasted weather conditions along the route of flight and at the intended destination. However, the briefing was incomplete as it did not contain any in-flight weather advisories, which would have alerted the pilot of moderate icing conditions expected over the flight route in the form of AIRMET Zulu. After takeoff and during the climb to 12,000 ft mean sea level (msl), the airplane encountered light rime ice, and the pilot activated the de-ice equipment with no issues noted. After hearing reports of better weather at a lower altitude, the pilot requested a descent to between 5,000 and 6,000 ft. During the descent to 6,000 ft msl and with the airplane clear of ice, the airplane encountered light to moderate icing conditions. The pilot considered turning back to another airport but could not get clearance until the airplane was closer to his destination. Shortly thereafter, the pilot stated that it felt “like a sheet of ice fell on us” as the airplane encountered severe icing conditions. The pilot applied full engine power in an attempt to maintain altitude. The airplane exited the overcast cloud layer about 500 ft above ground level. The pilot chose to execute an off-airport emergency landing because the airplane could not maintain altitude. During the landing, the landing gear separated; the airplane came to rest upright and sustained substantial damage to the wings and fuselage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and that the airplane was within its maximum gross weight. Structural icing was observed on the airframe after the landing. Based on the weather information, which indicated the probability of icing between 5,000 and 9,000 ft over the region and a high threat of supercooled large droplets between 5,000 and 7,000 ft, it is likely that the airplane, which was equipped for flight in icing conditions, inadvertently encountered severe icing conditions consistent with supercooled large droplets, which resulted in structural icing that exceeded the airplane’s capabilities to maintain altitude.
Probable cause:
The airplane’s inadvertent encounter with severe icing conditions during descent, which resulted in structural icing, the pilot’s inability to maintain altitude, and an emergency landing. Contributing to the accident was an incomplete preflight weather briefing.
Final Report:

Crash of a Cessna T303 Crusader in Serranía del Baudó: 1 killed

Date & Time: Jun 20, 2015 at 1305 LT
Type of aircraft:
Registration:
HK-4677-G
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Nuquí – Quibdo
MSN:
303-00189
YOM:
1982
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2322
Aircraft flight hours:
6491
Circumstances:
The twin engine airplane departed Nuquí Airport at 1256LT on a flight to Quibdó, carrying two passengers and one pilot. Two minutes after takeoff, the pilot informed ATC he was flying at an altitude of 1,500 feet and estimated his ETA at Quibdó-El Caraño Airport at 1315LT. Nine minutes into the flight, while cruising in IMC conditions, the aircraft contacted trees and crashed in a dense wooded area located near Serranía del Baudó, some 50 km north of Nuquí. SAR operations were initiated but the wreckage was found five days later only. Both passengers, a female aged 18 and her baby aged 8 months were evacuated with minor injuries while the pilot was killed. The aircraft was totally destroyed by impact forces.
Probable cause:
The accident was the consequence of a controlled flight into terrain following the decision of the pilot to continue under VFR mode in IMC conditions.
The following contributing factors were identified:
- Poor risk assessment when planning a flight in VFR conditions over a mountainous area, even though the weather conditions were unfavorable.
- Loss of situational awareness after entering the mountain area under VFR mode in IMC conditions, resulting in a CFIT.
Final Report:

Crash of a Cessna T303 Crusader in Barcelonnette

Date & Time: Mar 15, 2014 at 0945 LT
Type of aircraft:
Operator:
Registration:
N303W
Flight Type:
Survivors:
Yes
Schedule:
Cannes – Barcelonnette
MSN:
303-00227
YOM:
1983
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3950
Captain / Total hours on type:
280.00
Circumstances:
Following an uneventful flight from Cannes-Mandelieu Airport, the pilot initiated the approach to Barcelonnette-Saint-Pons Airport Runway 27. Following an unstabilized approach, the aircraft landed hard, causing the left main gear to collapse. The aircraft veered off runway to the left, lost its right main gear and came to rest. There was no fire. All five occupants escaped uninjured and the aircraft was damaged beyond repair.
Probable cause:
The accident was the consequence of the decision of the pilot to continue an unstabilized approach, resulting in a hard landing and the rupture of the left main gear upon touchdown.
Final Report:

Crash of a Cessna T303 Crusader off Jersey: 2 killed

Date & Time: Sep 4, 2013 at 1013 LT
Type of aircraft:
Operator:
Registration:
N289CW
Flight Type:
Survivors:
No
Schedule:
Dinan - Jersey
MSN:
303-00032
YOM:
1981
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
524
Captain / Total hours on type:
319.00
Circumstances:
The aircraft was on a VFR flight from Dinan, France, to Jersey, Channel Islands and had joined the circuit on right base for Runway 09 at Jersey Airport. The aircraft turned onto the runway heading and was slightly left of the runway centreline. It commenced a descent and a left turn, with the descent continuing to 100 ft. The pilot made a short radio transmission during the turn and then the aircraft’s altitude increased rapidly to 600 ft before it descended and disappeared from the radar. The aircraft probably stalled in the final pull-up manoeuvre, leading to loss of control and impact with the sea, fatally injuring those on board, Carl Whiteley and his wife.
Probable cause:
The accident was probably as a result of the pilot’s attempt to recover to normal flight following a stall or significant loss of airspeed at a low height, after a rapid climb manoeuvre having become disoriented during the approach in fog.
Final Report:

Crash of a Cessna T303 Crusader in Louisa: 1 killed

Date & Time: Mar 4, 2010 at 1245 LT
Type of aircraft:
Registration:
N9305T
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Manassas - Louisa - Danville
MSN:
303-00001
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2255
Aircraft flight hours:
1374
Circumstances:
During takeoff, one witness noted that at least one engine seemed to be running rough and not making power. Several other witnesses, located about 1/2 mile northwest of the airport, observed the accident airplane pass overhead in a right turn. They reported that the engine noise did not sound normal. Two of the witnesses noted grayish black smoke emanating from the airplane. The airplane then rolled left and descended nose down into the front yard of a residence. Review of maintenance records revealed the airplane underwent an annual inspection and extensive maintenance about 3 months prior to the accident. One of the maintenance issues was to troubleshoot the right engine that was reportedly running rough at cruise. During the maintenance, the right engine fuel pump, metering valve, and fuel manifold were removed and replaced with overhauled units. Additionally, the right engine fuel flow was reset contrary to procedures contained in an engine manufacturer service information directive; however, the fuel pump could not be tested due to thermal damage and the investigation could not determine if the fuel flow setting procedure contributed to the loss of power on the right engine. On-scene examination of the wreckage and teardown examination of both engines did not reveal any preimpact mechanical malfunctions. Teardown examination of the right propeller revealed that the blades were not at or near the feather position, which was contrary to the emergency procedure published by the manufacturer, to secure the engine and feather the propeller in the event of an engine power loss. The right propeller exhibited signatures consistent with low or no power at impact, while the left propeller exhibited signatures consistent of being operated with power at impact.
Probable cause:
The pilot's failure to maintain aircraft control and secure the right engine during a loss of engine power after takeoff. Contributing to the accident was the loss of engine power on the right engine for undetermined reasons.
Final Report:

Crash of a Cessna T303 Crusader in Punta Ocote: 1 killed

Date & Time: Dec 5, 2009 at 1830 LT
Type of aircraft:
Operator:
Registration:
HK-4324-G
Flight Type:
Survivors:
Yes
MSN:
303-00019
YOM:
1981
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Sole on board, the pilot was performing an illegal flight with a bag containing 25 kg of cocaine. While trying to land on a private airstrip in Punta Ocote, the twin engine aircraft hit tree tops and crashed on a road, killing an 18 years old motorcyclist. The aircraft was destroyed by a post crash fire and the pilot escaped uninjured.