FTW98FA411 · Cessna 170B
Cessna 170B · Accident: in flight collision with object while maneuvering
From Arledge Field (F56) to No airport
Event
- NTSB case
- FTW98FA411
- 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
- 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
Cessna 170B
- Aircraft type
- Cessna 170
- 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
- N3469D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Arledge Field (F56), Stamford, TXTo No airport
- 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
- Maneuvering
- 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, static
- 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 › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane impacted a power line while maneuvering. A witness observed the airplane overflying the pilot's private airstrip from south to north at about the same level as the power lines, which were located approximately 300 yards north of the grass runway. As the airplane neared the wires, its nose pitched up without the pilot adding power. The airplane struck the southern top static wire and subsequently impacted the ground 179 feet north of the power lines. The witness reported that the engine sounded 'great.' According to local residents, the pilot would normally takeoff to the south and land to the north. Examination of the airplane revealed that the left main landing gear tire had a straight-line abrasion across the tire tread extending around the inside edge of the tire. The left lower strut/axle had scrape marks on the leading edge from the brake hose clamp down to the wheel attachment bolts. The right main landing gear tire also had a straight-line abrasion across the tire tread extending around the outside edge of the tire. Continuity was established to all flight controls.
Probable cause
The pilot's failure to maintain obstacle clearance.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98FA411
- Event ID
- 20001211X11048
- Case number
- FTW98FA411
- 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: 652c5f545d658f7be62d103d9464bacf1d7944421716c39845aedd29165faee5; retrieved 2026-09-20T22:23:49.599Z.