code

LA

Crash of a Piper PA-31T Cheyenne II in Lafayette: 5 killed

Date & Time: Dec 28, 2019 at 0920 LT
Type of aircraft:
Registration:
N42CV
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Lafayette - Atlanta
MSN:
31T-8020067
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
The twin engine airplane departed Lafayette Airport runway 22L at 0918 on a private flight to Atlanta-DeKalb-Peachtree Airport, Georgia, carrying five passengers and one pilot. During initial climb, at an altitude of 375 feet, the airplane entered an uncontrolled descent and crashed near a post office in Lafayette, bursting into flames. Debris scattered on a large area and at least one vehicle (a taxi) was hit. A passenger on the plane as well as three people on the ground were seriously injured while five other occupants in the plane were killed. The aircraft was totally destroyed by impact forces and a post crash fire. It is believed the airplane may struck power cables during initial climb.

Crash of a Piper PA-46-350P Malibu Mirage in Shreveport: 2 killed

Date & Time: Feb 28, 2019 at 1039 LT
Operator:
Registration:
N428CD
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Shreveport - Vernon
MSN:
46-36232
YOM:
1999
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
On February 28, 2019, about 1039 central standard time, a Piper PA-46-350P airplane, N428CD, impacted a river after departing from Shreveport Downtown Airport (DTN), Shreveport, Louisiana. The private pilot and passenger were fatally injured, and the airplane was substantially damaged. The airplane was registered to Lennard Properties LLC and was being operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. The airplane departed on an instrument flight rules flight plan at 1037 during day instrument meteorological conditions, with a destination of Wilbarger Country Airport (F05), Vernon, Texas. The pilot and passenger were flying to a ranch near F05 for a hunting trip. According to preliminary air traffic control (ATC) information, after departing from Runway 32 and reaching 600 ft mean sea level (msl), ATC instructed the pilot to turn left to a heading of 270° and continue climbing to 12,000 ft msl. The airplane turned left continuously for 740 degrees. During this turn, after climbing steadily to 1,400 ft msl, the airplane's altitude began to oscillate between 725 ft and 1,900 ft msl. The airplane subsequently made a decelerating turn to the right and quickly descended, with the last recorded ATC data indicating a ground speed of 31 knots and an altitude of 575 ft msl. The airplane impacted the Red River and came to rest about 17 ft below the river's surface.

Crash of a Piper PA-61 Aerostar (Ted Smith 601) in Baton Rouge

Date & Time: Jul 20, 2018 at 1430 LT
Registration:
N327BK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Baton Rouge - Baton Rouge
MSN:
61-0145-076
YOM:
1973
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
28829
Captain / Total hours on type:
600.00
Aircraft flight hours:
1912
Circumstances:
The aircraft experienced a loss of engine power and landed in a field after takeoff from Baton Rouge Metropolitan Airport (BTR), Baton Rouge, Louisiana. The commercial pilot and one passenger were not injured and the airplane sustained substantial damage. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91 as a maintenance test flight. Visual meteorological conditions prevailed at the time of the accident and no flight plan had been filed. The local flight was departing at the time of the accident. A review of the air traffic control recording revealed that the pilot requested to takeoff from runway 31 and fly one time around the traffic pattern for a maintenance check. The air traffic controller stated that the airplane dropped below the tree line after takeoff and was unable to reach the pilot on the radio. After the accident the pilot stated that he completed a preflight inspection about 1400, then boarded the airplane and started both engines. While holding short of runway 31, he performed a pre-takeoff check of the airplane including a run-up for each engine with no anomalies noted. During the takeoff roll he advanced the throttles to takeoff power, then rotated. Shortly after rotation he noticed the right engine was not producing full power and the engine speed was decreasing. With no remaining runway available to land, he continued and looked for an off field landing location. He retracted the landing gear and feathered the right propeller. The airplane was unable to maintain altitude so the pilot made a hard forced landing to a grass covered field (figure 1) about 1 mile northwest of the departure end of runway 31.

Crash of a McDonnell Douglas MD-83 in Alexandria

