ATL84FA203 · Camair Aircraft Corp. 480
Camair Aircraft Corp. 480 · Accident: total loss of engine power (mechanical failure) during initial climb
From Stoney Point Field (6GA0) to Air Acres Airport (5GA4)
Event
- NTSB case
- ATL84FA203
- 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
- 2 · 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
Camair Aircraft Corp. 480
- Aircraft type
- Camair 480
- 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
- N231
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Stoney Point Field (6GA0)To Air Acres Airport (5GA4), Woodstock, GA
- 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
- Initial climb
- 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
- Total 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
- Destroyed
Cause areas
- Engine assembly, connecting rod › Fatigue
- Pilot in command › Aircraft handling, not maintained
- Pilot in command › Airspeed(vmc), not maintained
- Pilot in command › Emergency procedure, improper
- Pilot in command › Propeller feathering, not performed
Approximate · Estimated position: the centre of Cumming, GA, the place the record names. Not the accident site.
NTSB narrative
ACCORDING TO WITNESSES, THE ACFT CROSSED A HIGHWAY AFTER TAKING OFF, ENTERED A LEFT TURN, DESCENDED & PULLED BACK UP, THEN WENT OUT OF CONTROL & CRASHED. ONE WITNESS INDICATED THAT THE ACFT ENTERED A SPIN PRIOR TO CRASHING. AN EXAM OF THE WRECKAGE SHOWED EVIDENCE THAT THE RIGHT ENG WAS PROVIDING POWER. THE LEFT PROP WAS FOUND IN A FEATHERED POSITION, BUT THE COCKPIT CONTROLS WERE NOT POSITIONED TO FEATHER THE LEFT PROP. AN EXAM OF THE LEFT ENG REVEALED THAT THE #5 CONNECTING ROD HAD FAILED FROM FATIGUE. THE FATIGUE HAD ORIGINATED IN AN AREA WHERE THE ROD HAD BEEN BENT. THERE WAS EVIDENCE OF PREVIOUS COLUMN BENDING OF THE ROD (POSSIBLY FROM A HYDROSTATIC LOCK). THE LEFT PRIMER WAS FOUND BROKEN.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL84FA203
- Event ID
- 20001214X39803
- Case number
- ATL84FA203
- 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: fab484cafb9f97b3c79f9c94e0cd04546157a0f14a485d2e5e89d08c6a2eba1b; retrieved 2026-09-21T05:29:15.775Z.