# N25342: not currently registered

- Registered now: No (not in the FAA registry file). The mark may be reserved or free to assign
- Earlier aircraft: 1
- Last cancelled: September 21, 2024
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=25342
- Page: https://openairdocs.org/aircraft/N25342

## Aircraft that carried N25342

- [Cancelled 2024-09-21](https://openairdocs.org/deregistered/N25342-2024-09-21): Luscombe 8A, S/N 1218. Registration pending, canceled. Owner: [Prescott Valley, AZ](https://openairdocs.org/faa-place/AZ/Prescott%20Valley)

## NTSB investigations on N25342 (4)

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 CEN23LA117](https://openairdocs.org/ntsb/CEN23LA117), Feb 20, 2023: Luscombe 8A (N25342), Guthrie, OK, substantial damage. Probable cause: The student pilot’s failure to maintain directional control during the landing roll.
- [NTSB CEN09CA001](https://openairdocs.org/ntsb/CEN09CA001), Oct 3, 2008: Luscombe 8A (N25342), Greeley, CO, substantial damage. Probable cause: The pilot's failure to maintain directional control during the landing roll resulting in a ground loop. Contributing to the accident was the lack of remedial action from the flight instructor.
- [NTSB CHI03LA292](https://openairdocs.org/ntsb/CHI03LA292), Aug 21, 2003: Luscombe 8A (N25342), Macon, MO, substantial damage. Probable cause: The pilot's improper use of the rudder, which resulted in directional control not being maintained during the landing. A factor to the accident was the crosswind gust.
- [NTSB CHI86LA107](https://openairdocs.org/ntsb/CHI86LA107), Mar 23, 1986: Navion H (N25342), Columbus, IN, substantial damage

## FAA accident and incident reports on N25342 (4)

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.

- [Accident 20230220001209A](https://openairdocs.org/incident/20230220001209A), Feb 20, 2023: Luscombe 8A (N25342), Guthrie, OK, Substantial damage. On February 20, 2023 at approximately 1100 hours CST, a 1940 Luscombe 8A tail dragger [privacy data omitted] was on a student pilot solo flight and landed on…
- [Accident 20081003851129A](https://openairdocs.org/incident/20081003851129A), Oct 3, 2008: Luscom 8A (N25342), Greeley, CO, Substantial damage. (-23) On October 3rd 2008, at 10:45, N25342, a Luscom 8A, ground looped while performing touch and goes at Greeley Weld county airport (gxy), Colorado. The…
- [Accident 20030821021749A](https://openairdocs.org/incident/20030821021749A), Aug 21, 2003: Luscom 8A (N25342), Macon, MO, Substantial damage. (-23) The pilot was approaching Macon, MO (K89) from the west as thunderstorms were forming in the vicinity. The airplane touched down on runway 20 with all…
- [Incident 19830806044009I](https://openairdocs.org/incident/19830806044009I), Aug 6, 1983: Luscom 8A (N25342), Loveland, CO, Minor damage. Lost directional control landing on taxiway parallel to runway. Airport manager approved. Main runway closed.

---
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.