CEN23LA375 · Schweizer Aircraft Corp G-164B
Schweizer Aircraft Corp G-164B · Accident: loss of control on ground during landing
From Fort Ripley, MN to an unrecorded destination
Event
- NTSB case
- CEN23LA375
- 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
Schweizer Aircraft Corp G-164B
- Aircraft type
- Schweizer G-164
- 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
- N943QC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Ripley, MNTo not recorded
- Aircraft age
- About 40 years (built 1983)
- 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 137: Agricultural
- 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
- 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
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he performed a straight in landing to a private airstrip. He anticipated a crosswind from the east, so he made the approach with additional airspeed to have more controllability in the crosswind. He stated that he landed about two thirds of the way down the 2,574 ft runway, reduced power, and reduced the propeller pitch to low. The tailwheel settled to the ground at a location on the runway where there was a break in the adjacent tree line. The pilot reported that the crosswind intensified at this point, and the airplane yawed to the left. The left main landing gear exited the paved portion of the runway. The pilot attempted to correct with rudder and brakes; however, the airplane continued off the runway and into a plowed field. The airplane nosed over and came to rest inverted in the field. The vertical stabilizer was substantially damaged. The pilot reported that there were no mechanical failures or malfunctions with the airplane that would have precluded normal operation. At the time of the accident, wind at an airport 12 nm northwest of the accident site was 090°at 8 knots. The pilot was landing to the south.
Probable cause
The pilot’s failure to maintain directional control during the landing roll with a left crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA375
- Event ID
- 20230822192918
- Case number
- CEN23LA375
- 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: 5778c3e9591aa3373cf6636c39558dfe0e0c4cd596d07826f6c05b59511d02a3; retrieved 2026-09-16T18:02:02.717Z.