FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99LA103 · Zivko Aeronautics EDGE 540

18 Feb 1999 · Livermore, CA, United States

Zivko Aeronautics EDGE 540 · Accident: total loss of engine power (mechanical failure) en route

From Tracy Municipal Airport (TCY) to San Carlos Airport (SQL)

Report a problem

Event

NTSB case
LAX99LA103
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
0
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

Zivko Aeronautics EDGE 540

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
N9ND
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tracy Municipal Airport (TCY), Tracy, CATo San Carlos Airport (SQL), San Carlos, CA
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 · cruise
First occurrenceThe 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
Total loss of engine power (mechanical failure)
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

  • Eng assembly, crankshaft counterweights/vib damper › Loose part/bolt/nut/clamp/etc
  • Eng assembly, crankshaft counterweights/vib damper › Separation
  • Manufacturer › Inadequate quality control
  • Manufacturer › Procedures/directives, not followed

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot said he was in normal cruise flight when the 200-hour since new Lycoming AEIO-540 engine began to over speed. The pilot said a roughness, which progressively worsened, was associated with the onset of the over speed event. He stated that he was unsuccessful in regaining control of the engine and initiated a power-off forced landing to a clear area next to a highway. The aircraft touched down in soft, muddy soil and the landing gear was torn out of the structure. Cracks were found across the rear of the engine case between the Nos. 5 and 6 cylinders. Disassembly of the engine revealed that one of the two counterweight rollers had become dislodged from the corresponding counterweight crankshaft lug bore and precipitated a catastrophic internal failure of the No. 6 connecting rod. Detailed examination of the separated counterweight crankshaft lug bore revealed rotational scoring around the inside diameter of the hole, while the roller bushing was broken in two pieces and displayed rotational scoring marks around the outside diameter. The designed bushing to bore clearance provides for an interference fit. The problematic lug bore was measured for circularity, position, and diameter with respect to design specifications. The lug bore was found outside of acceptable tolerances in all areas. According to Textron Lycoming and the FAA, a small number of crankshafts by serial number where produced with the lug bore(s) misreamed to an out of round condition during that stage of the manufacturing process. The accident crankshaft by serial number was outside of the believed problem range.

Probable cause

The manufacturer's inadequate quality control procedures, which allowed an improperly manufactured crankshaft to be shipped, resulting in the separation of one counterweight from the crankshaft lug and the subsequent catastrophic internal failure of the engine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99LA103
Event ID
20001205X00191
Case number
LAX99LA103
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1999-02-19.
  • API snapshot SHA-256: d53573004e00b61edb6721ce50aca68da413ed74a6e945d2b0ff70422127de40; retrieved 2026-09-22T15:50:59.615Z.