LAX02LA283 · Minkler Venture M20
Minkler Venture M20 · Accident: airframe, component or system failure while maneuvering
From 4SD · Reno, NV to an unrecorded destination
Event
- NTSB case
- LAX02LA283
- 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
- 1 · 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
Minkler Venture M20
- Aircraft type
- Minkler VENTURE M20
- 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
- N360
- Operator
- Tommy E. Rose · private individual
- Onboard fatalities
- Unknown
- Route
- From 4SD · Reno, NVTo 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
- Maneuvering
- 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
- Destroyed
Cause areas
- Flight control, elevator attachment › Overload
- Flight control, elevator surface › Overload
- Flt control syst, load feel › Improper
- Pilot in command › Airspeed(vne), exceeded
- Pilot in command › Design stress limits of aircraft, exceeded
- Pilot in command › Porpoise/pilot-induced oscillation, encountered
- Unknown › Maintenance, installation, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The amateur-built experimental airplane sustained a structural failure of the left and right horizontal stabilizers and the associated elevators while participating in the sport class race as part of the annual Reno Air Races. Following the structural failure of the stabilizers and elevators, the airplane dove into the ground. FAA inspectors monitoring air race activities responded to the accident site and interviewed witnesses. The accident occurred about halfway through the sport class race. As the airplane was rounding pylon No. 1, the horizontal stabilizers and elevators began flexing (one witness said the airplane began a shallow porpoise just before the crash) and then bent down. The airplane then dove into the ground. On-site assessment of the wreckage disclosed that the horizontal stabilizers and elevators remained attached to the empennage; however, they were bent down at an acute angle at a point about 2 feet outboard from the root on each side. The airplane was extensively fragmented and control system continuity could not be established on scene. The airspeed indicator was recovered in the debris; the needle was trapped between the fractured glass and the instrument face at the 300-knot/red line. Official timers for the Reno Air Races reported to FAA inspectors that based on time over the measured course distance, the airplane was doing 330 knots just before the accident. The present owner of the design rights for this experimental kit-built all metal airplane said that the airplane was designed by professional aircraft design engineers who worked for a major general aviation manufacturer. The airplane was designed with a gross weight design maneuvering speed (Va) of 156 knots indicated airspeed (KIAS). Never exceed speed (Vne) is 300 KIAS, and the maximum structural cruising speed (Vno) is 265 KIAS. During the design and prototype development, a ground vibration test (GVT) survey was performed, with no excitable nodes found within the airplane's anticipated envelope. The flight test program validated that flutter could not be excited up to Vne. The design owner said that during the developmental flight test work with the prototype, it was flown one time without an artificial force feel limiting device in the elevator control circuit. The stick force per g without the force feel/limiters is less than a pound of control force. During that flight the test pilots encountered a very severe pilot induced oscillation (PIO). A spring assembly was devised for the elevator control circuit to impart a 10-pound per g force feel feed back in the elevator controls to prevent PIO. Examination of the wreckage disclosed that the spring in the elevator force feel/limiter assembly was the wrong size and had only 30 percent of the required tension. Other discrepancies were noted concerning the bushings and bearings in the elevator attachments and the construction workmanship.
Probable cause
the overload failure of the horizontal stabilizers and elevators due to a pilot induced oscillation at a speed at or above Vne, which exceeded the design stress limits of the structure. Also causal was the intentional alteration by an unknown person or persons of the elevator down spring assembly, which likely reduced the stick force per G from a nominal 10 pounds to less than 1, and led to the pilot induced oscillation. An additional cause was the pilot's decision to operate the aircraft at, above, or near never exceed speed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02LA283
- Event ID
- 20020919X05182
- Case number
- LAX02LA283
- 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, 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: 82acd01c5502ca10e1337e675cadde4ae466c74dc5b79f9f32706bf9885e5051; retrieved 2026-09-20T19:52:03.403Z.