WPR15FA152 · Piper PA 28-140
Piper PA 28-140 · Accident: loss of control in flight en route
From Hobby Field (77S) to Pearson Field (VUO)
Event
- NTSB case
- WPR15FA152
- 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
- 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
- Visual Meteorological Cond
Piper PA 28-140
- 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
- N1729J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hobby Field (77S), Cresswell, ORTo Pearson Field (VUO), Vancouver, WA
- Aircraft age
- About 47 years (built 1968)
- 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
- 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
- Destroyed
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
Radar data indicated that, after takeoff, the uncertificated, noninstrument-experienced pilot flew the airplane north toward the destination, which required the airplane to cross mountainous terrain, and climbed to an altitude of at least 6,300 ft mean sea level (msl). About 11 minutes after departure, the radar data showed an abrupt left turn to a southwest direction, which was followed by a loss of radar contact 19 seconds later. The abrupt left turn is indicative of a steep bank angle. The radar data also showed that the airplane descended rapidly over a ground distance of about 0.5 mile from at least 6,300 ft msl to 3,100 ft msl where it collided with terrain near the peak of a mountain. The steep left turn and the rapid descent are consistent with a loss of control. Further, the airplane's wreckage distribution was consistent with a high velocity collision with trees and terrain.
Weather observations indicated that instrument meteorological conditions (IMC) were likely present in the vicinity of the accident site around the time of the accident. The closest official weather observing station, located 11 miles from the accident site, reported a broken ceiling at 4,300 ft msl and an overcast cloud base at 5,000 ft msl. An unofficial weather observing station at an elevation of 2,100 ft, located 7 miles from the accident site, reported relative humidity greater than 90 percent, indicative of cloud or fog formation.
It is likely that the pilot encountered IMC conditions and lost visual reference to the ground or horizon. Given the pilot's lack of certification and instrument flight experience, the loss of visual reference likely resulted in spatial disorientation, leading to a loss of control of the airplane.
The pilot's toxicology testing detected amphetamine and donepezil in the muscle and liver; quetiapine in the liver; tetrahydrocannabinol (THC) in the liver, lung, and brain; and THC's inactive metabolite tetrahydrocannabinol carboxylic acid in the liver, lung, and brain. The pilot was likely being treated with donepezil for memory loss following a brain injury, but the condition being treated with quetiapine was not identified. While both a traumatic brain injury with memory loss and psychiatric disorder(s) could significantly degrade the pilot's cognitive skills and decision-making ability to safely operate the airplane, the investigation was unable to determine the extent of either condition, what role they played in the accident, or if the pilot had side effects from the medications. The toxicology results demonstrate that the pilot had used marijuana and amphetamine at some point before the accident, but the timing of use or blood levels around the time of the accident could not be obtained. Therefore, the investigation was unable to determine if the pilot's use of marijuana (source of THC) and amphetamine impaired his ability to safely operate the aircraft or if either drug contributed to the accident.
Probable cause
The noncertificated pilot's continued visual flight into instrument meteorological conditions, which resulted in spatial disorientation leading to the pilot's loss of control of the airplane and subsequent collision with mountainous terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15FA152
- Event ID
- 20150424X81527
- Case number
- WPR15FA152
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2015-04-22.
- API snapshot SHA-256: 9f59386a92e43cd35711ff2be77f95baa8d2fce55771dfbcd46ff95fcd9057bf; retrieved 2026-09-14T17:36:52.857Z.