LAX02LA154 · Cessna 152
Cessna 152 · Accident: on ground/water collision with object while taxiing
From Sacramento Executive Airport (KSAC) to Sacramento, CA
Event
- NTSB case
- LAX02LA154
- 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
- N67975
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sacramento Executive Airport (KSAC), Sacramento, CATo Sacramento, 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
- Taxi · to runway
- 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
- On ground/water collision with object
- 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 › Aircraft control, not maintained
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Brakes(normal), inadvertent deactivation
- Pilot in command › Parking brakes, not used
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane collided with two parked fuel trucks while taxiing for takeoff. The pilot stated that she started the airplane after fueling it and was holding the brakes. She felt like she needed to move her seat forward slightly and grabbed the dash with one hand while releasing the seat lock with the other. The seat then slid all the way back on the tracks and her feet were now off the pedals. The airplane began to move forward and she could not reach the pedals and her passenger, who had no prior flight experience, tried to push on the bottoms of the pedals instead of the tops to activate the brakes. Before the pilot could take further remedial actions, the airplane taxied into two parked fuel trucks.
Probable cause
Failure of the pilot to ensure the seat was set properly prior to engine start, and not using the parking brake when adjustment of seat was necessary, which resulted in the inadvertent deactivation of the brakes and subsequent collision with the fuel trucks.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02LA154
- Event ID
- 20020510X00661
- Case number
- LAX02LA154
- 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: e67b604e27eab3fffc112d85f9d3d1e735a8e209caf5618a768e731dfc250c3e; retrieved 2026-09-22T10:57:16.678Z.