FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19LA331 · Cirrus SR20

14 Sept 2019 · Orange, TX, United States

Cirrus SR20 · Accident: loss of engine power (total) en route

From Austin, TX to Lake Charles Regional Airport (LCH)

Report a problem

Event

NTSB case
CEN19LA331
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 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
N200Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Austin, TXTo Lake Charles Regional Airport (LCH), Lake Charles, LA
Aircraft age
About 16 years (built 2003)
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
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
Substantial

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

While in cruise flight, the airplane’s engine lost total power. The pilot deployed the airframe parachute and the airplane descended under canopy to a marsh, resulting in substantial damage. Examination of the engine found that a fuel line from the fuel manifold to the No. 1 cylinder failed in fatigue near the manifold, resulting in the loss of engine power.

The failed fuel line was replaced postaccident and the engine was test run with no anomalies noted. Although the fuel manifold bracket was replaced twice in the approximate 2.5 years before the accident, the extent to which this may have been related to the failure of the fuel line was not determined.

Probable cause

A total loss of engine power due to a fatigue failure of the fuel line from the fuel manifold to the No. 1 cylinder.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19LA331
Event ID
20190915X92010
Case number
CEN19LA331
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: investigation status, coordinates, cause areas. 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: 05eb51da43c3a42ad73c0dafa82046647f2bd364a090e4e7ee70aa168dc726f4; retrieved 2026-09-16T10:05:21.075Z.