FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA010 · Zodiac 601

9 Oct 2024 · Augusta, KS, United States

Zodiac 601 · Accident: loss of control on ground during landing

From Brady-Pippin Airport (SN20) to Brady-Pippin Airport (SN20)

Report a problem

Event

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

Zodiac 601

Aircraft type
Zodiac 601
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
N601KM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Brady-Pippin Airport (SN20), Augusta, KSTo Brady-Pippin Airport (SN20), Augusta, KS
Aircraft age
About 22 years (built 2002)
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
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 › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that during the landing roll, he inadvertently applied and removed engine power, which resulted in a loss of directional control of the airplane. He was unable to regain control of the airplane. The airplane exited the runway and struck a fence, which resulted in substantial damage to both wings, aft fuselage, and empennage. The pilot reported that there were no preimpact mechanical failures or malfunctions that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain directional control during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA010
Event ID
20241010195290
Case number
CEN25LA010
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: 6881ae98b6a8b36653246d23073282af38bd7a359d34686d0abda24ea5256a9d; retrieved 2026-09-16T19:22:01.429Z.