FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18LA166 · Cessna 421C C

11 Jun 2018 · Plant City, FL, United States

Cessna 421C C · Accident during takeoff

From Plant City Municipal Airport (PCM) to Immokalee Regional Airport (IMM)

Report a problem

Event

NTSB case
WPR18LA166
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
0 · 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 421C C

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
N13RF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Plant City Municipal Airport (PCM), Plant City, FLTo Immokalee Regional Airport (IMM), Immokalee, FL
Aircraft age
About 38 years (built 1980)
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
Takeoff · rejected takeoff
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
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During takeoff on a night aerial observation flight, the pilot reported that the airplane did not accelerate adequately, and he chose to abort the takeoff. The airplane continued off the end of the runway and came to rest in a field about 750 ft past the departure end, resulting in substantial damage to the wings and fuselage. Examination revealed that the left engine turbocharger compressor air duct was disconnected from the throttle body. The right engine's engine-driven fuel pump was contaminated with water and debris and would not produce normal pressures and flow; however, whether these anomalies were present at the time of the accident or occurred as a result of or after the accident could not be determined. There were no other anomalies observed that would have precluded normal engine operation. Review of performance information revealed that, given the airplane's weight and atmospheric conditions at the time of the accident, the pilot had adequate runway available to accelerate the airplane to a decision speed, abort the takeoff, and stop on the remaining runway. Airport surveillance video revealed that the pilot did not activate the pilot-controlled runway lighting before takeoff, and tire skid marks on the runway were consistent with heavy braking within the last 200 ft of the runway's paved surface. The circumstances of the accident are consistent with the pilot's delayed decision to abort the takeoff. The pilot's failure to activate the runway lighting system before takeoff likely contributed to the accident by reducing his ability to judge the airplane's acceleration with respect to the runway distance remaining and abort the takeoff in a timely manner upon recognizing an anomaly.

Probable cause

The pilot's delayed decision to abort the takeoff, which resulted in a runway overrun. Contributing to the accident was an engine anomaly for reasons that could not be determined based on the available information, and the pilot's failure to activate the runway lighting system before takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18LA166
Event ID
20180611X23949
Case number
WPR18LA166
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, coordinates. 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: 0cfe8115141fbfa5d7815afbded3f0b26719a4edf4ee5def99396221a85d672a; retrieved 2026-09-16T07:26:10.530Z.