CEN21LA035 · Piper PA28 140
Coastal Skies Aero Club Piper PA28 140 · Accident
From an unrecorded airport to Pearland Regional Airport (LVJ)
Event
- NTSB case
- CEN21LA035
- 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
- Event fatalities
- Unknown
- 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 PA28 140
- Aircraft type
- Piper PA28
- 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
- N32458
- Operator
- Coastal Skies Aero Club
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Pearland Regional Airport (LVJ), Pearland, TX
- Aircraft age
- About 46 years (built 1974)
- 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
- Unknown
- Defining eventThe 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
- Unknown or undetermined
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor and his student were departing on an instructional flight from a private grass airstrip. The pilots completed a before-takeoff engine runup with no anomalies or malfunctions reported. The flight instructor reported that his student performed the soft-field takeoff. After the airplane became airborne, the student reduced airplane pitch to remain within ground effect, and allowed the airspeed to increase to 80 knots. The flight instructor reported that during the initial climb there was a drop in engine speed (rpm). The flight instructor confirmed the throttle control was full forward, but there was “no significant engine performance.” The flight instructor took control of the airplane from his student, reduced pitch, and banked to avoid the highway and powerlines located at the end of the airstrip. The flight instructor stated that a lack of engine performance resulted in a forced landing before the airplane completed 90° of turn from the takeoff heading. The airplane landed on the northside of the highway, collided with a power pole, and came to a stop. The airplane’s left wing and engine mount were substantially damaged during the accident.
According to the flight instructor, the airplane’s flaps were extended 10° for the soft-field takeoff based on a laminated checklist in the cockpit. The airplane’s owner’s handbook requires the flaps to be extended 25° for a soft-field takeoff. However, according to the flight instructor, the airplane became airborne and accelerated to a safe airspeed before it climbed out of ground effect. As such, the incorrect flap extension likely did not contribute to the accident.
Postaccident engine examination revealed low cylinder compression and an oil-fouled lower spark plug for the No. 1 cylinder. Otherwise, the examination did not reveal any anomalies. The engine was subsequently started and run several times without any issues; however, the engine was not accelerated to maximum static rpm during the examination due to a damaged engine mount and the airplane being supported on jack-stands.
The flight instructor reported a decrease in engine rpm during initial climb out of ground effect. Although engine performance would be diminished by a low cylinder compression and an oil-fouled lower spark plug for the No. 1 cylinder, those discrepancies would not result in a sudden loss of engine rpm during flight. As such, the low cylinder compression and/or oil-fouled spark plug likely did not result in the reported decrease in engine rpm as described by the flight instructor.
The temperature and dewpoint at the time of the accident were in the range of susceptibility for the formation of serious carburetor icing at glide power. Although a formation of carburetor ice before takeoff could have resulted in a sudden decrease in engine rpm, the pilots completed a before-takeoff engine runup with no anomalies or malfunctions reported.
The reason for the partial loss of engine power could not be determined.
Probable cause
The partial loss of engine power for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21LA035
- Event ID
- 20201029102209
- Case number
- CEN21LA035
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: e3b1809c321ef150056f0f27a80b486f02c12492d166b3997004215d994feb35; retrieved 2026-09-16T13:18:47.335Z.