FTW89DRD03 · Schweizer G-164A
Schweizer G-164A · Accident: in flight collision with object while maneuvering
From MAXIE, LA (no airport) to an unrecorded destination
Event
- NTSB case
- FTW89DRD03
- 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
Schweizer G-164A
- Aircraft type
- Schweizer G-164
- 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
- N48467
- Operator
- Aerohead Cropdusters
- Onboard fatalities
- Unknown
- Route
- From MAXIE, LA (no airport)To 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
- Tree(s)
- 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 · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT WAS BEING USED ON A FLT TO SPREAD FERTILIZER. SUBSEQUENTLY, IT CRASHED IN AN AREA OF DENSE TREES NEAR THE EDGE OF A FIELD. THE 1ST IMPACT WITH TREES WAS AT AN ALT OF ABOUT 55' AGL, WHICH SHEARED OFF A 9' BRANCH FROM A TREE. THE ACFT CONTD 43' & HIT TREES AGAIN, ABOUT 31' AGL, & SHEARED OFF TWO 12' BRANCHES. IT THEN CRASHED TO THE GROUND & CAME TO REST ABOUT 85' FROM THE INITIAL IMPACT POINT. THERE WAS EVIDENCE THE ACFT WAS TRAVELING AT A MODERATE SPEED WHEN IT 1ST HIT THE TREES. ACCORDING TO WITNESSES, THE ENG WAS OPERATING NORMALLY BEFORE IMPACT. NO MECHANICAL PROBLEM OF THE ACFT OR ENG WAS FOUND, EXCEPT THAT CONTINUITY OF THE ENG SUPERCHARGER DRIVE WAS DISRUPTED; THE INVESTIGATION DID NOT REVEAL WHETHER THE SUPERCHARGER CONTINUITY HAD FAILED BEFORE OR AFTER IMPACT. THE ACFT'S HOPPER WAS FULLY LOADED WITH FERTILIZER WHEN THE ACFT CRASHED.
Probable cause
FAILURE OF THE PILOT TO MAINTAIN CLEARANCE FROM THE TREES. A FACTOR RELATED TO THE ACCIDENT WAS: THE PRESENCE OF TREES NEAR THE FIELD WHERE FERTILIZER WAS TO BE DISPENSED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW89DRD03
- Event ID
- 20001213X28307
- Case number
- FTW89DRD03
- 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: dc99bf3320e949d3ce5405db986403b7fff06326f87c5d6cce9e6bec4f87743d; retrieved 2026-09-21T03:18:50.587Z.