# Accident 19740330006099A: Luscom 8A, St George, KS, March 30, 1974

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 30, 1974
- Place: St George, KS
- Airport: Gellinger
- Damage: Substantial damage
- Phase of flight: Final Approach
- Location: 39.1926° N, 96.4183° W: Placed by OpenAirDocs: center of St. George, KS, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.1926&lon=-96.4183&mi=10
- Aircraft: N1136B, registered now (https://openairdocs.org/aircraft/N1136B) (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
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 152 total, 22 in this make and model, 40 in the last 90 days
- NTSB investigation: [NTSB MKC74DCQ33](https://openairdocs.org/ntsb/MKC74DCQ33) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19740330006099A

## Narrative

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

STRUCK TOP OF W BANK OF THE RAVINE AT RWY THRESHOLD.

## 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 MKC74DCQ33](https://openairdocs.org/ntsb/MKC74DCQ33), Mar 30, 1974: Luscombe 8A (N1136B), St George, KS, substantial damage

## Other reports on N1136B (1)

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

- [Incident 19780528040649I](https://openairdocs.org/incident/19780528040649I), May 28, 1978: Luscom 8 (N1136B), Wichita, KS, Minor damage. Student applied brakes on rollout and aircraft went up over on its' back.

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.