# Accident 20070525009119A: Luscom 8A, Elwood, IN, May 25, 2007

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 25, 2007, 09:30 local time
- Place: Elwood, IN
- Airport: Private
- Damage: Destroyed
- Phase of flight: Sfl Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 40.2333° N, 85.8167° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.2333&lon=-85.8167&mi=10
- Aircraft: N2897K, a cancelled registration (https://openairdocs.org/deregistered/N2897K-2021-05-08) (OpenAirDocs)
- Registry model: Luscombe 8A (registry code 8190104, https://openairdocs.org/model/luscombe-8a) (OpenAirDocs)
- Registry engine: Continental A&C65 series (registry code 17003, https://openairdocs.org/engine/continental-a-c65-series) (OpenAirDocs)
- Reported make and model: LUSCOM 8A
- Fatal injuries: 0
- Pilot flight hours: 1,900 total, 800 in this make and model, 17 in the last 90 days
- NTSB investigation: [NTSB CHI07CA156](https://openairdocs.org/ntsb/CHI07CA156) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20070525009119A

## Narrative

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

(-23) ON MAY 25, 2007 AT APPROXIMATELY 0930 LOCAL TIME WHILE PERFORMING A SIMULATED FORCED LANDING AT A PRIVATE AIRSTRIP SOUTH EAST OF ELWOOD INDIANA THE AIRCRAFT'S MAIN LANDING GEAR AND LEFT WING STRUCK THE GROUND, THE AIRCRAFT CART-WHEELED ACROSS THE GRASS RUNWAY AND BROKE INTO THREE PIECES. THE AIRCRAFT WAS DESTROYED.

## 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 CHI07CA156](https://openairdocs.org/ntsb/CHI07CA156), May 25, 2007: Luscombe 8A (N2897K), Elwood, IN, substantial damage. Probable cause: The commercial pilot's failure to maintain adequate altitude and airspeed which resulted in the airplane mushing into the terrain during the simulated forced landing along with the CFI's failure to…

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.