FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR25LA098 · Cessna 172 G

18 Feb 2025 · Oxnard, CA, United States

San Fernando Avitioin Cessna 172 G · Accident: loss of control on ground during landing

From Camarillo International Airport (CMA) to an unrecorded destination

Report a problem

Event

NTSB case
WPR25LA098
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 172 G

Aircraft type
Cessna 172
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
N3901L
Onboard fatalities
Unknown
Route
From Camarillo International Airport (CMA), Camarillo, CATo not recorded
Aircraft age
About 59 years (built 1966)
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
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

According to the student pilot, he had been practicing touch-and-goes. Upon the fifth landing, the airplane began to veer to the left. He attempted to correct with right rudder, however, the airplane exited the left side of the runway. Subsequently, the right main landing gear impacted a sign, which resulted in substantial damage to the fuselage. At the time of the accident, the student pilot was landing on runway 25 with the wind from 260° at 10 knots. The student pilot reported no preimpact mechanical malfunctions or anomalies that could have precluded normal operation.

Probable cause

The student pilot’s failure to maintain directional control during landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR25LA098
Event ID
20250219199724
Case number
WPR25LA098
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: 4ba3aaaa8c9ba863cd02a4e5971e88486616a73da466ed255b0a774a3c7111d6; retrieved 2026-09-16T19:40:35.574Z.