FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12FA020 · Piper PA-44-180

25 Oct 2011 · St. Paul, OR, United States

Hillsboro Aviation Piper PA-44-180 and Beech V35 · Accident: midair collision en route

Report a problem

Event

NTSB case
WPR12FA020
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

Aircraft 1 · Piper PA-44-180

Aircraft type
Piper PA-44
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
N3062H
Onboard fatalities
Unknown
Route
From McMinnville Municipal Airport (MMV), Mc Minnville, ORTo Aurora State Airport (UAO), Aurora, OR
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
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
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · Beech V35

Aircraft type
Beechcraft 35
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
N5938S
Onboard fatalities
Unknown
Route
From Hillsboro, ORTo Hillsboro, OR
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
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
Midair collision
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 › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

A Beech V35 and Piper PA-44-180 collided in flight in a common practice area for airwork. The flight instructor in the Piper reported that at an altitude of about 7,500 feet mean sea level (msl), he told the pilot receiving instruction to conduct a simulated emergency descent. The instructor stated that the pilot receiving instruction executed the simulated emergency descent and recovered to cruise flight at an altitude of about 4,500 feet msl before they continued toward a local airport. As the flight continued, the instructor observed a single-engine airplane that appeared to be on a converging course, and he transmitted a position report on the intended destination airport's common traffic advisory frequency. The instructor stated that after making a slight heading change and descent, he re-established visual contact with a single-engine airplane, which was then behind and above the Piper’s position. He then scanned the area ahead of the Piper’s position from left to right. The instructor said he then felt a jolt along with a violent shudder in the airplane followed by an uncommanded left roll and yaw. The instructor took control of the airplane and made a forced landing to a nearby open field.

Review of recorded radar data revealed that the Piper was on a northwesterly heading at 7,700 feet msl when it initiated a right descending turn. Meanwhile, the Beech was traveling on a continuous northeasterly heading at an altitude of about 2,400 feet msl. The last recorded radar target for each airplane before the collision showed that the airplanes were on converging paths; the Piper was at 2,800 feet msl on a northeasterly heading and maneuvering west of the Beech, which was at an altitude of about 2,400 feet msl on a north-northeasterly heading. During examination of the recovered wreckage, transfer marks were identified consistent with the radar-derived collision angle. Both airplanes were operating in visual conditions when they collided.

Based on relative positions of the airplanes, and given the other airplane traffic in the area, it seems likely that the single-engine airplane the Piper instructor observed before the collision was not the Beech with which the collision occurred. It could not be determined if either pilot could see the other just before the collision; however, based on the airplanes’ relative positions and flight attitudes, it seems unlikely. The Piper was maneuvering in a left bank at the time and it is likely that the Piper’s wing and engine blocked the Beech from the Piper pilot's field of vision. Additionally, the Beech pilot’s view of the Piper, which was above and to the left of his flight path, would likely have been blocked by the airplane’s door post and cabin roof structure.

Probable cause

The pilot was unable to see the other aircraft to avoid a collision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12FA020
Event ID
20111025X10819
Case number
WPR12FA020
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: a34cd6b4ad60ccb34888a10332b742bc5fb39381a6b2a56f72622427dac22e68; retrieved 2026-09-13T18:06:47.308Z.