FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12IA158 · Cirrus Design Corp SR20

3 Dec 2011 · Jacksonville, FL, United States

Cirrus Design Corp SR20 · Incident: loss of engine power (total) on approach

From Orlando Sanford International Airport (SFB) to Jacksonville Executive at Craig Airport (CRG)

Report a problem

Event

NTSB case
ERA12IA158
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
Incident
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 SR20

Aircraft type
Cirrus SR20
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
N486DA
Onboard fatalities
Unknown
Route
From Orlando Sanford International Airport (SFB), Orlando, FLTo Jacksonville Executive at Craig Airport (CRG), Jacksonville, FL
Aircraft age
About 4 years (built 2007)
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
Approach · IFR initial approach
Defining eventThe 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
Loss of engine power (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Aircraft › Aircraft power plant

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 landed the airplane on an interstate highway at night after a total loss of engine power. Neither of the two occupants were injured and the airplane was undamaged. Examination of the engine revealed that a crankshaft gear tooth failed due to fatigue, which resulted in the loss of several additional gear teeth and a subsequent total loss of engine power. According to the manufacturer, this type of failure was uncommon in this engine series. The engine had accrued 1,652.3 hours since rebuild and the recommended time between overhaul was 2,000 hours.

Probable cause

The failure of a crankshaft gear tooth due to fatigue, which resulted in the loss of several additional gear teeth and a subsequent total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12IA158
Event ID
20120126X01909
Case number
ERA12IA158
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2011-12-04.
  • API snapshot SHA-256: 80c561a2a56d91ef3f12a9b1a88f614c30d36ae750d77d7d34fa6342cf63fdf9; retrieved 2026-09-15T17:06:42.158Z.