FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC04LA221 · Piper PA-30

28 Aug 2004 · Cynthiana, KY, United States

Piper PA-30 · Accident: loss of control on ground/water during takeoff

From Cynthiana-Harrison County Airport (0I8) to Mount Sterling Montgomery County Airport (IOB)

Report a problem

Event

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

Piper PA-30

Aircraft type
Piper PA-30
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
N888LC
Onboard fatalities
Unknown
Route
From Cynthiana-Harrison County Airport (0I8), Cynthiana, KYTo Mount Sterling Montgomery County Airport (IOB), Mount Sterling, KY
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
Takeoff · roll/run
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
Loss of control on ground/water
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

  • Landing gear, normal brake system › Malfunction

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

NTSB narrative

The pilot was conducting the first flight of the airplane after an annual inspection had been performed. The start-up, taxi, and run-up all appeared to be "normal", so the pilot elected to depart. During the takeoff roll, at an airspeed of about 70 knots, the airplane yawed left, departed the runway pavement, and struck a windsock pole. Following the accident, a mechanic examined the brake systems of the airplane, and noted that the left main gear parking brake was improperly connected, and the left main gear brake check valve was inoperative resulting in constant pressure being placed to the left brake calipers.

Probable cause

The inoperative left main landing gear brake check valve, which resulted in a loss of directional control during the takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC04LA221
Event ID
20041025X01693
Case number
NYC04LA221
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: eac6f43d3a20990ba870b40b90294a8963a0faf2e9ccc2c871d6669a52016403; retrieved 2026-09-22T06:49:41.121Z.