LAX83FVG11 · Rietman WIDGET
Rietman WIDGET · Accident: airframe, component or system failure while maneuvering
Event
- NTSB case
- LAX83FVG11
- 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
- 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
Rietman WIDGET
- Aircraft type
- Rietman WIDGET
- 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
- N3881D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/spin
- 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
- Horizontal stabilizer attachment › Failure, total
- Horizontal stabilizer attachment › Improper
- Pilot in command › Maintenance, installation, improper
- Pilot in command › Stall/spin, uncontrolled
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER TAKEOFF THE ACFT WAS OBSERVED TO CLIMB TO ABOUT 7,000-8,000 FT MSL & ENTER A SLOW FLAT SPIN. 8 TURNS WERE COUNTED & THE ACFT DID NOT RECOVER. THE PLT BAILED OUT OF THE ACFT AT ABOUT 500-600 FT BUT THE PARACHUTE DID NOT HAVE TIME TO FULLY DEPLOY. THE RIGHT HORIZONTAL STABILIZER & ELEVATOR HAD BROKEN LOOSE & ONLY FABRIC HELD IT TO THE EMPENNAGE. BOTH THE FORWARD & REAR SPARS WERE BROKEN AT A POINT WHERE THE ATTACHING BOLTS GO THROUGH THE SPARS. THE FORWARD SPAR WAS 1/2 INCH THICK & DRILLED WITH A 1/4 INCH DRILL TO ACCOMMODATE THE 1/4 INCH MOUNTING BOLT. THE HOLE WAS NOT CENTERED IN THE SPAR & THE HOLE HAD RUN OUT THE SIDE OF THE SPAR. THE REAR SPAR WAS 1 INCH THICK & THE 1/4 INCH HOLE WAS ALSO DRILLED OFF-CENTER.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX83FVG11
- Event ID
- 20001214X43025
- Case number
- LAX83FVG11
- 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: 48e1702d3e606ebc32628c49fc16912aa2532d9eda291888ea2e75b15f5411bb; retrieved 2026-09-21T06:51:38.068Z.