CHI99LA143 · Narzinski AVID FLYER MARK IV AVID FLYER
Narzinski AVID FLYER MARK IV AVID FLYER · Accident: total loss of engine power (mechanical failure) en route
From Creve Coeur Airport (1H0) to an unrecorded destination
Event
- NTSB case
- CHI99LA143
- 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
Narzinski AVID FLYER MARK IV AVID FLYER
- Aircraft type
- Narzinski AVID FLYER MARK
- 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
- N313N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Creve Coeur Airport (1H0), Creve Coeur, MOTo not recorded
- 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
- First occurrenceThe 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
- Total loss of engine power (mechanical failure)
- 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
- Engine assembly, bearing › Failure
- Terrain condition › Rough/uneven
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The engine experienced an uncommanded loss of power from 6,000 rpm to 5,400 rpm over a period of 4-seconds. The pilot reported that he established the airplane on best glide speed and prepared for an off-field landing while the engine experienced a constant depletion of power, finally loosing all power after a period of approximately 30 seconds. The pilot stated that he executed a forced landing into a farm field that had, 'modest furrows'. Substantial damage to the airplane was sustained during the landing. External visual inspection of the engine revealed a hole in the lower engine case on the Power Takeoff (PTO) cylinder side. Internal examination of the engine revealed metal deposits on the PTO cylinder dome, cylinder wall, and piston head. Examination of the PTO connecting rod revealed that the connecting-rod bearing had failed.
Probable cause
The failure of the connecting rod bearing, and the rough/uneven terrain condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99LA143
- Event ID
- 20001212X18717
- Case number
- CHI99LA143
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 149b54cadd95e7b44d7af603ae95eef04af3258f1bc79c2400c4039e4f82f540; retrieved 2026-09-22T15:22:16.705Z.