CEN12CA596 · Arvold Jordon R CH 750
Arvold Jordon R CH 750 · Accident: loss of control on ground during landing
From Eagle Ridge Ultralightport (43WI) to Eagle Ridge Ultralightport (43WI)
Event
- NTSB case
- CEN12CA596
- 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
- Unknown
- 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
Arvold Jordon R CH 750
- Aircraft type
- Arvold Jordon CH-750
- 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
- N32JA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Eagle Ridge Ultralightport (43WI), Colfax, WITo Eagle Ridge Ultralightport (43WI), Colfax, WI
- 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
- Landing · landing roll
- 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
- Loss of control on ground
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was landing on a grass strip toward the west. The pilot stated that the airplane touched down on the centerline of the runway and was slowing down when the airplane encountered a strong gust of wind from the right. The pilot was unable to correct for the gust of wind and the airplane impacted trees on the left side of the runway. Examination of the airplane revealed that the right wing spar was broken, and the left wing spar was bent. The pilot stated that there were no mechanical malfunctions or failures that would have precluded normal operation. The wind at the time of the accident was recorded as 090 degrees at 9 knots.
Probable cause
The pilot did not maintain control of the airplane while landing with a gusty crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12CA596
- Event ID
- 20120904X34015
- Case number
- CEN12CA596
- 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, coordinates. 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: 95a61fc77584e5478c2eb2740c92e45d7bd91c2bf77d284ffbdfa81a2e44e8ec; retrieved 2026-09-15T19:40:21.560Z.