FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08CA198 · Cessna 152

13 Sept 2008 · Columbia, CA, United States

Flying Vikings Cessna 152 · Accident: loss of control on ground during landing

From Hayward Executive Airport (KHWD) to Columbia Airport (O22)

Report a problem

Event

NTSB case
SEA08CA198
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
N24342
Onboard fatalities
Unknown
Route
From Hayward Executive Airport (KHWD), Hayward, CATo Columbia Airport (O22), Columbia, 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 · landing roll
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
Loss of control on ground
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 oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The student pilot was on a solo cross-country flight and was landing at his planned destination. During the landing flare, he added engine power to help arrest the rate of descent, but after making a smooth successful touchdown, he forgot to reduce the engine power back to idle. With significantly greater than idle power being produced by the engine, the pilot lost directional control during his attempt to slow the airplane. The airplane veered off the runway and impacted a wall of boulders that had been erected as a barrier.

Probable cause

The student pilot's failure to maintain directional control during the landing roll. Contributing to the accident was the student pilot's improper use of the throttle control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08CA198
Event ID
20081003X71057
Case number
SEA08CA198
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. 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: 4c1e3191536dd85b1bf8d2de1af1c0f053136e8fd89dbeba04bdeb6461062fad; retrieved 2026-09-15T10:22:21.372Z.