ERA23LA283 · Airborne Edge-X
Airborne Edge-X · Accident while maneuvering
Event
- NTSB case
- ERA23LA283
- 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
- Event fatalities
- Unknown
- 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
Airborne Edge-X
- Aircraft type
- Airborne EDGE-X
- 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
- N147JL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 19 years (built 2004)
- 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
- Maneuvering
- 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
- 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
After performing a preflight inspection of the weight-shift-control aircraft, the pilot departed on a personal flight. After 30 minutes of flying, the engine began to surge. The pilot attempted to regain full engine power; however, the engine continued surging, and the pilot chose to conduct a forced landing to a golf course. During the landing, the aircraft touched down in a grass area, continued into a rocky area, and came to rest inverted in a pond, resulting in substantial damage to the fuselage. Postaccident examination of the two-stroke engine found water throughout the engine, likely from being submerged in the pond. No mechanical anomalies were noted with the engine that would have precluded normal operation; however, a white clay and white powder substance was noted throughout the fuel system. It is possible that the substance partially occluded the fuel lines, which resulted in the engine surging; however, it could not be determined when the contamination occurred; therefore, the reason for the partial loss of engine power could not be determined.
Probable cause
A partial loss of engine power for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA283
- Event ID
- 20230705192512
- Case number
- ERA23LA283
- 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: d3151abf9a2338d2228446be62e5a6bd55f9dc124b36eececd639ae7eb37afad; retrieved 2026-09-16T17:47:56.166Z.