SEA00LA146 · Jonas FALCON XP
Jonas FALCON XP · Accident: loss of engine power en route
From Eastern Oregon Regional Airport at Pendleton (PDT) to an unrecorded destination
Event
- NTSB case
- SEA00LA146
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Jonas FALCON XP
- Aircraft type
- Jonas FALCON XP
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N90345
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Eastern Oregon Regional Airport at Pendleton (PDT)To not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · climb to cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that after taking off and turning left to clear the runway, he felt a slight vibration and noticed a lack of thrust. He stated that the engine RPM was 'full at 6300' but that the plane was slowing. He reported that he then leveled out to regain speed, but that this was not effective. The pilot reported that he then turned left to land immediately on a parallel taxiway, and that he landed level but short of the taxiway. The landing was in grass adjacent to the taxiway. The landing roll was uneventful until the aircraft's main gear entered a 'rabbit hole' in the grass. The pilot reported that the aircraft's right axle then sheared, and that the aircraft did a 'flip flop' from the right wingtip to the left wing and stopped. The pilot stated that he suspected a gearbox failure as the reason for full engine RPM with no associated thrust.
Probable cause
A loss of engine power for undetermined reasons. A factor was rough/uneven terrain in the forced landing area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA00LA146
- Event ID
- 20001212X21619
- Case number
- SEA00LA146
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 2ed6066ee9607d85279507cd32f786e57a67b31e783a0927d989e265f2e4cfbd; retrieved 2026-09-22T12:38:13.480Z.