# Accident 20031203033829A: Cessna 152, Waterford, MI, December 3, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: December 3, 2003, 10:30 local time
- Place: Waterford, MI
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 42.6653° N, 83.4186° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=42.6653&lon=-83.4186&mi=10
- Aircraft: N65455, a cancelled registration (https://openairdocs.org/deregistered/N65455-2005-08-01) (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 O235*
- Fatal injuries: 0
- Pilot flight hours: 330 total, 23 in this make and model, 23 in the last 90 days
- NTSB investigation: [NTSB CHI04LA039](https://openairdocs.org/ntsb/CHI04LA039) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031203033829A

## Narrative

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

(-23) AIRCRAFT WAS FORCED TO MAKE AN EMERGENCY LANDING IN A FIELD. FAA INSPECTORS ON SCENE FOUND THAT THERE WAS NO USABLE FUEL IN THE FUEL TANKS, LINES, OR CARBURETOR.

## 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 CHI04LA039](https://openairdocs.org/ntsb/CHI04LA039), Dec 3, 2003: Cessna 152 (N65455), Pontiac, MI, substantial damage. Probable cause: The loss of engine power for undetermined reasons. A factor to the accident was the tree line and the unsuitable terrain.

## Other reports on N65455 (2)

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

- [Incident 19920901038299I](https://openairdocs.org/incident/19920901038299I), Sep 1, 1992: Cessna 152 (N65455), West Friendship, MD. Student pilot became lost on VFR crosscountry flight. Forced landing in field due to fuel exhaustion.
- [Incident 19880328015599I](https://openairdocs.org/incident/19880328015599I), Mar 28, 1988: Cessna 152 (N65455), Gaithersburg, MD, Minor damage. Lost directional control on a takeoff roll while practicing touch and go landings. Veered off runway. Hit a tree.

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.