ATL99LA123 · Cessna 172
Cessna 172 · Accident: partial loss of engine power (non-mechanical) during initial climb
From No airport to an unrecorded destination
Event
- NTSB case
- ATL99LA123
- 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 172
- Aircraft type
- Cessna 172
- 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
- N9785T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From No airportTo 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
- 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
- Partial loss of engine power (non-mechanical)
- 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
- Ignition system, magneto › Not switched
- Pilot in command › Checklist, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he completed the engine run-up procedure as he taxied to the runway for takeoff. He reported that all systems checked normal, but he believed he forgot to return the magneto switch to the both position before attempting the takeoff. He also said, he and his son had made several takeoffs from their private airstrip and they were usually airborne within the first half of the 1600-sod airstrip. No mechanical problems were reported by the pilot. The post-accident examination of the airplane also failed to disclose a mechanical problem.
Probable cause
The pilot's failure to switch the magneto switch to the both position before attempting a takeoff that resulted in the loss of engine power and resulted in the subsequent collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL99LA123
- Event ID
- 20001212X19690
- Case number
- ATL99LA123
- 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: e013a21669663fa20754711aadb0518c7da0fcf89e69cdcc0e144239ccb641b8; retrieved 2026-09-22T14:12:08.747Z.