# Incident 19860924069069I: Cessna 152, Terre Haute, IN, September 24, 1986

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 24, 1986, 18:10 local time
- Place: Terre Haute, IN
- Airport: Hulman Regional
- Phase of flight: In Traffic Pattern-Circling
- Operating rules: General operating rules (Part 91)
- Location: 39.4667° N, 87.4139° W: Placed by OpenAirDocs: center of Terre Haute, IN, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.4667&lon=-87.4139&mi=10
- Aircraft: N67520, a cancelled registration (https://openairdocs.org/deregistered/N67520-2013-02-13) (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
- Fatal injuries: 0
- Pilot flight hours: 420 total, 300 in this make and model, 90 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19860924069069I

## Narrative

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

SAFELY LANDED AIRCRAFT AFTER POWER LOSS ON DOWNWIND. ENGINE WAS RUN UP. STARTED TAKEOFF ROLL, ENGINE QUIT. NO FUEL.

## Other reports on N67520 (2)

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

- [Accident 20040926034549A](https://openairdocs.org/incident/20040926034549A), Sep 26, 2004: Cessna 152 (N67520), Springboro, OH, Substantial damage. (-23) On September 26, 2004 at approximately 1825 local, a Cessna 152, N67520 was substantially damaged while attempting to make an emergency landing at dayton…
- [Accident 19851026054002A](https://openairdocs.org/incident/19851026054002A), Oct 26, 1985: Cessna 152 (N67520), Clinton, IN, Substantial damage. Struck from above and behind by 10769. Touchdown was completed when metal sounds were heard. Lost control.

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.