# Accident 20060903029439A: Luscom 8A, Elwell, MI, September 3, 2006

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 3, 2006, 13:00 local time
- Place: Elwell, MI
- Airport: Hamp Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 43.3994° N, 84.8003° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=43.3994&lon=-84.8003&mi=10
- Aircraft: N28403, a cancelled registration (https://openairdocs.org/deregistered/N28403-2013-05-31) (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 certificates: Student
- Pilot flight hours: 71 total, 71 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB CHI06CA251](https://openairdocs.org/ntsb/CHI06CA251) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060903029439A

## Narrative

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

(-23) PILOT LANDED AIRCRAFT NEAR MID-POINT OF RUNWAY LENGTH, OVER-APPLIED BRAKES, CAUSING AIRCRAFT TO FLIP TAIL-OVER-NOSE, COMING TO REST ON TOP.

## 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 CHI06CA251](https://openairdocs.org/ntsb/CHI06CA251), Sep 3, 2006: Luscombe 8A (N28403), Elwell, MI, substantial damage. Probable cause: The airplane nosed over as a result of the pilot's excessive braking after he failed to attain the proper touchdown point and failed to perform a go-around.

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.