ERA23LA268 · Jabiru J250
Jabiru J250 · Accident: loss of control on ground during takeoff
Event
- NTSB case
- ERA23LA268
- 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
- 0
- 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 J250
- Aircraft type
- Jabiru J250
- 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
- N828WD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 16 years (built 2007)
- 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
- Takeoff
- 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 control on ground
- 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 oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the takeoff roll, the airplane started to drift left of the runway centerline. He responded with right rudder; however, the airplane continued to drift to the left. He continued to add right rudder until the pedals reached the hard stop. The airplane departed the runway surface and entered a rough, grassy area. The airplane’s nose landing gear collapsed, and the wreckage came to rest nose down, resulting in substantial damage to the airplane. A postaccident examination of the flight controls, wheel brakes, and tires did not reveal evidence of a preexisting mechanical malfunction or failure. The pilot reported that there were thunderstorms in the area. There was no wind information available for the departure airport; however, several airports in the area reported gusting wind conditions. The closest recorded observation noted distant lightning to the west. Based on this information, it is likely that the pilot encountered wind conditions that exceeded his ability to maintain directional control during the takeoff roll.
Probable cause
The pilot’s decision to take off in wind conditions that exceeded his ability to maintain directional control, resulting in a runway excursion and substantial damage to the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA268
- Event ID
- 20230614192370
- Case number
- ERA23LA268
- 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, 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: 0b0309603da4e5d9dcd462ee62e68f8569c278cda337dd11f012df97ac7ff9a2; retrieved 2026-09-16T17:43:34.225Z.