FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX08LA055 · Cessna 152

1 Feb 2008 · Palo Alto, CA, United States

West Valley Flying Club Cessna 152 · Accident: hard landing

From Palo Alto Airport (PAO) to San Carlos Airport (SQL)

Report a problem

Event

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

Cessna 152

Aircraft type
Cessna 152
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
N49811
Onboard fatalities
Unknown
Route
From Palo Alto Airport (PAO), Palo Alto, CATo San Carlos Airport (SQL), San Carlos, CA
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
Landing · flare/touchdown
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
Hard landing
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

Prior to the accident flight, a maintenance inspection was performed. A piece of the baffling was found in the throat of the carburetor venturi. The carburetor was inspected and reinstalled on the airplane. On the accident flight, the pilot/mechanic performed a post maintenance run-up with no mechanical problems noted. She taxied the airplane to the runway for takeoff and performed another run-up. Again there were no mechanical problems noted, and all the gages showed normal indications. On the takeoff roll the engine developed 2,300 rpm’s. About 500 feet mean sea level (msl), she noticed a hesitation in the engine and decided to make a 180-degree turn back to the runway. The airplane was still high on the approach, so the pilot reduced the airspeed, performed S-turns, and then slipped the airplane to lose altitude. She was still high, and about halfway down the runway, she further reduced the airspeed, which increased the sink rate. She lowered the nose to slow the sink rate, and was in the process of raising the nose again to flare for landing when the nose struck the runway. An inspection of the engine revealed zero compression of the number 1 cylinder with blow-by past the piston rings and exhaust valve. Maintenance personnel also noted that the bottom number 1 cylinder spark plug was "excessively" fouled with carbon deposits. There were no problems noted with the carburetor.

Probable cause

Loss of engine power during the takeoff initial climb due to lack of compression to a cylinder.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX08LA055
Event ID
20080211X00174
Case number
LAX08LA055
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. 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: 81a620cbb617cb7e52a686943c794c02a88dfd9122397b0e9b71778283326f64; retrieved 2026-09-15T09:21:48.315Z.