WPR22LA352 · Jacquneaux Glen R CGS HAWK Classic II
Jacquneaux Glen R CGS HAWK Classic II · Accident en route
From Hunt Field (KLND) to Kimball Municipal Robert E Arraj Field (KIBM)
Event
- NTSB case
- WPR22LA352
- 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
Jacquneaux Glen R CGS HAWK Classic II
- Aircraft type
- Jacquneaux Glen CGS HAWK
- 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
- N5148G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hunt Field (KLND), Lander, WYTo Kimball Municipal Robert E Arraj Field (KIBM), Kimball, NE
- Aircraft age
- About 19 years (built 2003)
- 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
- Defining eventThe 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
- Unknown or undetermined
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, about 40 minutes after departure at an altitude of about 9,500 ft mean sea level (msl), he decided to land off-airport due to severe up and down shaking of the experimental airplane’s empennage. The pilot reduced the throttle setting and initiated a glide. The pilot observed that the airplane remained stable during the glide, with no extreme vibration, and that he was able to manage the descent smoothly. Shortly after touchdown, the airplane bounced and landed hard on a field. Subsequently, the airplane nosed over and sustained substantial damage to the tail assembly. The wreckage was recovered from a field onto a flatbed truck by a local resident. The National Transportation Safety Board (NTSB) investigator-in-charge (IIC) interviewed the pilot after the accident and requested that he preserve the wreckage; however, the pilot had given the wreckage to the local resident who helped with the recovery. The pilot added that he was returning to his home country in two weeks when his visa expired. A Federal Aviation Administration (FAA) inspector took pictures of the airplane on top of the flatbed truck but was unable to conduct an examination of the airframe or engine. The pilot further reported during a follow-up interview that he believed the engine and frame installed were too heavy for the airframe, which resulted in the extreme airframe vibration. He added that the engine was from a pre-owned car and had been installed about 7 years before the accident. The pilot indicated that the violent shaking during the accident sequence was the first occurrence in the airplane's last 204 hours of flight, which spanned the last 90 days. The local resident reported that during the recovery process, the pilot admitted to using zip ties to keep sections of the airplane intact. The pilot was not responsive after several attempts to coordinate a follow-up examination. Moreover, despite several attempts, the local resident did not respond to the investigator’s request to examine the wreckage. Since the wreckage was not made available for examination, the reason for the reported airframe vibration could not be determined.
Probable cause
A reported severe airframe vibration and subsequent forced landing for reasons that could not be determined because the wreckage was not made available for examination.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22LA352
- Event ID
- 20220919105969
- Case number
- WPR22LA352
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 059bcad415dd00b0a306ad369320c81d7886942449002cc8f7b5c5f086e7af75; retrieved 2026-09-16T16:04:08.119Z.