ATL99LA130 · Cessna 182P
Cessna 182P · Accident: partial loss of engine power (mechanical failure) en route
From Barwick Lafayette Airport (9A5) to an unrecorded destination
Event
- NTSB case
- ATL99LA130
- 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
- 0
- 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 182P
- 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
- N6863M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Barwick Lafayette Airport (9A5), LaFayette, GATo not recorded
- Aircraft age
- Not recorded
- 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
- En route · cruise
- First occurrenceThe 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
- Partial loss of engine power (mechanical failure)
- 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
- Other maintenance personnel › Maintenance, installation, improper
- Throttle/power lever, linkage › Missing
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After departing the airport and leveling off at 2,500 ft. msl, the pilot began to make throttle adjustments. The throttle appeared to get loose and throttle movement brought no change in engine rpm. The engine then began to lose rpm. He located a 2,400 ft. grass strip on which to perform a precautionary landing and glided to the field. The airplane touched down at the mid-field point. The airplane departed the end of the grass field and impact several small pine trees. An examination of the airplane's engine revealed that the throttle linkage had separated from the throttle arm and there was a missing linkage bolt at the carburetor. A review of the maintenance logbooks revealed that a new engine was installed 1.2 hours prior to the accident.
Probable cause
The missing throttle linkage bolt from the carburetor due to an improper engine installation by maintenance personnel. Factors were the tailwind present during the landing roll and the trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL99LA130
- Event ID
- 20001212X19695
- Case number
- ATL99LA130
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 87fafbe3590b5c99b06d91976937980832f6735dcf702ddc178aefb8b8495d7b; retrieved 2026-09-22T14:08:14.672Z.