FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL95LA042 · Matto KR-2A MODIFIED KR-2A MODI

18 Jan 1995 · Boone, NC, United States

Matto KR-2A MODIFIED KR-2A MODI · Accident: airframe, component or system failure en route

From Johnson County Airport (6A4) to Johnson County Airport (6A4)

Report a problem

Event

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

Matto KR-2A MODIFIED KR-2A MODI

Aircraft type
Matto KR-2
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
N612W
Operator
Ives, Thomas E. · private individual
Onboard fatalities
Unknown
Route
From Johnson County Airport (6A4), Mountain City, TNTo Johnson County Airport (6A4), TN
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
Airframe, component or system 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

  • Miscellaneous, bolt/nut/fastener/clamp/spring › Failure, total
  • Miscellaneous, bolt/nut/fastener/clamp/spring › Undetermined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

DURING CRUISE FLIGHT, ABOUT 5,500 FEET MSL, THE PROPELLER SEPARATED FROM THE ENGINE. THE PILOT SET UP FOR A FORCED LANDING. THE AIRCRAFT WAS LANDED ON AN OPEN FIELD, ON RISING MOUNTAINOUS TERRAIN. THE PROPELLER WAS NOT LOCATED. THREE BOLTS ENDS REMAINED IN THE PROPELLER FLANGE, AND ALL SHOWED EVIDENCE OF OVERLOAD. THE OTHER THREE BOLTS WERE NOT LOCATED.

Probable cause

THE FAILURE OF THE PROPELLER RETAINING BOLTS FOR AN UNDETERMINED REASON, WHICH RESULTED IN THE SEPARATION OF THE PROPELLER FROM THE ENGINE. THE RISING, MOUNTAINOUS TERRAIN WAS A FACTOR.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL95LA042
Event ID
20001207X02825
Case number
ATL95LA042
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: 2bf2d77c85d8037de636167789ad60eaaca984774d3224330d01d583a97a4200; retrieved 2026-09-23T00:19:20.181Z.