Date & Time: Apr 20, 2018 at 1420 LT
Type of aircraft:
Operator:
Registration:
N807WA
Survivors:
Yes
Schedule:
Chicago - Alexandria
MSN:
53093/2066
YOM:
1993
Flight number:
WAL708
Crew on board:
7
Crew fatalities:
Pax on board:
94
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On April 20, 2018, at about 1420 central daylight time, a Caribbean Sun Airlines Inc., dba World Atlantic Airlines, MD83, N807WA, right main landing gear failed during the landing roll at Alexandria International Airport (KAEX), Alexandria, Louisiana. Due to the gear failure, the right wing dragged on the runway creating a friction fire which was quickly put out by the airport rescue and firefighting personnel. The airplane was substantially damaged and there were no injuries to the 101 passengers and crew aboard. The L1 emergency slide did not deploy during the evacuation. The flight was operating under 14 CFR Part 121 as a domestic passenger flight from Chicago-O'Hare International Airport (KORD), Chicago, Illinois, to KAEX.

Crash of a Beechcraft A90 King Air in Slidell: 2 killed

Date & Time: Apr 19, 2016 at 2115 LT
Type of aircraft:
Operator:
Registration:
N7MC
Survivors:
No
Schedule:
Slidell - Slidell
MSN:
LM-106
YOM:
1968
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
18163
Captain / Total hours on type:
614.00
Copilot / Total flying hours:
7769
Copilot / Total hours on type:
22
Aircraft flight hours:
15208
Circumstances:
The airline transport pilot and commercial copilot were conducting a mosquito abatement application flight. Although flight controls were installed in both positions, the pilot typically operated the airplane. During a night, visual approach to landing at their home airfield, the airplane was on the left base leg and overshot the runway's extended centerline and collided with 80-ft-tall power transmission towers and then impacted terrain. Examination of the airplane did not reveal any preimpact anomalies that would have precluded normal operation. Both pilots were experienced with night operations, especially at their home airport. The pilot had conducted operations at the airport for 14 years and the copilot for 31 years, which might have led to crew complacency on the approach . Adequate visibility and moon disk illumination were available; however, the area preceding the runway is a marsh and lacks cultural lighting, which can result in black-hole conditions in which pilots may perceive the airplane to be higher than it actually is while conducting an approach visually. The circumstances of the accident are consistent with the pilot experiencing the black hole illusion which contributed to him flying an approach profile that was too low for the distance remaining to the runway. It is likely that the pilot did not maintain adequate crosscheck of his altimeter and radar altimeter during the approach and that the copilot did not monitor the airplane's progress; thus, the flight crew did not recognize that they were not maintaining a safe approach path. Further, it is likely that neither pilot used the visual glidepath indicator at the airport, which is intended to be a countermeasure against premature descent in visual conditions.
Probable cause:
The unstable approach in black-hole conditions, resulting in the airplane overshooting the runway extended centerline and descending well below a safe glidepath for the runway.
Contributing to the accident was the lack of monitoring by the copilot allowing the pilot to fly well below a normal glidepath.
Final Report:

Crash of a Cessna 421B Golden Eagle II in Hammond: 2 killed

Date & Time: Oct 14, 2015 at 1548 LT
Operator:
Registration:
N33FA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Hammond - Atlanta
MSN:
421B-0502
YOM:
1973
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1370
Circumstances:
The twin-engine airplane, flown by a commercial pilot, was departing on a business flight from runway 31 when the right engine lost power. According to a pilot-rated witness, the airplane was about halfway down the 6,500 ft runway at an altitude of about 100 ft above ground level when he heard a "loud pop" and then saw the airplane's right propeller slow. The witness reported that the airplane yawed to the right and then began a right turn toward runway 18 with the right engine's propeller windmilling. The witness further reported that the airplane cleared a tree line by about 150 ft, rolled right, descended straight down to ground impact, and burst into flames. Postaccident examination of the airplane's right engine revealed that the crankshaft was fractured adjacent to the No. 2 main bearing, which had rotated. The crankcase halves adjacent to the No. 2 main bearing were fretted where the case through-studs were located. The fretting of the mating surfaces was consistent with insufficient clamping force due to insufficient torque of the through-stud nuts. Records indicated that all six cylinders on the right engine had been replaced at the airplane's most recent annual inspection 8 months before the accident. In order to replace the cylinders, the through-stud nuts had to be removed as they also served to hold down the cylinders. It is likely that when the cylinders were replaced, the through-stud nuts were not properly torqued, which, over time, allowed the case halves to move and led to the bearing spinning and the crankshaft fracturing. During the accident sequence, the pilot made a right turn in an attempt to return to the airport and did not feather the failed (right) engine's propeller, allowing it to windmill, thereby creating excessive drag. It is likely that the pilot allowed the airspeed to decay below the minimum required for the airplane to remain controllable, which combined with his failure to feather the failed engine's propeller and the turn in the direction of the failed engine resulted in a loss of airplane control.
Probable cause:
The loss of right engine power on takeoff due to maintenance personnel's failure to properly tighten the crankcase through-studs during cylinder replacement, which resulted in crankshaft fracture. Also causal were the pilot's failure to feather the propeller on the right engine and his failure to maintain control of the twin-engine airplane while maneuvering to return to the airport.
Final Report:

