FTW98FA028 · Weatherly 620B
Weatherly 620B · Accident: in flight collision with object while maneuvering
From Dan E Richards Municipal Airport (3F6) to an unrecorded destination
Event
- NTSB case
- FTW98FA028
- 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
- 1 · 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
Weatherly 620B
- Aircraft type
- Weatherly 620
- 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
- N46278
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dan E Richards Municipal Airport (3F6), Paducah, TXTo not recorded
- 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 137: Agricultural
- 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
- Maneuvering · aerial application
- 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 collision with object
- 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
- Wire, transmission
- 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 › Clearance, not maintained
Approximate · Estimated position: the centre of Cee Vee, TX, the place the record names. Not the accident site.
NTSB narrative
The agricultural airplane collided with power lines and terrain during a local aerial application flight. Witnesses reported that the airplane was flying level, approximately the height of the power lines, when it passed behind an obstruction, out of their view. They reported seeing black smoke 5-10 seconds later. The witnesses went to the accident site and observed power lines severed and stretched to the ground. Examination of the airplane by the investigator-in-charge revealed that the airplane struck the power lines with the main landing gear mounted wire cutter. Further examination of the airframe, engine and logbooks revealed no evidence of pre-impact defects.
Probable cause
The pilot's failure to maintain clearance with the power lines during an aerial application flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98FA028
- Event ID
- 20001208X08996
- Case number
- FTW98FA028
- 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. 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: e5821a94f41f38c37e82c452336c0821dcb6f2515fa0bf3187e4afb359ab0248; retrieved 2026-09-20T22:47:05.544Z.