MIA05LA093 · Piper PA-28-161
Orlando Flight Training Piper PA-28-161 · Accident: partial loss of engine power (mechanical failure) en route
From Seminole Lake Gliderport (6FL0) to Kissimmee Gateway Airport (KISM)
Event
- NTSB case
- MIA05LA093
- 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-161
- 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
- N270FT
- Operator
- Orlando Flight Training
- Onboard fatalities
- Unknown
- Route
- From Seminole Lake Gliderport (6FL0), Groveland, FLTo Kissimmee Gateway Airport (KISM), Kissimmee, 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 · climb to 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
- Partial loss of engine power (mechanical 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
- Substantial
Cause areas
- Pilot in command › Planned approach, poor
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/mechanic arrived at the Seminole Lake Gliderport to repair the engine following an uneventful precautionary landing the day before due to a bent exhaust pushrod of the No. 2 cylinder. He replaced the damaged No. 2 cylinder exhaust pushrod, pushrod housing, pushrod seals and lock tab. He reported visually inspecting the valve springs which did not appear to be damaged, but did not inspect the valve, nor did he remove the cylinder. Following the repairs, the engine was started and a full static run-up was performed with no discrepancies noted. The flight departed for Kissimmee Gateway Airport and shortly after takeoff, the engine started running rough though it was still producing power. He elected to return to the Seminole Lake Gliderport and after recognizing he was going to overshoot the runway with the engine not producing full power, elected to perform a 360-degree turn back onto final approach. During the turn, the aircraft impacted trees and came to rest in a swamp south of the south edge of runway 18. A pilot-rated witness observed the airplane on final approach and noted that as it descended to treetop level, or the height of the buildings, the airplane began to abruptly pitch up and down and was abruptly yawing. It appeared to the pilot-rated witness that some of the motions of the airplane did not coincide with the wind conditions that he observed. Postaccident examination of the engine by an FAA inspector revealed the replaced pushrod was damaged on both ends, with no obvious indication of a stuck valve. Additionally, the rotator type exhaust valve stem cap was missing from under the exhaust rocker arm of the No.2 cylinder. The exhaust valve and guide were within new limits in compliance with the Lycoming overhaul manual. There was no evidence of carbon inside the guide; however, there was swirl marks from reaming of the guide. Review of Lycoming Service Bulletin (SB) No. 388C revealed inspection procedures to be carried out at 400 hours or earlier, when valve sticking is suspected. The SB indicates that failure to comply with this provision could result in sticking valves, or broken exhaust valves which could result in engine failure. A section of the SB outlines the inspection procedure that uses a "GO/NO-GO" gage, and recommends moving the exhaust valve completely out of the guide to avoid interference when using the GO/NO-GO gage to check the guide for wear or carbon build up. The mechanic did not report using the GO/NO-GO gage. Additionally, the mechanic did not report using a local manufactured tool.
Probable cause
The pilot's poorly planned approach during a precautionary landing following partial loss of engine power resulting in a go-around and subsequent in-flight collision with trees. A contributing factor in the accident was the inadequate maintenance by the mechanic/pilot for his failure to comply with Lycoming SB 388C, following a stuck exhaust valve.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA05LA093
- Event ID
- 20050419X00474
- Case number
- MIA05LA093
- 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: bda9d4e43150cd75837282b29ae3dd95c6a76c7e2a75dd20b0277b9cf793c3fb; retrieved 2026-09-22T06:04:07.443Z.