Cessna 421B accident near Hammond, Louisiana, October 14, 2015
On October 14, 2015 at about 8:42 pm local time, a 1973 Cessna 421B, registered N33FA, was destroyed in an accident during initial climb near Hammond, Louisiana (Hammond Northshore Rgnl airport). It was a business flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 14, 2015 · about 8:42 pm local time · cases in 2015
- Place
- Hammond, Louisiana · Hammond Northshore Rgnl · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 421B B, built 1973 · all 421Bs on the register
- Registration
- N33FA · no longer on the register · serial 421B0502
- Damage
- Destroyed
- Flight
- Business flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during initial climb defining event
- Loss of control in flight during initial climb
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Aircraft › Aircraft handling/service › Maintenance/inspections › (general) › Incorrect service/maintenance
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Failure other cases naming the engine
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Engine out control › Not attained/maintained
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Prop/rotor parameters › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Last inspection: annual inspection, February 1, 2015
- Maximum gross weight: 7,449 lb
- Seats: 7
- Landing gear: retractable
- Engine 1: Cont Motor GTSI0-520-F-K (piston); 0 hours total
- Engine 2: Cont Motor GTSI0-520-F-K (piston); 0 hours total
- Fire on the ground
- Operator: Aero One, Inc.
The flight
- Departed from: HDC Hammond LA at 8:30 pm
- Destination: ATL Atlanta GA
- Flight plan: IFR
- Runway 31, 6,502 ft by 100 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 91°F (33°C), dew point 30°F (-1°C)
- Altimeter: 30.03 inHg
- Observation at 8:35 pm from HDC
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
9 documents, released by the NTSB on October 26, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Toxicological Report | PDF, 1 page | View Download |
| 2 | Airplane Maintenance Information 1 | PDF, 16 pages | View Download |
| 3 | Airplane Maintenance Information 2 | PDF, 26 pages | View Download |
| 4 | Witness Statements | PDF, 9 pages | View Download |
| 5 | Record of Conversation with Pilot's Girlfriend | PDF, 2 pages | View Download |
| 6 | Record of Conversation with Passenger's Business Partner | PDF, 2 pages | View Download |
| 7 | Communications Transcript | PDF, 2 pages | View Download |
| 8 | Photograph Log | PDF, 13 pages | View Download |
| 9 | Statement of Party Representatives to NTSB Investigation | PDF, 2 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N33FA: not on the register today · the record of its deregistration
- Cessna 421 Golden Eagle 768 registered today · the model family and its accident history
- Cessna 72,672 aircraft on the register
- Engine: Cont Motor GTSI0-520-F-K 169 aircraft carry this series today · as the NTSB recorded it
- Engine: Cont Motor GTSI0-520-F-K 169 aircraft carry this series today · as the NTSB recorded it
- Hammond Northshore Regional · nearest airport
- Hartsfield/Jackson Atlanta International · bound for
- Accidents and incidents in Louisiana 1,274 since 1982 · 188 in the last ten years
- Louisiana 3,725 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN16FA013.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
