FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16LA273 · Brandt SONEX

18 Jul 2016 · Lodi, WI, United States

Brandt SONEX · Accident: loss of engine power (partial) en route

From Lodi Lakeland Airport (9WN5) to Lodi Lakeland Airport (9WN5)

Report a problem

Event

NTSB case
CEN16LA273
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

Brandt SONEX

Aircraft type
Brandt SONEX
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
N393SX
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lodi Lakeland Airport (9WN5), Lodi, WITo Lodi Lakeland Airport (9WN5), Lodi, WI
Aircraft age
Not recorded
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
En route
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 (partial)
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 power plant

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During a local flight, the pilot of an experimental amateur-built airplane had a partial engine power loss. He said that the engine sounded different but remained running. He turned the airplane back to the airport and noted he was high and fast. He indicated that he bled off airspeed, as he wanted to avoid buildings before landing. He subsequently reduced power and performed a landing with calm wind present. The airplane's nose and left main landing gear collapsed after touchdown, the airplane skidded to the north side of the runway, and exited the runway into a ditch where it sustained the substantial damage. The airplane was powered by an engine that the pilot/builder assembled from a kit. The airplane accumulated 25 hours of flight time at the time of the accident. The kit manufacturer engine assembly and installation manual had specific rocker shaft instructions that included procedures on how to adjust and install rocker arms. An examination revealed that the threaded shaft of a rocker arm swivel pad had separated at a point on the shaft where there was a cross drilled hole. The remaining rocker arms did not exhibit the appearance of arm adjustment in accordance with the kit manufacturer's assembly manual. Detailed examination of the failed valve adjuster showed it separated into two portions approximately mid length in the shank area between the two threaded areas. This location was coincident with a hole drilled crosswise through the shank of the valve adjuster. The fracture surfaces exhibited crack arrest patterns consistent with a fatigue fracture. The origin of the fatigue fracture appears to be coincident with the edge of the cross-drilled hole. Examination of the exemplar valve adjuster and specifically the cross-drilled hole revealed a roughly finished surface with a pronounced burr around the circumference of the hole. A professional materials engineering publication, in part, stated, "The fatigue strength of components can be reduced merely by the presence of a drilled hole; it is further reduced by failure to remove burrs (incurred during drilling) from the hole edges. Fractures originating at drilled holes are common in complex parts containing internal, intersecting machined passages because of the difficulty and expense of providing adequate break-edge radii at such locations. It could not be determined if the failure of the rocker arm was due to the misassembly of the rocker arm assembly and/or the toolmarks left by the manufacturing process.

Probable cause

The separated rocker arm assembly for undetermined reasons, which resulted in the partial loss of engine power and led to the landing gear collapsing during the subsequent forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16LA273
Event ID
20160720X01138
Case number
CEN16LA273
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-07-19.
  • API snapshot SHA-256: ef13ce98eecca970fdf1b858d2362b156a5636e562f56ba9721a3143ef4dd510; retrieved 2026-09-16T03:40:33.182Z.