CEN15FA092 · Piper PA 28-181
Piper PA 28-181 · Accident: VFR encounter with IMC en route
From 2F5 · Lamesa, TX to Albuquerque International Sunport (ABQ)
Event
- NTSB case
- CEN15FA092
- 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
- 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
- Instrument Meteorological Cond
Piper PA 28-181
- Aircraft type
- Piper PA-28
- 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
- N2558M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 2F5 · Lamesa, TXTo Albuquerque International Sunport (ABQ), Albuquerque, NM
- Aircraft age
- About 37 years (built 1977)
- 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 · descent
- 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
- VFR encounter with IMC
- 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 › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The operator reported that the noninstrument-rated pilot departed on a cross-country flight in the airplane after topping off the fuel tanks. Radar data and fuel records revealed that, about 3 hours later, the airplane stopped at an airport and was fueled. The airplane subsequently departed and flew toward the pilot's destination airport for about 30 miles, but it then returned to the same airport to be fueled again. The airplane subsequently departed again and flew toward the destination airport. Radar data showed that the airplane then climbed to 10,500 ft mean sea level but that it subsequently began to descend; the last radar return showed the airplane at 7,100 ft msl. The airplane was reported missing when it did not arrive at the destination. A subsequent search was conducted, and the airplane's emergency locator transmitter signal was used to find the wreckage. The airplane had impacted rising terrain in a level flight attitude. An examination of the wreckage did not reveal any preimpact anomalies that would have precluded normal operation. Witness marks and bending found on the propeller were consistent with the engine producing power at the time of impact.
Multiple weather sources showed that instrument meteorological conditions existed along the route of flight and that these were reported before the accident airplane departed. Additionally, the freezing level was at the surface, and moderate turbulence was expected from the surface through 24,000 ft. Pilots flying in the area around the time of the accident confirmed the presence of turbulence and/or mountain-wave conditions, and they indicated the presence of icing in the clouds with cloud tops near 9,000 ft. Further, no moonlight was present during the flight. No record was found indicating that the pilot received a formal preflight weather briefing; if the pilot had received a formal weather briefing, he would have been made aware of the weather conditions along the route of flight. Although the investigation could not determine what weather information the pilot might have reviewed before departure, his decision to conduct the flight in poor weather conditions was indicative of poor decision-making. The evidence is consistent with the noninstrument-rated pilot flying at night in instrument conditions while likely attempting to fly under the clouds when the airplane hit rising terrain.
Toxicological testing of the pilot detected tetrahydrocannabinol (THC). However, the investigation could not determine if the pilot was impaired from the THC before or during the accident flight.
Probable cause
The noninstrument-rated pilot’s continued flight into night instrument meteorological conditions, which resulted in his failure to maintain clearance from terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15FA092
- Event ID
- 20150101X13628
- Case number
- CEN15FA092
- 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. 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: acd168bf024b88a4f83603fc84a439d1588cf45358a2b177eb10e77f5d5c8afe; retrieved 2026-09-14T17:30:28.345Z.