CEN11LA083 · Piper PA-34-200T
Piper PA-34-200T · Accident: collision with terrain/object (non-CFIT) during landing
From Sugar Land Regional Airport (SGR) to Shreveport Downtown Airport (DTN)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN11LA083
- 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
Piper PA-34-200T
- Aircraft type
- Piper PA-34
- 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
- N36405
- Operator
- Jeffrey O. Clarke · private individual
- Onboard fatalities
- Unknown
- Route
- From Sugar Land Regional Airport (SGR), Sugar Land, TXTo Shreveport Downtown Airport (DTN), Shreveport, LA
- 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
- Landing
- 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
- Collision with terrain/object (non-CFIT)
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While in cruise flight, about 1 hour and 10 minutes after departure, the left engine lost power. The pilot proceeded to the nearest airport and as he maneuvered the airplane onto the base leg of the traffic pattern, the right engine lost power. He performed a wheels-up forced landing about 600 feet from the runway. He said he had departed with full fuel. A postaccident examination by Federal Aviation Administration inspectors found no evidence of fuel leakage, and the only visible fuel was approximately 5 gallons of unusable fuel. However, retrieval crews reported a very strong smell of avgas when they arrived one hour after the accident. They estimated at least ten to fifteen gallons of avgas was in both the left and right wing tanks. No anomalies were found with the airplane.
Probable cause
A total loss of power in both engines for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11LA083
- Event ID
- 20101130X12357
- Case number
- CEN11LA083
- 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. 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: 9f3a65839caab84ade3769a5f8939dca1875afc0a0883a478680c0005ee01024; retrieved 2026-09-15T15:35:20.804Z.