FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR14CA004 · Venables Zenith CH701

3 Oct 2013 · Snohomish, WA, United States

Venables Zenith CH701 · Accident: flight control system malfunction/failure en route

From Harvey Field (S43) to Harvey Field (S43)

Report a problem

Event

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

Venables Zenith CH701

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
N143TZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Harvey Field (S43), Snohomish, WATo Harvey Field (S43), Snohomish, WA
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
Defining eventThe 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
Flight control system malfunction/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

  • Aircraft › Aircraft systems
  • Not determined › Not determined

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

NTSB narrative

The pilot reported that during a test flight the airplane encountered moderate turbulence so he decided to return to the airport for landing. While turning to the crosswind leg in the pattern, the airplane suddenly banked sharply and descended uncontrollably. The pilot was able to regain control about 500 feet above ground level, and managed to turn the airplane to the downwind leg, but he continued to have difficulty maintaining control. The pilot then decided to make an emergency off airport landing to a field. During the landing roll, the airplane collided with obstructions and nosed over. The wings and fuselage were substantially damaged. After the accident, the pilot reported that the loss of aircraft control was due to a jammed rudder for undetermined reasons.

Probable cause

A jammed rudder control while maneuvering in the pattern for reasons that could not be determined. No follow-up examination was conducted due to a lapse in agency funding and subsequent government shutdown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR14CA004
Event ID
20131003X90157
Case number
WPR14CA004
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 58937da70ec8d1a5c86b7670f0ee57c312b08746ceb6d25b740d99961ed088b6; retrieved 2026-09-15T22:56:23.061Z.