CHI92DEM02 · Gillespie/Pitts S1C
Gillespie/Pitts S1C · Accident: airframe, component or system failure during landing
From James Clements Municipal Airport (3CM) to an unrecorded destination
Event
- NTSB case
- CHI92DEM02
- 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
Gillespie/Pitts S1C
- Aircraft type
- Gillespie/pitts S1
- 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
- N71309
- Operator
- Dean C. Vanzwoll · private individual
- Onboard fatalities
- Unknown
- Route
- From James Clements Municipal Airport (3CM), Bay City, MITo 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
- Landing · flare/touchdown
- 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
- Flt control syst, rudder control cable/rod › Failure, total
- Pilot in command › Rudder, unavailable
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT OF A TAIL WHEEL CONFIGURED AEROBATIC AIRPLANE HAD TOUCHED DOWN ON LANDING AND DISCOVERED THE AIRPLANE DID NOT HAVE RIGHT RUDDER PEDAL CONTROL. THE PILOT STATED HE TOOK OFF TO TROUBLE SHOOT THE PROBLEM. DURING THE INFLIGHT INVESTIGATION HE DISCOVERED THE RIGHT RUDDER CABLE HAD SEPARATED WHERE THE CABLE RUNS THROUGH THE COCKPIT NEAR THE RIGHT SIDEWALL. THE PILOT MADE A CABLE REPAIR SO IT WOULD ALLOW BRAKE SYSTEM OPERATION. DURING THE SUBSEQUENT LANDING THE AIRPLANE WAS NOT AS DIRECTIONALLY CONTROLLABLE AS IT SHOULD HAVE BEEN. AS THE AIRPLANE BEGAN TO DECELERATE IT BEGAN AN UNCONTROLLABLE SWERVE WHICH RESULTED IN A LANDING GEAR COLLAPSE.
Probable cause
A TOTAL FAILURE OF THE RUDDER CONTROL CABLE AND UNAVAILABILITY OF RUDDER TO CONTROL THE AIRPLANE DURING ITS LANDING PROCESS. FACTORS WHICH CONTRIBUTED TO THE ACCIDENT WERE DIRECTIONAL CONTROL AND REMEDIAL ACTION NOT BEING POSSIBLE ON BEHALF OF THE PILOT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI92DEM02
- Event ID
- 20001211X14613
- Case number
- CHI92DEM02
- 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: 7e7f123b3fb326a8f79372172b011b5c246cb7fe99f8356faf08aaf89b783ad4; retrieved 2026-09-23T03:10:51.581Z.