ATL99LA056 · Cessna 152
Cessna 152 · Accident: airframe, component or system failure en route
From Florence Regional Airport (FLO) to Dillon County Airport (DLC)
Event
- NTSB case
- ATL99LA056
- 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
- Unknown
Cessna 152
- Aircraft type
- Cessna 152
- 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
- N46542
- Operator
- Michael C. Williamson · private individual
- Onboard fatalities
- Unknown
- Route
- From Florence Regional Airport (FLO), Florence, SCTo Dillon County Airport (DLC), Dillon, SC
- 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
- Airframe, component or system failure
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the engine could not be started during the departure preparations. The battery was changed and the engine started. According to the pilot, after engine start, the instrument lights did not illuminate. He elected to continue the night cross country flight. Approximately one hour into the flight, the pilot's flashlight failed followed by loss of vacuum pressure and a subsequent loss of the vacuum-driven instruments. Moments later, while at 3,500 feet mean sea level, the pilot stated that all electrical power was lost followed by a total loss of engine power. The pilot made a forced landing in a wooded area and collided with several trees. Following the accident, the engine, alternator, vacuum pump, carburetor, and magnetos that were on the airplane at the time of the accident were tested and found to function normally through all ranges of power settings.
Probable cause
The loss of engine power for undetermined reasons. Factors were an electrical system malfunction for undetermined reasons and the dark night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL99LA056
- Event ID
- 20001205X00260
- Case number
- ATL99LA056
- 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: 3ea64d6ce559eba404ca6377258a9d8ce492e9254ad99cc940bdc49ff7deeb9c; retrieved 2026-09-21T20:35:05.696Z.