Cessna 152 accident near Atwater, California, January 27, 2013
On January 27, 2013 at about 2:00 am local time, a Cessna 152, registered N68757, was substantially damaged in an accident during approach near Atwater, California (Castle Airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The student pilot's inadequate flight planning, which resulted in his getting lost and not being able to return to the airport before the fuel was exhausted and the engine lost power.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 27, 2013 · about 2:00 am local time · cases in 2013
- Place
- Atwater, California · Castle Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 152 · all 152s on the register
- Registration
- N68757 · no longer on the register · serial 15282360
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Upon arrival at the airport for the solo local flight, the student pilot performed a preflight inspection, during which he noted that the airplane had 12 gallons of fuel; he stated that the flight was expected to be 1.3 hours long. During the flight, the student became lost while attempting to return to his home airport. The student contacted air traffic control for assistance and was provided position reports back to the airport but was still unable to identify the airport until he was within about 10 miles of it. About this time, which was 2 hours into the flight, the engine began to run roughly and, shortly after, it lost power. The student's attempts to restart the engine were unsuccessful, so he configured the airplane at the best glide speed and conducted an off-airport landing. During the landing roll, the airplane impacted a small rise in the ground and then came to rest inverted. During recovery of the airplane, it was noted that the fuel tanks had not been compromised, and about 1 gallon of fuel was recovered from both of the fuel tanks. According to the Pilot's Operating Handbook, the airplane had a total usable fuel capacity of 24.5 gallons, 1.5 gallons of which were unusable; with full fuel, the airplane could have flown for about 3.4 hours. Based on the evidence, it is likely that the engine lost power due to fuel exhaustion because the airplane did not have sufficient fuel on board for the extended flight, which resulted from the student's inadequate flight planning.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during approach defining event
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level other cases naming the fuel system
- factor Personnel issues › Task performance › Planning/preparation › Flight planning/navigation › Student/instructed pilot
Dual student
- Certificate: student
- Flight time: 41 hours in all; 41 in this make and model
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 6,592 hours
- Last inspection: 100-hour inspection, January 17, 2013; 16 hours since
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-235-L2C (piston); 8,721 hours total
- Operator: Ks Aviation INC
The flight
- Departed from: MER Atwater CA
- Destination: MER Atwater CA
Weather at the time
- Light: daylight
- Wind: from 350° at 10 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 3,500 ft; clear
- Temperature: 55°F (13°C), dew point 43°F (6°C)
- Altimeter: 29.98 inHg
- Observation at 1:45 am from MER, 2 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
4 documents, released by the NTSB on March 10, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Pilot Statement | PDF, 2 pages | View Download |
| 3 | Pilot Written Statement (FAA) | PDF, 2 pages | View Download |
| 4 | FAA Inspector's Statement | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N68757: not on the register today · the record of its deregistration
- Cessna 152 1,635 registered today · the model family and its accident history
- Cessna 72,673 aircraft on the register
- Engine: Lycoming O-235-L2C 84 aircraft carry this series today · as the NTSB recorded it
- Castle Airport · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,093 in the last ten years
- California 28,515 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR13LA106.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
