FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12LA047 · Saber Trike unk

14 Oct 2011 · Okmulgee, OK, United States

Saber Trike unk · Accident en route

From Okmulgee, OK to Okmulgee, OK

Report a problem

Event

NTSB case
CEN12LA047
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

Saber Trike unk

Category
Weight-Shift
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
UNREG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Okmulgee, OKTo Okmulgee, OK
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
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
Unknown or undetermined
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
Wire
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

  • Environmental issues › Physical environment
  • Not determined › Not determined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

A non-certificated pilot was flying a weight-shift control airplane, and he reported that he had developed “mechanical problems” and was going to fly under a set of electrical wires to land in a vacant lot; the airplane impacted the wires and terrain. The pilot added that, prior to the accident flight, he had landed due to a fuel problem, repaired the problem, and departed. The pilot died about two weeks after the accident, in a manner unrelated to the accident. Circumstances surrounding the pilot’s death precluded a detailed examination of the airplane and engine.

Probable cause

The in-flight collision with electrical wires for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12LA047
Event ID
20111101X54701
Case number
CEN12LA047
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2011-10-15.
  • API snapshot SHA-256: ab945f0ebdbd2f89c7907e21f56e63e2f0f3ddd22ea21b3a061a2accd7d11745; retrieved 2026-09-15T16:54:12.320Z.