NYC05LA118 · Piper PA-28-180
Piper PA-28-180 · Accident: loss of engine power during initial climb
From Elyria Airport (1G1) to Canton-Plymouth-Mettetal Airport (1D2)
Event
- NTSB case
- NYC05LA118
- 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-28-180
- Aircraft type
- Piper PA-28
- 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
- N9233J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Elyria Airport (1G1), Elyria, OHTo Canton-Plymouth-Mettetal Airport (1D2), Plymouth, MI
- 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
- Initial climb
- 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 engine power
- 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
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
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 reported that the airplane accelerated and lifted off of the 3,053-foot-long, asphalt runway; however, when the airplane was about 200 to 300 feet above the ground, he felt a loss of engine power. The airplane began to sink, impacted trees, and came to rest in a wooded area, about 600 feet northeast of the departure end of the runway. Post accident examination of the airplane did not reveal any mechanical malfunctions. Review of airplane maintenance records revealed the most recent annual inspection was performed about 7 months prior to the accident. The airplane had been operated for 3 hours since the inspection, and a total of about 50 hours during the 3 years prior to the inspection. The pilot reported 225 hours of total flight experience, which included about 57 hours accumulated in the same make and model as the accident airplane.
Probable cause
A loss of engine power during initial climb, as reported by the pilot, for an undetermined reason which resulted in a collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC05LA118
- Event ID
- 20050714X01013
- Case number
- NYC05LA118
- 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: 287f32770f787391dba5b83d68ec722e3c69d36b2cf1367adf69974a9058d5f6; retrieved 2026-09-21T09:05:20.408Z.