DFW08CA184 · Wright Avid Flyer MK IV
Wright Avid Flyer MK IV · Accident: loss of engine power (total) en route
From Texas Gulf Coast Regional Airport (LBX) to 37R · Hitchcock, TX
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DFW08CA184
- 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
Wright Avid Flyer MK IV
- Aircraft type
- Wright AVID FLYER MK
- 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
- N583AF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Texas Gulf Coast Regional Airport (LBX), ANGLETON/LAKE J, TXTo 37R · Hitchcock, TX
- 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 · cruise
- 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 › 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
The pilot reported that while in cruise flight at an altitude of 1,300 feet, the engine started to lose power and "created a rattling sound". The pilot tried to return to his departure airfield but was unable; and elected to perform a forced landing on a dirt road. During the landing the aircraft's nose gear collapsed and the aircraft came to stop against a fence post. An inspection of the engine by the aircraft owner revealed that one of the connecting rods had failed.
Probable cause
The loss of engine power due to a connecting rod failure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW08CA184
- Event ID
- 20080918X01495
- Case number
- DFW08CA184
- 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: 828ea636485bdad7296bfb773e8d6928f0696704016df730800c4c2bf2bc9b55; retrieved 2026-09-15T10:14:45.089Z.