# Accident 20130222002979A: Luscombe 8A, Lebanon, OR, February 22, 2013

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 22, 2013, 09:30 local time
- Place: Lebanon, OR
- Airport: Tallman Airport
- Damage: Substantial damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 44.5683° N, 122.9714° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=44.5683&lon=-122.9714&mi=10
- Aircraft: N1192K, a cancelled registration (https://openairdocs.org/deregistered/N1192K-2018-01-02) (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: LUSCOMBE 8A
- Reported engine: CONT MOTOR A&C65 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 716 total, 328 in this make and model, 14 in the last 90 days
- NTSB investigation: [NTSB WPR13CA133](https://openairdocs.org/ntsb/WPR13CA133) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130222002979A

## Narrative

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

PILOT DECIDED TO LAND IN A FIELD SHORTLY AFTER TAKEOFF DUE TO STRONG CROSSWINDS. THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE AFTER HITTING A FENCE AND CROSSING A DITCH.

## 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 WPR13CA133](https://openairdocs.org/ntsb/WPR13CA133), Feb 22, 2013: Luscombe 8A (N1192K), Lebanon, OR, substantial damage. Probable cause: The pilot’s failure to compensate for a crosswind during initial climb, which resulted in a loss of 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.