Diamond Aircraft Ind GMBH DA 40 NG accident near Kingman, Arizona, December 29, 2016
On December 29, 2016 at about 7:30 pm local time, a 2015 Diamond Aircraft Ind GMBH DA 40 NG, registered N605SJ, was substantially damaged in an accident during enroute (cruise) near Kingman, Arizona. It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The loss of engine oil pressure during cruise flight, which resulted in partial loss of engine power and necessitated a forced landing. The loss of oil pressure was the result of a failed engine piston, likely initiated by foreign object damage, which resulted in the pressurization of the crankcase and expulsion of the engine oil.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 29, 2016 · about 7:30 pm local time
- Place
- Kingman, Arizona · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Diamond Aircraft Ind GMBH DA 40 NG NO SERIES, built 2015
- Registration
- N605SJ · no longer on the register · serial 40.N284
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that, during cruise flight, the airframe began to shake, and he received a failure annunciation indication from both engine control units, followed by indications of an increase in oil temperature and a loss of oil pressure. He decided to perform a forced landing into a field, during which both wings impacted vegetation and the airplane sustained substantial damage. Subsequent examination revealed that a large quantity of engine oil had been expelled out of the engine breather tube and onto the belly of the airplane. Disassembly of the engine revealed heavy pitting to the piston crown and combustion chamber surfaces of the No. 1 cylinder. The damage appeared to be the result of a fatigue crack in the piston, which allowed combustion gases to create a gas path, which eventually tunneled through the piston. The path ultimately reached the lowest piston ring, allowing pressurization of the engine crankcase, resulting in the observed expulsion of oil. The crack appeared to have been initiated by a nick in the piston crown, possibly caused by ingestion of a foreign wire-like object, which was harder than the aluminum material that comprised the piston and cylinder head. A determination of the foreign object type could not be made, but there are multiple possibilities regarding the source. The induction side of the turbocharger had experienced a failure about 234 flight hours prior, and the induction-to-intake plenum was replaced 192 hours prior to the accident. A fragment of material, such as safety wire, could have been inadvertently left inside the unfiltered side of the induction system during those maintenance events and been ingested into the engine. The design of the air induction system incorporated filters for both normal and alternate air operations, and, as such, foreign object ingestion during operation was unlikely. The engine’s oil analysis history did not indicate any significant deviations throughout its service history. Such damage would likely have resulted in oil contamination; therefore, the crack likely began to propagate during the 90-hour period between the last oil analysis and the accident flight. Multiple similar piston failures have occurred to other engines in the series, seemingly initiated by either foreign object ingestion and damage or thermal overload due to an out-of-tolerance fuel injector, or a combination of both. The manufacturer released a mandatory service bulletin to address the fuel injector defects and a service letter to address the potential for foreign object ingestion following maintenance events. Although not contributing to the accident, during the investigation, a series of cracks were observed in the cylinder head of both the accident engine and a series of other similar engines. In one event, a crack led to a loss of coolant after the cooling system became over-pressurized. In all cases, the cracks had occurred before the engines had reached their service life. The FAA-certified engine was originally designed and manufactured for automobile use, and subsequently modified by the manufacturer for aviation use. As such, the engine was not operating in the manner (continuous high-power operation) for which it was originally designed. The significance of this finding could not be determined.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (partial) during enroute (cruise) defining event
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Damaged/degraded
- Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng oil sys › Damaged/degraded
- Aircraft › Fluids/misc hardware › Fluids › Oil › Fluid level
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 220 hours in all; 217 in this make and model; 51 in the last 90 days; 19 in the last 30 days; 144 as pilot in command
- Last flight review: October 26, 2016
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,384 hours
- Last inspection: continuous airworthiness programme, December 13, 2016; 40 hours since
- Maximum gross weight: 2,535 lb
- Seats: 4
- Landing gear: fixed
- Engine: Austro E4 (piston); 1,342 hours total
- Operator: Ctc Aviation Leasing (US) INC
The flight
- Departed from: IGM Kingman AZ at 6:50 pm
- Destination: HII Lake Havasu City AZ
Weather at the time
- Light: daylight
- Wind: from 350° at 9 knots, gusting 18
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 64°F (18°C), dew point 32°F (0°C)
- Altimeter: 30.21 inHg
- Observation at 11:15 am from KHII, 37 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
9 documents, released by the NTSB on June 23, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
| 2 | Oil Analysis Report | PDF, 2 pages | View Download |
| 3 | Fuel Analysis | PDF, 2 pages | View Download |
| 4 | Mandatory Service Bulletin MSB-E4-025/3 | PDF, 5 pages | View Download |
| 5 | Service Information Letter SI-E4-010 | PDF, 1 page | View Download |
| 6 | EASA Airworthiness Directive 2019-0041 | PDF, 3 pages | View Download |
| 7 | FAA Service Difficulty Report | text file | View Download |
| 8 | Statement of Party Representatives to NTSB Investigation | PDF, 3 pages | View Download |
| 9 | ATSB Transport Safety Report AO-2017-090 | PDF, 29 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
