CEN17LA205 · Amstutz Curtis J BD-5B
Amstutz Curtis J BD-5B · Accident: loss of engine power (total) on approach
From Portland Municipal Airport (PLD) to Portland Municipal Airport (PLD)
Event
- NTSB case
- CEN17LA205
- 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
- 0 · 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
Amstutz Curtis J BD-5B
- Aircraft type
- Amstutz Curtis BD-5
- 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
- N604KA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Portland Municipal Airport (PLD), Portland, INTo Portland Municipal Airport (PLD), Portland, IN
- Aircraft age
- About 1 year (built 2016)
- 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
- Approach · VFR pattern base
- 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
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot, who was the builder of the airplane, stated that the purpose of the test flight was to obtain rate of climb data on the airplane, which had recently been completed. Following the sixth climb of the flight, the engine began to run rough. The pilot turned back toward the airport and entered the traffic pattern, and the engine experienced a total loss of power. The pilot determined that the airplane would not reach the runway and performed an off-airport landing in a field. The field was soft and contained high vegetation, which resulted in a ground loop during landing.
The pilot noted that, during the flight, the No. 1 cylinder exhaust gas temperature and cylinder head temperature had dropped, indicating that the No. 1 cylinder was not firing properly. It was after the No. 1 cylinder quit firing that the No. 2 cylinder also quit firing. A postaccident examination of the engine revealed that the wire in the No. 1 cylinder connector between the engine control unit and the fuel injector was not properly crimped at the connector, which allowed the wire to be pulled back. In addition, a wire to the No. 2 connector was found broken where the wire had been spliced. This wire most likely separated at the spliced area due to engine vibrations after the No. 1 cylinder ceased operating.
Probable cause
A failure of the wiring between the engine control unit and the fuel injector, which resulted in a total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA205
- Event ID
- 20170531X55038
- Case number
- CEN17LA205
- 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: 93dbca8a9e547df3b35c6da12bcf87ae55f746d28f93d4423578b44e377c2ab7; retrieved 2026-09-16T05:20:53.775Z.