FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA067 · Jabiru J230-SP

18 Nov 2018 · Center, TX, United States

Jabiru J230-SP · Accident: loss of engine power (total) en route

From C E 'Rusty' Williams Airport (3F3) to Center Municipal Airport (F17)

Report a problem

Event

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

Jabiru J230-SP

Aircraft type
Jabiru J230
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
N667J
Operator
Unknown
Onboard fatalities
Unknown
Route
From C E 'Rusty' Williams Airport (3F3), Mansfield, LATo Center Municipal Airport (F17), Center, TX
Aircraft age
About 10 years (built 2008)
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 › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

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 reported that, before departure, he noted that a NOTAM stated that fuel was not available at the airport where he had landed and had planned to refuel but that he felt he had sufficient fuel onboard to continue to another airport to get fuel if necessary. He assessed his fuel quantity and departed the airport, and subsequently, the engine lost power. He pitched the nose down, and the engine regained power, but the pilot realized that the fuel supply was almost exhausted. He attempted to maintain power and altitude but eventually chose to land in a field. He selected a touchdown point and circled to land, but the airplane did not complete the turn before he had to level the wings. The airplane touched down gently but overran the intended landing area, collided with a drainage culvert, and nosed over.

The airplane sustained substantial damage to the composite fuselage and windscreen.

Probable cause

The pilot's improper preflight fuel planning, which resulted in fuel exhaustion and a total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA067
Event ID
20181118X11853
Case number
GAA19CA067
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. 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: c2ae5bf3eb596cd79c15cd2d200b58a409b24766ecaf685b4ee6a2fb2193fb86; retrieved 2026-09-16T08:26:27.756Z.