CEN20CA226 · Bellanca 17 30 Undesignat
Bellanca 17 30 Undesignat · Accident: hard landing
From Wichita Valley Airport (F14) to Talihina Municipal Airport (6F1)
Event
- NTSB case
- CEN20CA226
- 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 30 Undesignat
- 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
- N6681V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wichita Valley Airport (F14), Wichita Falls, TXTo Talihina Municipal Airport (6F1), Talihina, OK
- Aircraft age
- About 53 years (built 1967)
- 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
- 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
- Hard landing
- 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 from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
After an uneventful local flight in the single-engine airplane, the pilot entered the landing pattern at his destination airport and the windsock indicated an almost perpendicular crosswind of about 10 knots. On final approach, after clearing a tree line, the pilot reduced engine power to land. As engine power and airspeed were reduced, the airplane's rate of descent suddenly increased. The pilot attempted to slow the rate of descent, but the airplane impacted the runway hard and bounced. The airplane exited the runway and impacted a berm. The nose landing gear collapsed, resulting in substantial damage to the front lower part of the fuselage and firewall. The pilot stated that, due to the crosswind and the trees at the end and side of the runway, he should have adjusted his landing point further down the runway to avoid possible wind anomalies.
Probable cause
The pilot's failure to maintain control of the airplane during a crosswind landing, which resulted in a hard landing and runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20CA226
- Event ID
- 20200608X84254
- Case number
- CEN20CA226
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
- 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, 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: cb4a3ee152a76b650f8d8e8498c7b8ddcae509b2321c0f0a24768c3b2d038be7; retrieved 2026-09-16T11:48:28.936Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: destination. Talihina is in Oklahoma, which is also the recorded accident state; the destination state TX is wrong.