GAA20CA033 · Weatherly 620 B
Weatherly 620 B · Accident: low altitude operation/event while maneuvering
From Fabens Airport (E35) to Fabens Airport (E35)
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- GAA20CA033
- 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
Weatherly 620 B
- 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
- N9033T
- Operator
- Roger J. Zeledon Dba · private individual
- Onboard fatalities
- Unknown
- Route
- From Fabens Airport (E35), Fabens, TXTo Fabens Airport (E35), Fabens, TX
- Aircraft age
- About 23 years (built 1996)
- 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 · low-altitude flying
- 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
- Low altitude operation/event
- 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
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial Possible conflict
Cause areas
- Environmental issues › Physical environment
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during an agricultural application flight, he made six passes underneath power wires to complete the applications. On the seventh pass underneath the power wires, the wire deflector cable and the vertical stabilizer struck the wires. The pilot asserted that the vertical stabilizer jammed the rudder to the left, and the airplane entered a skidding left turn and then impacted terrain. The airplane was consumed by fire.
Probable cause
The pilot's failure to maintain clearance from power wires while maneuvering at a low altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA20CA033
- Event ID
- 20191018X04535
- Case number
- GAA20CA033
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 4faffbb2497aa0912aeddc2f0b44f2504e63e5650cbde2555ed9d6330ce22a86; retrieved 2026-09-16T10:25:00.719Z.