- Date
- March 25, 2002, 10:40 local (18:40 UTC)
- Place
- Camarillo, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N2630UCessna 172R
- Weather
- Visual (VMC) · Day
- Status
- Completed · report June 8, 2005
- Report
- Approved by Office Director
- Parties
- FAA Flight Standards District Office
- FAA report
- 20020325004899A
- Case key
- 54399
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot's failure to maintain directional control.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
The student pilot reported that he was en route from Torrance to Santa Barbara, California, on a solo cross-country flight with a planned intermediate stop at Camarillo. On his first approach to runway 26 at Camarillo, he was uncomfortable with the approach and turbulence and made a go-around. On the second approach he made a normal landing, near the centerline. During the landing roll, the airplane veered to the right toward the runway edge, and he believed it was better to bring the airplane to a stop instead of initiating a go-around. The airplane left the runway edge and went into a gravel area where the pilot continued braking; however, the gravel ended and the airplane went into a plowed agricultural field where the nosewheel dug in and the airplane nosed over.
Factual narrative
On March 25, 2002, at 1040 Pacific standard time, a Cessna 172R, N2630U, nosed over after veering off the runway during landing at the Camarillo, California, airport. The student-certificated pilot, the sole occupant, was not injured. The airplane was substantially damaged. The instructional flight, operated under 14 CFR Part 91 by South Bay Aviation, originated at Torrance, California, at 1005. Visual meteorological conditions prevailed. The pilot filed a VFR flight plan but did not activate the flight plan after departure from Torrance.
The student pilot reported that he was en route from Torrance to Santa Barbara, California, on a solo cross-country flight with a planned intermediate stop at Camarillo. On his first approach to runway 26 at Camarillo, he was uncomfortable with the approach and turbulence and made a go-around. On the second approach he made a normal landing, near the centerline. During the landing roll, the airplane veered to the right toward the runway edge, and he believed it was better to bring the airplane to a stop instead of initiating a go-around. The airplane left the runway edge and went into a gravel area where the pilot continued braking; however, the gravel ended and the airplane went into a plowed agricultural field where the nosewheel dug in and the airplane nosed over.
The pilot reported no mechanical malfunctions.
Aircraft
- Registration
- N2630U
- Reported as
- Cessna 172R
- Category
- Airplane
- Serial number
- 17280568
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Registered owner
- South Bay Aviation, Inc.
- Airworthiness certificate
- Standard, Normal
- Departed
- TOA · Torrance, CA
- Destination
- CMA · Camarillo, CA
- Flight plan
- VFR
- Airport
- CMA · camarillo, runway 26, 6,010 × 150 ft, concrete
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Injuries
- None
- Certificate
- Student
- Medical
- Class 3
- Flight hours
- 56 total · 14 in this make and model · 6 as pilot in command
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 230° at 10 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 61 °F, dew point 46 °F
- Altimeter
- 30.05 inHg
- Observed at
- CMA
Docket · 1
The files NTSB released with the investigation on March 20, 2003, on NTSB’s docket system: statements, records, photos and specialists’ reports. 507 KB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.