FTW00LA086 · Piper PA-18
Piper PA-18 · Accident: in flight collision with object during landing
From 12R · Brookshire, TX to TX (no airport)
Event
- NTSB case
- FTW00LA086
- 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
- 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
Piper PA-18
- Aircraft type
- Piper PA-18
- 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
- N8967C
- Operator
- Leonard F. Firth · private individual
- Onboard fatalities
- Unknown
- Route
- From 12R · Brookshire, TXTo TX (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
- Landing · aborted
- 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
- 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 › Altitude/clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Upon arrival at the destination, the pilot flew the airplane over the grass airstrip, and noted that the wind was 90 degrees to the runway at a speed of 10 to 12 knots. The pilot reported that when the airplane descended below the tree height, the airplane 'floated more than expected and when I touched down, the surface of the strip had gopher mounds making aircraft braking ineffective so I added power to abort the landing. The aircraft seemed to be in a downdraft and was hesitant to fly, but I was committed at this point and continued.' The airplane struck a barbed wire fence at the end of the runway and the propeller became entangled with the fence. The aircraft continued to climb to the height of the treetops and 'lost power'. Subsequently, the main landing gear struck the trees causing the airplane to nose over and come to rest in a brush pile.
Probable cause
The pilot's failure to maintain clearance with a fence during the aborted landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA086
- Event ID
- 20001212X20491
- Case number
- FTW00LA086
- 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: 9943222f318d197c4429aa73732e95ce108110d9d40f818cf3b913b000b60296; retrieved 2026-09-21T20:18:05.892Z.