Cessna 180 N3683C
1 June 2017 · Ventura, California, United States · Fatal
Summary
On 1 June 2017 at about 18:55 local time, a Cessna 180 registered N3683C was involved in an accident near Ventura, California, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 18:55
- Classification
- Accident
- Location
- Ventura, California, United States
- Coordinates
- 34.3181, -119.3403
- Aircraft
- Cessna 180
- Registration
- N3683C
- Category
- Airplane
- Year built
- 1954
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Santa Paula → Santa Paula
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR17FA117
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Cessna 180 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 21 Sep 2017 | Cessna 180 | Albuquerque, New Mexico, United States | - | No injuries | - |
| 2 Aug 2017 | Cessna 180 | Puntilla, Alaska, United States | - | No injuries | - |
| 4 Aug 2017 | Cessna 180 | Willow, Alaska, United States | - | No injuries | - |
| 22 Sep 2017 | Cessna 180 | Danbury, Connecticut, United States | - | No injuries | - |
| 3 Dec 2017 | Cessna 180 | Frederick, Maryland, United States | - | Minor injuries | - |
| 9 Jul 2017 | Cessna 180 | Baker City, Oregon, United States | - | No injuries | - |
All 2,729 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 1 Mar 2017 | Bell 206B | Firebaugh, California, United States | West Valley Aviation Inc | No injuries | - |
| 1 Aug 2017 | Rockwell S 2R | Brawley, California, United States | - | No injuries | - |
| 15 Sep 2017 | Cessna T210N | Watsonville, California, United States | Singh Amandeep | No injuries | - |
| 17 Nov 2017 | Piper PA 28R-201T | Nipton, California, United States | - | No injuries | - |
| 19 Nov 2017 | Cessna 172M | Chico, California, United States | Northgate Aviation Inc | Minor injuries | - |
| 1 Mar 2017 | Maule MX7 | Live Oak, California, United States | - | Minor injuries | - |