ASN Wikibase Occurrence # 75491
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Monday 5 July 2010 |
| Time: | 14:15 |
| Type: |  Cessna 172P Skyhawk II |
| Owner/operator: | Private |
| Registration: | N52614 |
| MSN: | 172-74563 |
| Total airframe hrs: | 1655 hours |
| Engine model: | Lycoming O-320-D2J |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | about 5 mi S of Chesapeake Airport, VA -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Chesapeake, VA (CPK) |
| Chesapeake, VA (CPK) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot departed his home airport, in his personal airplane in visual meteorological conditions, for an undetermined purpose. Radar data indicated that the airplane orbited at low altitude over flat terrain about 6 miles north of the departure airport for about 30 minutes, before it descended to ground impact. In the minute preceding the descent, a transmission from the airplane that included the words "mayday mayday mayday" and "[I] have a flight control malfunctions looks like I'm going down" was broadcast, and the airplane transmitted the emergency transponder beacon code. Postaccident examination and testing of the airframe and engine revealed no indications of preimpact anomalies; all observed damage was consistent with ground impact. The airplane impacted a corn field in a nose-down attitude, creating an impact crater 13 inches deep. The wreckage location was adjacent to a dirt road approximately 3 miles long. About 14 months prior to the accident, the pilot was diagnosed with mild Ankylosing Spondylitis (a chronic inflammation of the spine and sacroiliac joints), but both his airline employer and the Federal Aviation Administration determined that it did not adversely affect his continued employment as an airline pilot. Post-mortem toxicology tests detected low levels of ethanol, and several intermediate compounds in the generation or metabolism of ethanol. Given the presence of putrefaction in the biological specimens, it was possible that some or all of the ethanol was produced post-mortem. The reason why the pilot declared a flight control malfunction could not be determined.
Probable Cause: The airplane's impact with terrain for undetermined reasons following the pilot's report of a flight control malfunction.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 05-Jul-2010 23:44 | Geno | Added |
| 06-Jul-2010 00:54 | RobertMB | Updated [Time, Aircraft type, Operator, Location, Phase, Destination airport, Source] |
| 21-Dec-2016 19:25 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 26-Nov-2017 18:00 | ASN Update Bot | Updated [Other fatalities, Departure airport, Destination airport, Source, Narrative] |
| 21-Sep-2023 09:51 | Ron Averes | Updated [[Other fatalities, Departure airport, Destination airport, Source, Narrative]] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation