ASN Wikibase Occurrence # 168260
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: | Tuesday 5 August 2014 |
| Time: | 10:20 |
| Type: |  Quad City Challenger II |
| Owner/operator: | Private |
| Registration: | N518DT |
| MSN: | CH2-0711-2894 |
| Year of manufacture: | 2012 |
| Total airframe hrs: | 128 hours |
| Engine model: | HKS E 700 T |
| Fatalities: | Fatalities: 0 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | West of Felicity, Arizona -
 United States of America
|
| Phase: | Landing |
| Nature: | Private |
| Departure airport: | Yuma, AZ (NYL) |
| San Diego/el Cajon, CA (SEE) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The private pilot departed on a cross-country flight and climbed to cruise altitude when the engine suddenly experienced a total loss of power. The pilot attempted to restart the engine, but was unsuccessful. During the forced landing approach, at an altitude about 20 ft above ground level, the airplane encountered a wind gust, impacted the ground hard, and nosed over.
The 2-cylinder, turbocharged engine was equipped with an electronic engine control unit (ECU) that controlled the ignition and fuel injection systems. While performing the engine prestart sequence during the wreckage examination, the No. 1 electrical system indicated an ignition fault, the source of which could not be determined; the No. 2 electrical system would not activate properly. Several attempts to start the engine were unsuccessful; the engine would stumble, backfire, produce black exhaust, and stop. Examination of the spark plugs revealed that only one plug was firing in each cylinder. The ECU did not contain non-volatile memory, and it could not be determined whether the ECU was functioning properly during the accident flight. Further, examination of the electrical system was not possible due to the damage sustained during the accident; therefore, the reason for the loss of engine power could not be determined.
Probable Cause: A total loss of engine power during cruise for reasons that could not be determined based on the available information. Contributing to the accident was the pilot’s loss of control during the forced landing.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=518DT
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 05-Aug-2014 23:39 | Geno | Added |
| 06-Aug-2014 00:05 | Geno | Updated [Aircraft type, Registration, Cn, Operator, Total fatalities, Total occupants, Other fatalities, Location, Source, Damage, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 23-Dec-2017 20:05 | ASN Update Bot | Updated [Time, Cn, Nature, 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