ERA19FA283 · Cessna 421 Undesignat
Cessna 421 Undesignat · Accident: loss of control in flight while maneuvering
From Deland Municipal Sidney H Taylor Field (DED) to Deland Municipal Sidney H Taylor Field (DED)
Event
- NTSB case
- ERA19FA283
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 3 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 421 Undesignat
- Aircraft type
- Cessna 421
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N731PF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Deland Municipal Sidney H Taylor Field (DED), Deland, FLTo Deland Municipal Sidney H Taylor Field (DED), Deland, FL
- Aircraft age
- About 51 years (built 1968)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Experience/knowledge
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA19FA283
- Event ID
- 20190929X70917
- Case number
- ERA19FA283
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e061b8c6c1f6ad1e38e00cda9c3ebf5c5470e50111b860b55687fb68fdb78325; retrieved 2026-09-15T07:06:10.728Z.