CEN11CA679 · Waltman Theodore J MOOSE
Waltman Theodore J MOOSE · Accident: flight control system malfunction/failure en route
From Platte Valley Airpark (18V) to Hays Regional Airport (HYS)
Event
- NTSB case
- CEN11CA679
- 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
Waltman Theodore J MOOSE
- Aircraft type
- Waltman Theodore MOOSE
- 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
- N384JP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Platte Valley Airpark (18V), Hudson, COTo Hays Regional Airport (HYS), Hays, KS
- 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
- 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 oper/perf/capability
- Aircraft › Aircraft structures
- Aircraft › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During cruise flight in smooth air, with the autopilot engaged, the experimental category amateur-built airplane suddenly encountered a single occurrence of rudder flutter that lasted 2 to 3 seconds and then ceased. One passenger described the “frequency of vibration about 10 Hz” (cycles per second) and described the sound as “BRAAP.” The pilot disengaged the autopilot and continued to his original destination for an uneventful landing. A subsequent examination of the airplane found substantial damage to the stringers, frames, and empennage skin in the area just forward of the horizontal stabilizers. The pilot, who was also the builder of the airplane, had added an electrically actuated rudder trim tab several years earlier. Most of the weight of the rudder assembly was aft of the rudder hinges, and the builder had not installed rudder counterbalance weights forward of the hinges. In addition, he had recently installed struts on the bottom of the horizontal stabilizer. Airworthiness standards for certification of normal category airplanes require that they must be shown to be free from flutter. Airworthiness standards for certification of experimental category airplanes do not require that they meet those standards.
Probable cause
Rudder flutter due to the design changes to the airplane's horizontal stabilizer.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11CA679
- Event ID
- 20110930X81510
- Case number
- CEN11CA679
- 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: 73e98f8db6433de36665d344f27dd21f1320656e3cbff5522f53cd20ca85b800; retrieved 2026-09-15T16:48:12.691Z.