FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04LA049 · Bellanca 17-30A

29 Dec 2003 · Wellington, KS, United States

Bellanca 17-30A · Accident: loss of control on ground/water during landing

From Shawnee Regional Airport (SNL) to Wellington Municipal Airport (EGT)

Report a problem

Event

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

Bellanca 17-30A

Aircraft type
Bellanca 17
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
N14763
Operator
Unknown
Onboard fatalities
Unknown
Route
From Shawnee Regional Airport (SNL), Shawnee, OKTo Wellington Municipal Airport (EGT), Wellington, KS
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
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
Destroyed

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 airplane was destroyed during landing roll when it impacted a concrete electrical box following an excursion off of runway 17. The pilot stated, "I (as pilot) made an input of right aileron down which [exacerbated the] skid, including [the] right wing tip scraping the runway. Aircraft departed runway. Aircraft returned to three wheels down within 40 feet of runway edge. Aircraft was uncontrollable on dry, dead grass." The concrete electrical box was located approximately 75 feet left of the runway. The Airport/Facility Directory contained published remarks that warned personnel and equipment would be working adjacent to that runway.

Probable cause

The pilot not maintaining directional control during the landing roll. Factors were the dry grass and the concrete box he encountered during his excursion off the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA049
Event ID
20031230X02097
Case number
CHI04LA049
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: 76c2748ca3d1a7e3803bed7823ffc85a08c330ae3364216b34f7b1f1b3957712; retrieved 2026-09-21T19:18:32.961Z.