FTW95LA061 · Piper PA-32-260
Piper PA-32-260 · Accident: in flight encounter with weather en route
From Deming Municipal Airport (DMN) to Brownwood Regional Airport (BWD)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- FTW95LA061
- 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-32-260
- Aircraft type
- Piper PA-32
- 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
- N2LK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Deming Municipal Airport (DMN), Deming, NMTo Brownwood Regional Airport (BWD), Brownwood, TX
- 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
- En route · cruise
- 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 encounter with weather
- 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 › Flight into known adverse weather, attempted
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE EN ROUTE FROM DEMING, NM, TO WACO, TX, THE PILOT ENCOUNTERED DETERIORATING WEATHER AND ELECTED TO DIVERT TO BROWNWOOD, TX, HIS ALTERNATE. PRIOR TO HIS DEPARTURE FROM DEMING, NEW MEXICO, HE HAD RECEIVED A COMPLETE WEATHER BRIEFING. THE BRIEFER INFORMED HIM THAT THE WEATHER ALONG HIS PROPOSED ROUTE OF FLIGHT WOULD BE DETERIORATING. THE PILOT WAS UNABLE TO LOCATE THE ALTERNATE AIRPORT DUE TO REDUCED VISIBILITY AND THE LIGHT CONDITIONS, SO HE DECIDED TO LAND IN A COW PASTURE. DURING THE LANDING ROLL, THE AIRPLANE STRUCK A BARBED WIRE FENCE AND NOSED OVER INTO A CREEK.
Probable cause
THE PILOT'S ATTEMPTED FLIGHT INTO KNOWN ADVERSE WEATHER CONDITIONS. FACTORS WERE THE UNSUITABLE TERRAIN, REDUCED VISIBILITY DUE FOG AND LOW CEILINGS, AND THE REDUCED LIGHT CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95LA061
- Event ID
- 20001206X02719
- Case number
- FTW95LA061
- 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: 377e1d1acf621005f68d71b39f22485005ef1b520b95406275f9e047aaf0c51f; retrieved 2026-09-21T22:25:45.345Z.