Cessna 152 accident near Lodi, California, June 14, 2000
On June 14, 2000, a Cessna 152, registered N67608, was substantially damaged in an accident near Lodi, California (Lodi Airport). It was a personal 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 pilot's inaccurate fuel consumption calculations, his misjudged in-flight planning, and his failure to flare during the landing attempt. A factor was the pilot's improper preflight inspection when he refueled the airplane.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 14, 2000
- Place
- Lodi, California · Lodi 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
- N67608 · registry record · serial 15281943
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Near the destination airport, the engine lost power. During the attempted forced landing on the airport the pilot landed hard. The pilot had purchased fuel just prior to his departure, having fueled the airplane himself. He stated that he had performed fuel consumption calculations during the flight. As he approached the destination airport, the engine began to run roughly, and abruptly lost all power. The pilot turned toward the airport but was too low and far out to fly a normal pattern. He said he set himself up for the final approach, with a tailwind, for runway 08. He stated he was unable to keep the airplane under control and landed abruptly with no landing flare. Postaccident examination of the airplane revealed that the right-hand fuel cap was missing. Also during the postaccident examination of the airplane, upon application of electrical power, both fuel tank quantity indicators registered empty.
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
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 121 hours in all; 114 in this make and model; 31 in the last 90 days; 25 in the last 30 days; 61 as pilot in command
- Medical certificate: Class 3 (valid medical--no waivers/lim.)
- Seat: left
The aircraft
- Airframe total time: 7,260 hours
- Last inspection: annual inspection, December 30, 1999; 57 hours since
- Maximum gross weight: 1,670 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O235-LQC (piston); 0 hours total
The flight
- Departed from: AJO Corona CA at 9:20 pm
- Destination: 103 CA
- Flight plan: none
- Runway 8, 3,085 ft by 42 ft
Weather at the time
- Light: daylight
- Wind: from 320° at 9 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 212°F (100°C), dew point 102°F (39°C)
- Altimeter: 29.00 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.