ERA16LA171 · Cessna 421 B
Cessna 421 B · Accident: collision during takeoff/landing
From Foley Municipal Airport (5R4) to West Georgia Regional Airport / O V Gray Field (CTJ)
Event
- NTSB case
- ERA16LA171
- 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 421 B
- 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
- N3372Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Foley Municipal Airport (5R4), Foley, ALTo West Georgia Regional Airport / O V Gray Field (CTJ), Carrollton, GA
- Aircraft age
- About 44 years (built 1972)
- 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
- 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
- Collision during takeoff/landing
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot of the twin-engine airplane departed on the personal flight. During the takeoff roll, all indications were normal. When the airplane accelerated to between 75 and 80 knots, the pilot pulled back on the yoke slowly, and the airplane began to climb. After he raised the landing gear, the pilot noticed that the airplane was not continuing to climb and that the airspeed was 80 knots; he then heard the stall warning horn. The airplane impacted trees about 1/4 mile from the runway, caught fire, and was destroyed; the pilot egressed with minor injuries. The airplane's published minimum control speed was 86 knots and the break ground and climb speed was 106 knots. Given that information, it is likely that the pilot's attempt to rotate and climb the airplane below 80 knots resulted in the airplane being unable to gain altitude and climb above trees at the end of the runway.
Probable cause
The pilot's failure to obtain proper takeoff speed before breaking ground, which resulted in the airplane’s failure to gain altitude and a collision with trees and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16LA171
- Event ID
- 20160427X81659
- Case number
- ERA16LA171
- 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. 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: aae040c7b6b23fced0744964ab8feda8fb84e4bb96394866fde1cb3c37466ca0; retrieved 2026-09-16T03:20:10.285Z.