ATL03FA125 · Bellanca 7KCAB
Bellanca 7KCAB · Accident: in flight encounter with weather en route
From Short Creek Airport (8TN7) to KFIO · Paducah, KY
Event
- NTSB case
- ATL03FA125
- 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
- 2 · 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 7KCAB
- Aircraft type
- Bellanca 7
- 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
- N68551
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Short Creek Airport (8TN7), Dover, TNTo KFIO · Paducah, KY
- 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
- En route · cruise
- 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
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › Flight into adverse weather, continued
- Pilot in command › VFR flight into imc, continued
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 departed a private airstrip shortly before the arrival of a thunderstorm, and one witness stated it used an abnormal amount of runway. A second witness stated the engine sounded like it was laboring, and another witness stated it sounded normal. One witness described the storm as a "virtual wall of water." The airplane was not equipped with an artificial horizon instrument. When the airplane failed to arrive at its destination, a search was initiated. On June 22, 2003, a portion of the left main landing gear strut and tire was located in the river a few hundred yards from the departure airport. On August 8, 2003, the airplane was located in the water a few miles from the departure airport. Examination revealed no evidence of airframe, engine, or component malfunction. A review of radar and satellite data revealed a large area of thunderstorms along the intended route of flight, with cumulus clouds embedded in an overcast layer, a band of towering cumulus to developing cumulonimbus clouds, and an area of radar echoes across the intended route of flight with reflectivities at video integrator and processor (VIP) Level 4 to 5, "very strong" to "intense" intensity.
Probable cause
The pilot continued VFR flight into adverse weather conditions including instrument meteorological conditions and turbulence in thunderstorms, which resulted in a loss of control in flight and subsequent collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL03FA125
- Event ID
- 20030623X00932
- Case number
- ATL03FA125
- 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: 20a9b0c6de05d43168ced7a8fb79001b2f472c79ac9eb2701cd2395ee1355903; retrieved 2026-09-20T19:09:54.131Z.