WPR19FA077 · Rockwell 112 A
Rockwell 112 A · Accident: loss of control in flight while maneuvering
From Portland Troutdale Airport (TTD) to Grove Field (1W1)
Event
- NTSB case
- WPR19FA077
- 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
Rockwell 112 A
- Aircraft type
- Rockwell 112
- 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
- N1332J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Portland Troutdale Airport (TTD), Portland, ORTo Grove Field (1W1), Camas, WA
- Aircraft age
- About 44 years (built 1975)
- 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
- Maneuvering
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed on a visual flight rules flight toward a nearby mountain with a summit elevation of 11,239 ft. After completing one orbit around the summit at a radial distance of about 3 miles, the pilot flew the airplane to within 1,500 ft horizontally for a second orbit. As the airplane turned around the southern side of the mountain, it began to descend at a rate of about 2,500 ft per minute (fpm) and impacted an almost-vertical face of the mountain about 1,600 ft below the summit. Due to the treacherous and remote nature of the accident site, an on-scene examination could not be performed, and the airplane was not recovered from the site.
The airplane's flight path around the summit revealed significant ground speed variations consistent with the airplane encountering headwinds as it circled. The pilot was likely aware of the wind conditions aloft because he appeared to perform a heading correction during the first orbit, as wind likely pushed the airplane toward the mountain. This should have served as a cue for the pilot to prepare for terrain-induced downdrafts and turbulence and to avoid flying too close to the peak; however, he continued with the second pass. Atmospheric analysis indicated that the airplane was operating in an area of mountain wave conditions at the time of the accident, with modeling indicating the presence of rapid changes in horizontal wind speed. Vertical velocity data showed that the airplane likely encountered updrafts of between 100 and 300 fpm during its first orbit around the mountain, and downdrafts greater than 2,000 fpm during the second, closer orbit, significantly exceeding the airplane's 200-fpm climb performance for that altitude. There was no evidence to suggest that the pilot obtained an official weather briefing before the flight. Had he done so, he would have been made aware of the winds aloft conditions, which indicated the likelihood of terrain-induced turbulence close to the mountain.
Review of the pilot's medical records indicated that he was experiencing ongoing back pain due to an injury. Toxicological testing indicated that he had been using oxycodone, mitragynine, and metoclopramide, all of which are sedating and impairing. The levels of oxycodone in his blood were considered impairing. Use of the stimulant modafinil suggested that the pilot was attempting to counter fatigue. Toxicology also indicated that the pilot had used marijuana; however, it could not be determined if the concentration would have been impairing or decreased his performance. Given that multiple drugs involved were sedating or impairing both individually and combined, the pilot would most likely have experienced diminished decision-making ability, increased reaction times, and degraded motor skills. Thus, it is likely that the use of these drugs contributed to the accident.
Probable cause
The pilot's decision to fly the airplane in close proximity to mountainous terrain in an area of mountain wave activity that exceeded the performance capabilities of the airplane. Contributing to the accident was the pilot's degraded decision making and performance due to his use of multiple sedating and impairing drugs.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19FA077
- Event ID
- 20190130X94929
- Case number
- WPR19FA077
- 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: 30f804112f0e3faeeb1eeebfd49f610fc0ae43c00ea90c353fcd488ff6534c3e; retrieved 2026-09-15T06:53:34.447Z.