FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07CA163 · Schweizer G-164B

5 Jun 2007 · Walnut Ridge, AR, United States

Schweizer G-164B · Accident: loss of control on ground/water during landing

From Walnut Ridge, AR (private airstrip) to an unrecorded destination

Report a problem

Event

NTSB case
CHI07CA163
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

Schweizer 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
N3627B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Walnut Ridge, AR (private airstrip)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 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 · landing roll
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 control on ground/water
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

  • Pilot in command › Directional control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The agricultural airplane was substantially damaged when it impacted terrain during an aborted landing from runway 9 (2,640 feet by 50 feet, dry asphalt) at a private airstrip. The pilot reported that the airplane veered to the right after touchdown and subsequently departed the right side of the runway. The pilot added engine power to abort the landing, but the airplane impacted a rice levee and flipped twice before coming to a stop. The pilot did not report any mechanical malfunctions with the airplane that would have prevented its normal operation. Local winds at the time of the accident were 240 degrees magnetic at 5 knots.

Probable cause

The pilot's failure to maintain directional control of the airplane upon landing, which resulted in the airplane impacting a rice levee. The rice levee and the tailwind condition were contributing factors to the accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07CA163
Event ID
20070726X01020
Case number
CHI07CA163
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, 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: 269eef3e58fe37039bdf22ff564f0e2f5c9a902e60965b207f09cf5c7b4d3edc; retrieved 2026-09-21T18:29:57.943Z.