# Accident 20000309043959A: Cessna 152, Lake Charles, LA, March 9, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 9, 2000, 20:13 local time
- Place: Lake Charles, LA
- Damage: Substantial damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 30.2093° N, 93.1992° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=30.2093&lon=-93.1992&mi=10
- Aircraft: N68333, a cancelled registration (https://openairdocs.org/deregistered/N68333-2013-05-02) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Reported engine: LYC O235L2C
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 450 total, 178 in this make and model, 7 in the last 90 days
- NTSB investigation: [NTSB FTW00LA094](https://openairdocs.org/ntsb/FTW00LA094) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000309043959A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) SUBJECT PILOT CONTACTED LAKE CHARLES APPROACH END AND ASKED FOR VECTORS FIRST TO CHENNAULT INTL, THEN LAKE CHARLES REGIONAL, THEN TO NEAREST AIRPORT. AT APPROXIMATELY 2013 LOCAL TIME THE PILOT TOLD APPROACH HE WAS HAVING ENGINE PROBLEMS. WHEN THE CONTROLLER ASKED FOR NUMBER OF PEOPLE ON BOARD AND FUEL, THE PILOT RESPONDED TWO AND ABOUT TWENTY MINUTES. AIRCRAFT CONTACT WAS LOST. PILOT MADE FORCED LANDING APPROXIMATELY 5.5 MILES BEARING 320 DEGREES FROM THE LAKE CHARLES MUNICIPAL AIRPORT. INVESTIGATION YIELDED THE FOLLOWING: AIRCRAFT HOLDS 26 GALLONS TOTAL, WITH USABLE QUANTITY OF 24.5 US GALLONS. AFTER RIGHTING AIRCRAFT, NO EVIDENCE OF FUEL LEAKAGE WAS FOUND. APPROXIMATELY 1.5 GALLONS WERE DRAINED FROM THE LEFT TANK AND .05 GAL (6.4 OUNCES) FROM THE RIGHT TANK. ALL FUEL FILTERS WERE CLEAN AND NO OBSTRUCTION TO FUEL FLOW COULD BE FOUND. IN CHECKING FOR IGNITION INTEGRITY, THE ENGINE FIRED BRIEFLY. NO MECHANICAL ABNORMALITIES READILY EVIDENT. IN MY OPINION THE FACTS SHOW FUEL EXHAUSTION.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB FTW00LA094](https://openairdocs.org/ntsb/FTW00LA094), Mar 10, 2000: Cessna 152 (N68333), Lake Charles, LA, substantial damage. Probable cause: The failure of the pilot to refuel the airplane which resulted in fuel exhaustion. Factors were the pilot's poor preflight planning, failure to lean the mixture in accordance with the POH, and lack…

## Other reports on N68333 (4)

Matched to the same aircraft by N-number and date.

- [Incident 19821029066839I](https://openairdocs.org/incident/19821029066839I), Oct 29, 1982: Cessna 152 (N68333), Ft Worth, TX, Minor damage. Crashed when aircraft was landed on the nose wheel.
- [Incident 19810604036769I](https://openairdocs.org/incident/19810604036769I), Jun 4, 1981: Cessna 152 (N68333), Fort Worth, TX, Minor damage. Student solo bounced on landing another 3 point on second contact with nose wheel shimmy. Wheel and fork separated.
- [Accident 19790605026279A](https://openairdocs.org/incident/19790605026279A), Jun 5, 1979: Cessna 152 (N68333), Kellerrth, TX, Substantial damage. Made slow final approach to lndg. Acft hit short of runway, bounced, nosewheel collapsed..
- [Incident 19790517027139I](https://openairdocs.org/incident/19790517027139I), May 17, 1979: Cessna 152 (N68333), Dallas, TX. Student had electrical failure at night. Landed dfw, taxied into grass and spent the night.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.