# N90345: 2000 Jonas Steve W FALCON XP, registration cancelled 2013-04-16

- Type: Cancelled registration (FAA registry, deregistered aircraft)
- Cancelled: April 16, 2013
- Status when cancelled: Sale reported, pending cancellation
- Airframe: [Jonas Steve W FALCON XP](https://openairdocs.org/model/jonas-steve-w-falcon-xp) (registry code 05610E1)
- Engine: [Bombardier ROTAX (ALL)](https://openairdocs.org/engine/bombardier-rotax-all) (registry code 09050)
- Serial number: 600520
- Year built: 2000
- Type of aircraft: Fixed wing single engine
- Engine type: Reciprocating
- Kit: American Aircraft FALCON
- Airworthiness: Experimental, amateur built
- Airworthiness date: July 15, 2000
- Last registry action: June 6, 2002
- Mode S code: AC7D53
- Location: [Oklahoma City, OK](https://openairdocs.org/faa-place/OK/Oklahoma%20City)
- Owner type: Individual
- Owner's area on the map: 35.4676° N, 97.5164° W: Placed by OpenAirDocs: center of Oklahoma City, OK, within about 14 miles (OpenAirDocs). The owner's mailing address, not where the aircraft was based
- The mark today: https://openairdocs.org/aircraft/N90345
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=90345
- Page: https://openairdocs.org/deregistered/N90345-2013-04-16

From the FAA registry file of November 4, 2026, cancelled registrations. Owners' street addresses are left out. The Mode S code belongs to the N-number, not the airframe.

ADs and bulletins for the Jonas Steve W FALCON XP: https://openairdocs.org/model/jonas-steve-w-falcon-xp.md

## NTSB investigations (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 SEA00LA146](https://openairdocs.org/ntsb/SEA00LA146), Jul 30, 2000: Jonas Falcon XP (N90345), Pendleton, OR, substantial damage. Probable cause: A loss of engine power for undetermined reasons. A factor was rough/uneven terrain in the forced landing area.

## FAA accident and incident reports (1)

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 20000730006129A](https://openairdocs.org/incident/20000730006129A), Jul 30, 2000: Amtr FALCONXP (N90345), Pendleton, OR, No damage. (-23) After take-off, pilot noticed that the a/c was not producing sufficient power to continue departure. Decision was made to return to the airport. Upon…

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