The U.S. aircraft register, updated daily
Accidents · NTSB WPR12CA368 · Final report

Piper PA-28-140 accident near Mcminnville, Oregon, August 21, 2012

On August 21, 2012 at about 9:15 pm local time, a Piper PA-28-140, registered N8154N, was substantially damaged in an accident during takeoff near Mcminnville, Oregon (Mcminnville Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s loss of directional control during the takeoff roll, which resulted in a runway excursion.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 21, 2012 · about 9:15 pm local time · cases in 2012
Place
Mcminnville, Oregon · Mcminnville Municipal Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-140 · all PA-28-140s on the register
Registration
N8154N · registry record · serial 28-25348
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot reported that during the takeoff roll, he attempted to close a window vent and the airplane veered off the left side of the runway. He aborted the takeoff and taxied back for takeoff; he examined the airplane before takeoff and did not see any damage. After landing, he secured the airplane in the club hangar. During a flying club meeting 4 days later, the pilot observed damage to the right wing; subsequent examination revealed substantial damage to the wing spar. The pilot reported that there were no mechanical malfunctions or anomalies with the airplane before the runway excursion.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control on ground during takeoff defining event
  2. Runway excursion during takeoff
  3. Collision with terrain or object (not controlled flight into terrain) during takeoff (rejected takeoff)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 145 hours in all; 47 in this make and model; 4 in the last 90 days; 3 in the last 30 days; 94 as pilot in command
  • Last flight review: February 5, 2012
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,952 hours
  • Last inspection: annual inspection, March 10, 2012; 12 hours since
  • Maximum gross weight: 2,150 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 0 hours total
  • Operator: Pacific Flyers INC

The flight

  • Departed from: UAO Aurora OR at 8:55 pm
  • Destination: MMV Mcminnville OR
  • Flight plan: none
  • Runway 22, 5,420 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 330° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 82°F (28°C), dew point 54°F (12°C)
  • Altimeter: 30.12 inHg
  • Observation at 8:30 pm from SLE, 18 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

2 documents, released by the NTSB on September 25, 2012. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR12CA368.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.