FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD04LA016 · Pilatus P3-05

10 Apr 2004 · Edgewater, FL, United States

Pilatus P3-05 · Accident: airframe, component or system failure en route

From Space Coast Regional Airport (TIX) to Spruce Creek Airport (7FL6)

Report a problem

Event

NTSB case
IAD04LA016
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
2 · 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

Pilatus P3-05

Aircraft type
Pilatus P3
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
N860MK
Operator
Unknown
Onboard fatalities
Unknown
Route
From Space Coast Regional Airport (TIX), Titusville, FLTo Spruce Creek Airport (7FL6), Daytona Beach, FL
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
Airframe, component or system failure
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Engine assembly, bearing › Delamination

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

NTSB narrative

The single-engine experimental airplane was the lead airplane in a formation with three other airplanes, in cruise flight at 1,500 feet above the ground, when it suddenly experienced a catastrophic engine failure and began to veer to the left toward one of the other airplanes. The pilot of the other airplane turned to avoid the accident airplane, and noticed that the accident airplane's cockpit was filling with smoke. Oil was also seen streaming back onto the canopy. The accident pilot requested help, and one of the other pilots attempted to guide him to a safe off-field landing. The accident pilot was then observed to open the cockpit canopy. Smoke and oil were seen pouring onto the pilot's face. The accident airplane then continued to descend until impacting trees and terrain. Examination of the wreckage revealed that the engine's no. 2 connecting rod had separated and punched a hole in the crankcase. A detailed engine exam revealed that the no. 2 connecting rod bearing substrate had delaminated from the steel backing of the bearing, thus allowing excessive bearing clearance. This led to a failure of the rod cap bolts (due to overstress) and separation of the connecting rod from the crankshaft. The separated rod punctured a hole in the engine crankcase, allowing oil to escape and mechanical seizure of the engine. No materials deficiencies of any engine part were noted. The bearing type was the subject of a Lycoming Special Advisory (no. 59-800) in 2000, a Mandatory Service Bulletin (no. 547) in 2001, and another Mandatory Service Bulletin (no. 561) in 2004 which discussed delamination of the bearings for undetermined reasons, and recommended replacement of them with bearings that had "increased durability." These bulletins addressed a higher powered engine (TIO-540), and not the accident engine; however, two other instances of delaminated bearing failures from lower-powered engines (including one similar to the accident engine) were noted. The accident airplane had a propeller installed that was not the one required for normal certification. Additionally, the pilot frequently flew the airplane in formation, thus requiring frequent power changes (with a geared engine). Records indicate that all 6 cylinders were overhauled and sent back to the pilot's mechanic about 6 months before the accident. About 4 months before the accident, the mechanic changed the oil and oil filter about 20 operating hours after the cylinders were replaced. This entry (as well as a previous oil change entry 8 months prior) did not indicate that the oil filters and screens were opened and inspected for metal debris; however, the mechanic stated that he always checked for debris. The airplane had flown an additional 14 flights since the last oil change. The pilot's log indicated that 7 quarts of oil were added to the engine during that time. The final pilot logbook entry was dated one week before the accident and indicated that one quart of oil was added to the engine, at an engine time of 326.2 hours. The logs did not reveal any unresolved discrepancies.

Probable cause

The delamination of the no. 2 connecting rod bearing for undetermined reasons, resulting in a total loss of engine power. A factor in the accident was the pilot's inability to complete a successful forced landing due to oil on the windscreen, and smoke and oil in the cockpit as a result of the mechanical failure of the engine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD04LA016
Event ID
20040414X00460
Case number
IAD04LA016
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: investigation status, coordinates. 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: 6802f7cc7168f1ab173ec64cc116d98e5234c745949d7ff5abcbfdd8336f8625; retrieved 2026-09-20T18:30:19.658Z.