FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA239 · Cessna 150 M

1 Jun 2024 · San Juan, PR, United States

Ace Aviation Cessna 150 M · Accident: powerplant system/component malfunction/failure during takeoff

From Fernando Luis Ribas Dominicci Airport (SIG) to Mercedita International Airport (TJPS)

Report a problem

Event

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

Cessna 150 M

Aircraft type
Cessna 150
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
N6198K
Operator
Ace Aviation
Onboard fatalities
Unknown
Route
From Fernando Luis Ribas Dominicci Airport (SIG), San Juan, PRTo Mercedita International Airport (TJPS), Ponce, PR
Aircraft age
About 49 years (built 1975)
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
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
Powerplant system/component malfunction/failure
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

  • Aircraft › Aircraft power plant

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot and flight instructor reported that the engine lost power shortly after takeoff. ADS-B data showed that the airplane reached a maximum altitude of 213 ft above ground level (agl) before entering a descending left turn back toward the runway. The airplane impacted the ground before reaching airport property. Examination of the wreckage found substantial damage to the engine mounts, fuselage, both wings, the right horizontal stabilizer, and elevator. Examination of the engine revealed that the rocker shaft bosses for the No. 2 cylinder had failed. Metallurgical examination found that a portion of the cylinder head, which contained the rocker arm shaft, fractured due to fatigue cracking that had initiated along the bore for the shaft. Once this section of the cylinder head fractured, the remainder of the cylinder head holding the rocker shaft fractured from overstress, freeing the shaft and rocker arms. These fractures would prevent the proper function of the drivetrain, preventing the valves from opening and leading to the failure of the No. 2 cylinder. The housing boss bore walls exhibited wear significant enough to allow for movement of the bushings and shaft. The bore exhibited wear marks consistent with rotational and lateral movement of the shaft, and the adjacent bushings exhibited lateral wear marks. Many of these marks matched those observed on the shaft, indicating movement along these surfaces. This uneven wear likely led to the rocker arms pushing erratically on the valves, as evidenced by the off-center wear marks on the rocker arm and valve stem faces. This uneven movement and wear likely led to wobbling and sliding. This created more wear, which eventually resulted in fatigue cracking and the subsequent failure of the rocker shaft bosses. A review of maintenance records was unable to determine the number of hours on the cylinder. The review found no record of the No. 2 cylinder being removed and reinstalled on the engine. While the logs described that about 7 years before the accident three unspecified cylinders had been removed and replaced, no information regarding which position they were installed to, or their serial numbers were recorded. The engine was subject to an FAA airworthiness directive (AD), which stated that the cylinder rocker shaft bosses must be inspected “At the next cylinder removal from the engine, or engine overhaul, whichever occurs first, after the effective date of this AD, inspect the cylinder rocker shaft bosses for cracks….” Based on the records, it could not be determined whether the No. 2 cylinder had been inspected in accordance with the AD.

Probable cause

A partial loss of engine power due to the failure of the No. 2 cylinder rocker shaft bosses from fatigue cracking.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA239
Event ID
20240603194363
Case number
ERA24LA239
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, 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: a8867fab69e665e89f8b2bcd133fee0022d1c18fdd4ef33d43033893ab711048; retrieved 2026-09-16T18:49:43.373Z.