FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA117 · Cessna 180 UNDESIGNAT

1 Jun 2017 · Ventura, CA, United States

Cessna 180 UNDESIGNAT · Accident: aircraft structural failure en route

From Santa Paula Airport (SZP) to Santa Paula Airport (SZP)

Report a problem

Event

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

Cessna 180 UNDESIGNAT

Aircraft type
Cessna 180
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
N3683C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Santa Paula Airport (SZP), Santa Paula, CATo Santa Paula Airport (SZP), Santa Paula, CA
Aircraft age
About 63 years (built 1954)
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
Aircraft structural 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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft structures
  • Not determined › Not determined
  • Personnel issues › Task performance

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

NTSB narrative

The private pilot was conducting a local, personal flight over mountainous terrain. Several witnesses near the accident site reported that they heard a loud sound. Two witnesses stated that before hearing the loud sound, it sounded like the engine was powering up. Another witness stated that after hearing the loud sound, he looked up and saw the airplane spinning towards the ground, and that the engine and both wings had separated from the airplane.

During postaccident examination of the airplane, no pre-existing cracks or anomalies with the horizontal stabilizers, elevators, or wing structures were found. Additionally, the airplane was likely operated within the weight and balance limitations. Further, no preaccident anomalies with the flight controls were found that would have precluded normal airplane control. Damage noted at the wing and empennage separation points indicated that all cables were intact before the breakup. However, damage and deformation were observed on the right horizontal stabilizer and elevator that was consistent with a significant download that exceeded the capabilities of the structure. The wings had separated from the airplane, and the fractures and deformations were consistent with a negative overload failure of the wings.

Examination of the left horizontal stabilizer and elevator could not conclusively determine the cause of the damage and deformation but indicated that it was likely caused by a partial downward failure. The loads required to fail the horizontal stabilizers and elevators could not have been generated by normal flight or control movements. Such failures would have required the pilot to abruptly pull back on the yoke and move the elevator to a trailing-edge-up position, at speeds higher than the airplane's maneuvering speed. A review of the radar data returns indicated that before the in-flight breakup, the airplane was accelerating and had reached a speed that was higher than its maneuvering speed.

Given the radar data and wreckage examinations, it is likely that the pilot performed an abrupt and substantial pull up maneuver, while flying the airplane above maneuvering speed, which caused a downward failure of the right horizontal stabilizer and partial downward failure of the left horizontal stabilizer, which resulted in the airplane rapidly pitching nose down. Subsequently, the wings were overloaded in the negative direction and fragmented due to the abnormal aerodynamic loads. It could not be determined why the pilot would suddenly pull up; no radar returns or structural damage indicative of airplanes or birds were detected in the area. Further, a review of the weather information revealed that no significant weather or turbulence was reported or forecast in the accident area around the time of the accident.

Probable cause

The pilot's abrupt and substantial pullup maneuver while flying the airplane above the maneuvering speed, which resulted in an in-flight breakup. The reason for the pilot's maneuver could not be determined based on the available evidence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA117
Event ID
20170601X72202
Case number
WPR17FA117
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: c2270741fc610d22c385d86cf001704a3b6c18e77f6c8c06e8342d7589093637; retrieved 2026-09-15T06:03:30.258Z.