MIA01LA222 · Cirrus Design Corp. SR-22
Cirrus Design Corp. SR-22 · Accident: total loss of engine power (non-mechanical) en route
From Louisville Municipal Airport (2J3) to Gwinnett County Briscoe Field (LZU)
Event
- NTSB case
- MIA01LA222
- 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
Cirrus Design Corp. SR-22
- Aircraft type
- Cirrus SR-22
- 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
- N232CD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Louisville Municipal Airport (2J3), Louisville, GATo Gwinnett County Briscoe Field (LZU), Lawrenceville, 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
- En route · climb to 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
- Total 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
- Fuel starvation
- 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
- Pilot in command › In-flight planning/decision, poor
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported personally fueling the airplane himself the day before the accident from his own fuel tank. The day of the accident the pilot and 1 passenger departed on an uneventful 20 minute flight to another airport where 1 additional passenger boarded the airplane. The flight departed and during climbout at 6,500 feet msl with the autopilot engaged, the VFR pilot noted adverse weather ahead as depicted on the airplane's stormscope. He disengaged the autopilot and turned 90 degrees to the left to avoid the weather. The flight encountered IMC conditions and a downdraft losing 2,000-3,000 feet of altitude. The airplane then encountered an updraft during which the airspeed decreased and the engine quit. The pilot maintained a nose-low attitude to descend and placed the mixture control to the full rich position and turned on the auxiliary fuel pump in an effort to restore engine power. Engine power was not restored and the pilot performed a forced landing in a planted millet field. During recovery of the airplane, 28-30 gallons of fuel were noted in the left fuel tank and no fuel was noted in the right fuel tank which was later found to be compromised consisting of a crack. No fuel leakage was noted at the accident site from the point where the airplane touched down to the point where the airplane came to rest. Additionally, no fuel stains were noted on the upper or lower surfaces of the right wing. The fuel vents of both fuel tanks were clear and there were no obstructions of the fuel lines from either fuel tank to the center section of the wing. A temporary fuel tank was plumbed into the fuel selector valve and with it positioned to the left and right positions, fuel flow was noted at each fuel injector nozzle. Examination of the engine revealed crankshaft, camshaft, and valve train continuity, no evidence of lack of lubrication was noted. The impulse couplings and components of both impulse couplings were broken. Metallurgical examination of the broken components of both impulse couplings revealed that with the exception of the main spring from the impulse coupling of the left magneto, all fracture surfaces exhibited overstress failure. The main spring of the impulse coupling of the left magneto exhibited fatigue signatures; the spring met specification for material, width, and thickness. The roll trim motor actuator was positioned to correct for a left wing heavy situation. According to a representative of the engine manufacturer, the damage to the impulse couplings for both magnetos was consistent with the magnetos being operated over an extended period of time at speeds below 450 magneto rpm. The airplane was equipped with a fuel caution light that would illuminate if one tank were empty and the other tank held less than 14 gallons of fuel; the light would not illuminate if one tank was empty and the other tank held greater than 14 gallons of fuel.
Probable cause
The poor in-flight planning by the pilot-in-command resulting in the total loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01LA222
- Event ID
- 20010822X01754
- Case number
- MIA01LA222
- 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, coordinates. 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: 91f273dd2f79206c9c6434f23f0c179c01c10eb2eead2604fbb427c893293722; retrieved 2026-09-22T11:38:26.849Z.