FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW04FA052 · Bellanca 17-30A

1 Jan 2004 · Dallas, TX, United States

Bellanca 17-30A · Accident: in flight encounter with weather during initial climb

From Addison Airport (ADS) to Rick Husband Amarillo International Airport (AMA)

Report a problem

Event

NTSB case
FTW04FA052
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
Instrument 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
N4104B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Addison Airport (ADS), Addison, TXTo Rick Husband Amarillo International Airport (AMA), Amarillo, TX
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
Initial climb
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
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

  • Aircraft control › Not maintained
  • Flight/nav instruments › Inoperative
  • Pilot in command › Flight/navigation instrument(s), unavailable

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

NTSB narrative

After takeoff and climb out in solid instrument meteorological conditions, the single-engine airplane experienced failures of flight/navigation instruments. The 1,050-hour pilot was attempting to maneuver the airplane using partial panel techniques. Radar data showed that the pilot appeared to be experiencing spatial disorientation. ATC controllers were alerted due to the fact that the airplane was making "left' turns" instead of right turns as advised. After being observed by several witnesses flying just below the lowest cloud layer (approximately 125 feet agl) the airplane impacted several homes in a residential neighborhood. Both homes and the airplane were destroyed by post-impact fire. One person who was located 1/2 miles from the accident site, witnessed the airplane flying overhead in an straight and level attitude approximately 125 feet above ground level (agl), slightly below a layer of clouds. Another person who was a private pilot and located about 1/2 miles from the accident site, stated that he heard an airplane engine that sounded "normal." After about 15 seconds, it sounded as if the airplane was maneuvering, because of the pitch change in the engine. According to this witness, the engine sounded like it was "making good power." The airplane was rapidly getting closer and sounded very low and fast. The witness stated, "at no time did I see the aircraft due to the weather conditions." The nearest automated surface observing station reported wind from 130 degrees at 6 knots, visibility 7/8 in mist, overcast at 100 feet. The temperature and dew point were reported as 17 degrees Celsius, and an altimeter setting of 30.20 inches of Mercury. Flight control continuity could not be verified due to impact damage. A fire extinguisher from the airplane was found with the handle lock pin missing and bottle fully discharged. The instrument panel was completely destroyed by post-impact fire. The vacuum pump was separated and the drive coupling was bent approximately 30-degrees. The unit was disassembled and the rotor vanes were observed to be in place and not damaged. The core element was cracked. The intake and exhaust pipes were separated; the exhaust pipes were separated aft of the mufflers. Examination revealed that the left side ball flange clamp had four washers on the bolt. The clamp was tight on the ball flange, and the tailpipe would not move on the ball flange. The exhaust pipes were separated on both sides of the left ball flange. Due to the extensive post-impact fire damage, it could not be concluded as to the cause of the pilot's reported loss of instruments during the flight. However, it was noted that the wire bundle that connects the instrument panel through the firewall were in close proximity to the muffler's exhaust flange, on the engine side of the firewall.

Probable cause

The failure of flight/navigation instruments while in instrument meteorological conditions (in-cloud flight and low ceilings) resulting in spatial disorientation. A contributing factors was the prevaling instrument meteorological conditions (low ceiling and in-cloud flight)

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW04FA052
Event ID
20040106X00018
Case number
FTW04FA052
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: f8a90857e23ca6cb13c791d9ce975971ec34b8634d768491ec854cd0e2e20bcc; retrieved 2026-09-20T18:39:53.264Z.