ERA16LA114 · Cessna 182 K
Cessna 182 K · Accident: collision during takeoff/landing
From Fort Lauderdale Executive Airport (FXE) to Gainesville Regional Airport (GNV)
Event
- NTSB case
- ERA16LA114
- 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 182 K
- Aircraft type
- Cessna 182
- 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
- N2861R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FLTo Gainesville Regional Airport (GNV), Gainesville, FL
- Aircraft age
- About 49 years (built 1967)
- 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
- Landing · landing roll
- 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
- Substantial
Cause areas
- Aircraft › Aircraft power plant
- Aircraft › Fluids/miscellaneous hardware
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot stated that, before takeoff, he conducted a preflight inspection of the airplane and added 1 quart of oil to make a total of 8 quarts of oil in the airplane; the engine runup was normal. He further stated that the approximate 2-hour flight was uneventful until after he was cleared to land, when the engine began to run "rough." He enriched the mixture and reduced power, but the engine began shaking, oil sprayed onto the windshield, and then the engine lost total power. He declared an emergency and conducted a forced landing on a road, during which the left wing impacted a tree.
An examination of the engine revealed that the crankshaft's Nos. 4 and 5 connecting rod journals exhibited discoloration and heat damage, consistent with oil starvation, and that the rods had separated from the crankcases at their respective journals. The main bearing support mating surfaces were intact and exhibited no signs of fretting, bearing movement, or bearing rotation. The oil galleys and passages in the crankshaft and engine case halves were clear and unrestricted. Although an unmeasured quantity of oil was noted in the engine's oil sump, due to the damage of the sump and crankcase, the quantity of oil in the engine before the accident could not be determined.
Probable cause
The failure of the engine crankshaft near the Nos. 4 and 5 crankshaft journals due to oil starvation. The reason for the oil starvation could not be determined during postaccident examination.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16LA114
- Event ID
- 20160229X81455
- Case number
- ERA16LA114
- 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: 88c4345ce7d1916c5cba1fdec73e45f226215d072bffbaf5213eba0634dd7a82; retrieved 2026-09-16T03:11:22.329Z.