CEN23LA024 · Cessna 170A
Cessna 170A · Accident: collision during takeoff/landing
From La Porte Municipal Airport (T41) to an unrecorded destination
Event
- NTSB case
- CEN23LA024
- 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
- Event fatalities
- Unknown
- 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
Cessna 170A
- 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
- N9244A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From La Porte Municipal Airport (T41), La Porte, TXTo not recorded
- Aircraft age
- About 73 years (built 1949)
- 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
- Landing
- 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
- Collision during takeoff/landing
- 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
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that while landing on a friend’s private airstrip the airplane struck wires that crossed the approach end of the runway. He continued the landing on the airstrip and the airplane departed the left side of the runway. The pilot reported that there were no mechanical problems with the airplane and that he just did not see the wires in time to avoid them. The airplane sustained substantial damage to the rudder. The owner of the airstrip had previously purchased orange markers to attach to the wires to aid visibility, but the electric power company had not yet attached the markers to the wires when the accident happened. After the accident the markers were placed on the wires.
Probable cause
The pilot’s failure to maintain clearance from the powerlines while landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA024
- Event ID
- 20221102106239
- Case number
- CEN23LA024
- 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, coordinates, cause areas. 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: 8142cdbfbcce087658db747b4b209f8be6decf63916a6fb25877c69cb4dd7337; retrieved 2026-09-16T16:20:35.281Z.