Crash of a Beechcraft B200GT Super King Air in Baker: 1 killed

Date & Time: Jun 7, 2013 at 1310 LT
Operator:
Registration:
N510LD
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Baton Rouge - McComb
MSN:
BY-24
YOM:
2007
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
15925
Captain / Total hours on type:
5200.00
Aircraft flight hours:
974
Circumstances:
The accident pilot and two passengers had just completed a ferry flight on the recently purchased airplane. A review of the airplane’s cockpit voice recorder audio information revealed that, during the ferry flight, one of the passengers, who was also a pilot, was pointing out features of the new airplane, including the avionics suite, to the accident pilot. The pilot had previously flown another similar model airplane, but it was slightly older and had a different avionics package; the new airplane’s avionics and flight management system were new to the pilot. After completing the ferry flight and dropping off the passengers, the pilot departed for a short cross-country flight in the airplane. According to air traffic control recordings, shortly after takeoff, an air traffic controller assigned the pilot a heading and altitude. The pilot acknowledged the transmission and indicated that he would turn to a 045 heading. The radio transmission sounded routine, and no concern was noted in the pilot’s voice. However, an audio tone consistent with the airplane’s stall warning horn was heard in the background of the pilot’s radio transmission. The pilot then made a radio transmission stating that he was going to crash. The audio tone was again heard in the background, and distress was noted in the pilot’s voice. The airplane impacted homes in a residential neighborhood; a postcrash fire ensued. A review of radar data revealed that the airplane made a climbing right turn after departure and then slowed and descended. The final radar return showed the airplane at a ground speed of 102 knots and an altitude of 400 feet. Examination of the engines and propellers indicated that the engines were rotating at the time of impact; however, the amount of power the engines were producing could not be determined. The examination of the airplane did not reveal any abnormalities that would have precluded normal operation. It is likely that the accident pilot failed to maintain adequate airspeed during departure, which resulted in an aerodynamic stall and subsequent impact with terrain, and that his lack of specific knowledge of the airplane’s avionics contributed to the accident.
Probable cause:
The pilot’s failure to maintain adequate airspeed during departure, which resulted in an aerodynamic stall and subsequent impact with terrain. Contributing to the accident was the pilot’s lack of specific knowledge of the airplane’s avionics.
Final Report:

Crash of a Beechcraft King Air 90 in New Roads: 5 killed

Date & Time: Jun 23, 2005 at 1900 LT
Type of aircraft:
Operator:
Registration:
N62BL
Flight Type:
Survivors:
No
Schedule:
Jonesboro-New Roads
MSN:
LW-272
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
4000
Captain / Total hours on type:
1790.00
Aircraft flight hours:
7166
Circumstances:

On final approach to runway 36, all seems to be ok on board. Suddenly, the twin engine aircraft nosed down and crashed. All occupants were killed.

Crash of a Rockwell Aero Commander 500 in Monroe: 3 killed

Date & Time: Nov 1, 2002 at 1130 LT
Operator:
Registration:
N1HV
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Monroe-Monroe
MSN:
500-0950-16
YOM:
1960
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
18500
Aircraft flight hours:
8881

Crash of a Cessna 414 Chancellor in Monroe

Date & Time: Nov 17, 1998 at 1855 LT
Type of aircraft:
Operator:
Registration:
N30ML
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Monroe-Dallas
MSN:
414-0005
Crew on board:
2
Crew fatalities:
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
313
Captain / Total hours on type:
54.00
Aircraft flight hours:
6415