WPR26FA257 · Luscombe 8A
Luscombe 8A · Accident: loss of control in flight
From Goode Field (TX43) to an unrecorded destination
Event
- NTSB case
- WPR26FA257
- 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
- Ongoing
- API-reported fatalities
- 1 · 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
- Not recorded
Luscombe 8A
- Aircraft type
- Luscombe 8
- 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
- N1164K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Goode Field (TX43), Canton, TXTo not recorded
- Aircraft age
- About 80 years (built 1946)
- 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
- Unknown
- 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
- Loss of control in flight
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On July 14, 2026, sometime between 1252 and 1356 CDT, a Luscombe 8A, N1164K, was substantially damaged when it crashed in a field near Canton, Texas. The pilot, who was the sole occupant, was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
The flight had originated from the pilot’s private airstrip where the airplane was hangared, which was oriented north to south. A farmer discovered the airplane wreckage about 800 ft northwest of the private airstrip, at about 1356.
There were no eyewitnesses to the accident. The pilot sent a text message to a friend at about 1252, which was his last known communication. Additionally, a nearby resident reported hearing what sounded like an engine “winding up” for a few seconds, followed by less than a second of silence, then a “boom” sound. He stated that he heard the sound within the general timeframe of the accident, but he was unable to identify the specific time.
The accident pilot purchased the airplane in December 2025. His wife told investigators that the pilot flew the airplane frequently and that they felt it did not produce sufficient take-off performance for them to fly together. She said he usually flew it in the morning or evening and had not flown the airplane much in high-temperature conditions. When she returned home from an appointment at around 1400, she observed the windsock located at the north end of the runway, which indicated the wind was from the north. She noted that the wind had been coming from the south earlier in the day. She said that the pilot typically took off to the south because the prevailing winds were generally from that direction, but on the day of the accident she believed he must have taken off to the north.
Figure 1: Overhead map view of accident location
The airplane impacted a field in a steep, nose-down attitude about 800 feet northwest of the northern end of the private airstrip. The longitudinal axis of the fuselage was oriented on a heading of about 349° magnetic and exhibited fore-aft crushing. All major structures and components of the airplane were located within the immediate wreckage area. Pieces of windscreen plexiglass were scattered forward and left of the primary wreckage, within about a 30-ft diameter. Disturbance of the surface soil was limited to the area located immediately under the wreckage.
Figure 2: Photo of airplane wreckage at accident scene
The right wing was displaced aft and the left wing was displaced forward. Compression wrinkling was observed along the top skin of the left wing along with forward bending at the wing root leading edge. The right wing was damaged at the outboard leading edge and the aft spar had separated at the fuselage. Both the left and right ailerons remained attached to their respective wings. The empennage remained intact and attached to the aft fuselage. Both elevators and the rudder also remained attached. The elevator trim tab was connected to the left elevator and articulated freely by hand. The upper fuselage had collapsed into the cabin.
The propeller remained attached to the engine crank flange. One blade was intact and exhibited no chordwise scratches or damage. The second blade was fractured and splintered near the blade root with aft bending.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record WPR26FA257
- Event ID
- 20260714203392
- Case number
- WPR26FA257
- 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. 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: f286f0067436bbb4ccddae6f7076adcc1837a77e72157e662e17c5053c38841b; retrieved 2026-09-15T09:18:33.787Z.