# Accident 19910418011479A: Luscom 8A, Clark Fork, ID, April 18, 1991

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 18, 1991, 19:45 local time
- Place: Clark Fork, ID
- Damage: Destroyed
- Phase of flight: Unauth Low Level Opns
- Operating rules: General operating rules (Part 91)
- Location: 48.0591° N, 116.1700° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=48.0591&lon=-116.1700&mi=10
- Aircraft: N45656, a cancelled registration (https://openairdocs.org/deregistered/N45656-2012-11-14) (OpenAirDocs)
- Registry model: Luscombe 8A (registry code 8190104, https://openairdocs.org/model/luscombe-8a) (OpenAirDocs)
- Registry engine: Continental A&C75 series (registry code 17005, https://openairdocs.org/engine/continental-a-c75-series) (OpenAirDocs)
- Reported make and model: LUSCOM 8A
- Reported engine: CONT A658
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 900 total, 100 in this make and model, 100 in the last 90 days
- NTSB investigation: [NTSB SEA91LA088](https://openairdocs.org/ntsb/SEA91LA088) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19910418011479A

## Narrative

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

COLLIDED WITH OBJECT IN FLIGHT,BROKE WINDSHIELD.DITCHED AIRCRAFT IN RIVER,HIT TELEPHONE LINE DESENDING TO RIVER.

## 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 SEA91LA088](https://openairdocs.org/ntsb/SEA91LA088), Apr 19, 1991: Luscombe 8A (N45656), Clark Fork, ID, destroyed. Probable cause: THE PILOT-IN-COMMAND'S FAILURE TO MAINTAIN PROPER ALTITUDE IN CRUISE LIGHT RESULTING IN AN IN FLIGHT COLLISION WITH A WIRE AND SUBSEQUENT FORCED LANDING IN A RIVER.

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.