eFlight
Accidents · NTSB ERA19FA283 · Final report

Cessna 421 accident near Deland, Florida, September 29, 2019

On September 29, 2019 at about 8:00 pm local time, a 1968 Cessna 421, registered N731PF, was destroyed in an accident during maneuvering near Deland, Florida (Deland Muni-Sidney H Taylor Fi airport). It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to maintain control of the airplane, which resulted in a collision with terrain. Contributing was the pilot’s lack of training and experience in the accident airplane make and model.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 29, 2019 · about 8:00 pm local time · cases in 2019
Place
Deland, Florida · Deland Muni-Sidney H Taylor Fi · cases near this airport · map
Type
Accident
Injuries
3 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 421 Undesignat, built 1968 · all 421s on the register
Registration
N731PF · no longer on the register · serial 421-0164
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The owner of the airplane had purchased the airplane with the intent to resell it after repairs had been made. As part of that process, a mechanic hired by the owner had assessed the airplane’s condition, proposed the necessary repairs to the airplane’s owner, and had identified a pilot who would, once the repairs and required inspection annual inspection had been completed, fly the airplane from where it was located to where the owner resided. While the mechanic had identified a potential pilot for the relocation flight, he had not yet completed the repairs to the airplane, nor had he completed the necessary logbook entries that would have returned the airplane to service. The pilot-rated passenger onboard the airplane for the accident flight, was the pilot who had been identified by the mechanic for the relocation flight. Review of the pilot-rated passenger’s flight experience revealed that he did not possess the necessary pilot certificate rating, nor did he have the flight experience necessary to act as pilot-in-command of the complex, high-performance, pressurized, multi-engine airplane. Additionally, the owner of the airplane had not given the pilot-rated-passenger, or anyone else, permission to fly the airplane. The reason for, and the circumstances under which the pilot-rated passenger and the commercial pilot (who did hold a multi-engine rating) were flying the airplane on the accident flight could not be definitively determined, although because another passenger was onboard the airplane, it is most likely that the accident flight was personal in nature. Given the commercial pilot’s previous flight experience, it is also likely that he was acting as pilot-in-command for the flight. One witness said that he heard the airplane’s engines backfiring as it flew overhead, while another witness located about 1 mile from the accident site heard the accident airplane flying overhead. The second witness said that both engines were running, but they seemed to be running at idle and that the flaps and landing gear were retracted. The witness saw the airplane roll to the left three times before descending below the tree line. As the airplane descended toward the ground, the witness heard the engines make “two pop” sounds. The airplane impacted a wooded area about 4 miles from the departure airport, and the wreckage path through the trees was only about 75-feet long. While the witnesses described the airplane’s engines backfiring or popping before the accident, the postaccident examination of the wreckage revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Additionally, examination of both propeller blades showed evidence of low rotational energy at impact, and that neither propeller had been feathered in flight. Given the witness statement describing the airplane “rolling three times” before it descended from view toward the ground, it is most likely that the pilot lost control of the airplane and while maneuvering. It is also likely that the pilot’s lack of any documented previous training or flight experience in the accident airplane make and model contributed to his inability to maintain control of the airplane. Toxicology testing was performed on the pilot’s chest cavity blood. The results identified 6.7 ng/ml of delta-9-tetrahydracannabinol (THC, the active compound in marijuana) as well as 2.6 ng/ml of its active metabolite, 11-hydroxy-THC and 41.3 ng/ml of its inactive metabolite delta-9-carboxy-THC. Because the measured THC levels were from cavity blood, it was not possible to determine when the pilot last used marijuana or whether he was impaired by it at the time of the flight. As a result, it could not be determined whether effects from the pilot’s use of marijuana contributed to the accident circumstances.

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

  1. Loss of control in flight during maneuvering defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
  • Personnel issues › Experience/knowledge › Experience/qualifications › Total experience w/ equipment › Pilot

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
  • Flight time: 500 hours in all; 0 in this make and model; 185 as pilot in command
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

Pilot-Rated Passenger

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 155 hours in all
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: rgt
  • Injury: fatal

Passenger

  • Seat: rear
  • Injury: fatal

The aircraft

  • Airframe total time: 858 hours
  • Last inspection: annual inspection, February 15, 2014; 4 hours since
  • Maximum gross weight: 6,841 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine 1: Continental GTSIO-520-D (piston); 858 hours total
  • Engine 2: Continental GTSIO-520-D (piston); 858 hours total
  • Fire on the ground

The flight

  • Departed from: DED Deland FL at 7:42 pm
  • Destination: DED Deland FL
  • Flight plan: none
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 060° at 7 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 4,800 ft; scat at 3,100 ft
  • Temperature: 84°F (29°C), dew point 73°F (23°C)
  • Altimeter: 30.07 inHg
  • Observation at 7:55 pm from DED, 4 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

16 documents, released by the NTSB on October 5, 2021. 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.

#DocumentWhat it is
1 Aircraft Owner Statement PDF, 3 pages · our copy View Download
2 Aircraft Owner Statement - Repaired Items PDF, 3 pages · our copy View Download
3 Memorandum of Record - Mechanic Statement PDF, 1 page · our copy View Download
4 Witness Statements PDF, 2 pages · our copy View Download
5 Pilot Logbook Review Summary (FAA) PDF, 2 pages · our copy View Download
6 Pilot Logbook Excerpts PDF, 6 pages · our copy View Download
7 Maintenance Records PDF, 15 pages · our copy View Download
8 Fueling Records PDF, 5 pages · our copy View Download
9 Left Engine Examination Report PDF, 36 pages · our copy View Download
10 Right Engine Examination Report PDF, 37 pages · our copy View Download
11 Propeller Examination Report PDF, 7 pages · our copy View Download
12 Airframe and Engine Wreckage Examination Summary PDF, 3 pages · our copy View Download
13 Toxicological Report PDF, 2 pages · our copy View Download
14 Photo Array PDF, 4 pages · our copy View Download
15 Evidence Control Form PDF, 8 pages · our copy View Download
16 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download

The same docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA19FA283.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.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.