Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

May 22, 2000 · Piper PA-32R-300 · N424TP

Erie, CO

Overview

Report Status
Final with probable cause
Event Type
Incident
Date
May 22, 2000
Injury Outcomes
No injuries (2 uninjured)
Location
Erie, CO
Aircraft
Piper PA-32R-300
Tail Number
N424TP
Operator
Brian J Inskeep
Injuries
None
Aircraft Damage
Minor
NTSB Number
DEN00IA093

During climb to cruise, on an IFR flight plan, in visual conditions, the engine lost all power approximately 10 minutes after takeoff. A forced landing was made in an open field and no damage was incurred during the landing. Examination of the engine provided evidence the number 2 cylinder had separated from the case and had lodged in the cowl. Detailed examination provided evidence that the cylinder hold down studs had failed and were 'necked-down' at the fracture points. The rod bolts then failed and the piston reversed itself and lodged in the case. No signatures of oil starvation or heat distress were found. Examination at an engine overhaul facility provided evidence that none of the hold down stud nuts on the remaining five cylinders had sufficient torque.

NTSB Probable Cause

Improper installation of cylinders by unknown maintenance personnel who failed to torque the cylinder stud nuts sufficiently.

Full Narrative

On May 22, 2000, at 1700 mountain daylight time, a Piper PA-32R-300, N424TP, sustained minor damage when the engine failed catastrophically during climb to cruise. The two private pilots were not injured. The flight was operating on an instrument flight rules flight plan, in visual conditions, under the provisions of Title 14 CFR Part 91. The landing site was about 10 miles north of Erie Tri-County Airport, Lafayette, Colorado, and the takeoff occurred from Jefferson County Airport, Broomfield, Colorado, about 20 miles south of the landing site. As the flight was climbing through about 8,000 feet above mean sea level (msl), [3,000 feet above ground level] the engine lost all power and oil was observed by the pilot on the cowl and wind screen. The pilot made an emergency landing in a field. No damage was incurred as a result of the landing. Initial examination of the engine revealed that the number 2 cylinder separated from the case and all the cylinder hold-down studs had sheared. The connecting rod contacted the skirt of the piston and fractured the skirt and jammed. The piston and connecting rod rotated nearly 180 degrees and the piston lodged in the case. The case revealed some piston impact damage. One connecting rod bolt and both connecting rod nuts with the bolt ends were recovered along with the connecting rod cap and both halves of the main rod bearings. One inner cylinder base nut with the stud end attached was also recovered. All fragments were found inside the engine cowling. Visual examination of the portions of the connecting rod bolts and the cylinder hold down studs provided evidence of "necking" at the fracture points. The bearing surfaces of the connecting rod, the rod and cap had no signatures of oil starvation or heat distress. The sequence of events, as provided by the witness marks, provided evidence that the connecting rod bolt failure was secondary in nature and resulted from cylinder separation. The cylinder was visually inspected and no paint or foreign material on the crankcase mounting surface or cylinder base surface was found. The other five cylinders had torque putty on all the cylinder hold down nuts. Examination of the engine at an engine overhaul facility provided evidence that none of the hold down nuts on the remaining five cylinders had sufficient torque.

Flight

Event TypeIncident
Event Time17:00 MDT
Nearest Airport0nm
Runway0
Flight Plan FiledIFR
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32R-300
Tail NumberN424TP
Aircraft CategoryAir
DamageMinor
OperatorBrian J Inskeep
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · TO-540-KIG5D · Reciprocating · 300
Seats6

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 31 · Third Class

Conditions

ConditionsVMC
LightDaylight
Wind290° @ 12 kt
Visibility60 sm
CeilingBroken clouds 16000 ft
Temperature / Dew Point37 C
Altimeter29.00 inHg
Observation Time22:45
Weather SourceWFAC

Appendix: Source Data