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

Cessna 152 accident near Hillsboro, Oregon, August 12, 2016

On August 12, 2016 at about 9:30 pm local time, a 1977 Cessna 152, registered N48440, was substantially damaged in an accident during landing (flare/touchdown) near Hillsboro, Oregon (Portland-Hillsboro airport). It was an instructional 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 student pilot's improper pitch control during the landing flare, which resulted in a porpoise and substantial damage to the engine mount.

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

What the record shows

Date
August 12, 2016 · about 9:30 pm local time
Place
Hillsboro, Oregon · Portland-Hillsboro · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 152, built 1977 · all 152s on the register
Registration
N48440 · registry record · serial 15280910
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The student pilot reported that during a short field landing, she flared a "little bit too high". She pushed the yoke forward, and the nose wheel impacted the ground first, subsequently the airplane porpoised and impacted a taxiway edge identifier light on the edge of the runway. The student pilot further reported that after she applied "heavy" brakes she taxied the airplane to the ramp area without further incident. The airplane sustained substantial damage to the engine mount. According to the student pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. The Federal Aviation Administration has published the Airplane Flying Handbook FAA-H-8083-3A (2004). This handbook discusses porpoising and states in part: In a bounced landing that is improperly recovered, the airplane comes in nose first setting off a series of motions that imitate the jumps and dives of a porpoise—hence the name. The problem is improper airplane attitude at touchdown, sometimes caused by inattention, not knowing where the ground is, mistrimming or forcing the airplane onto the runway. Ground effect decreases elevator control effectiveness and increases the effort required to raise the nose. Not enough elevator or stabilator trim can result in a nose low contact with the runway and a porpoise develops. Porpoising can also be caused by improper airspeed control. Usually, if an approach is too fast, the airplane floats and the pilot tries to force it on the runway when the airplane still wants to fly. A gust of wind, a bump in the runway, or even a slight tug on the control wheel will send the air plane aloft again. The corrective action for a porpoise is the same as for a bounce and similarly depends on its severity. When it is very slight and there is no extreme change in the airplane's pitch attitude, a follow-up landing may be executed by applying sufficient power to cushion the subsequent touchdown, and smoothly adjusting the pitch to the proper touchdown attitude.

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. Abnormal runway contact during landing (flare/touchdown) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student/instructed pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Pitch control › Not attained/maintained
  • Environmental issues › Physical environment › Object/animal/substance › Sign/marker › Contributed to outcome

Dual student

  • Certificate: student
  • Flight time: 105.5 hours in all; 105.5 in this make and model; 60 in the last 90 days; 21 in the last 30 days; 6 as pilot in command
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 21,986.8 hours
  • Last inspection: annual inspection, July 29, 2016
  • Maximum gross weight: 1,670 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235-L2C (piston); 5,695 hours total
  • Operator: Hillsboro Aero Academy

The flight

  • Departed from: HIO Hillsboro OR at 8:30 pm
  • Destination: HIO Hillsboro OR
  • Runway 31L, 6,600 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 160° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 93°F (34°C), dew point 54°F (12°C)
  • Altimeter: 29.97 inHg
  • Observation at 9:53 pm from KHIO

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 October 27, 2016. 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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.