FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA01IA113 · Cessna 172S

30 May 2001 · Monroe, OR, United States

Hillsboro Aviation Cessna 172S · Incident: loss of control in flight en route

From Eugene Airport (EUG) to Portland Hillsboro Airport (HIO)

Report a problem

Event

NTSB case
SEA01IA113
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
Incident
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
0 · 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

Cessna 172S

Aircraft type
Cessna 172
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
N571SP
Onboard fatalities
Unknown
Route
From Eugene Airport (EUG), Eugene, ORTo Portland Hillsboro Airport (HIO), 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 · climb to cruise
First occurrenceThe 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
None

Cause areas

  • Reason for occurrence undetermined

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

NTSB narrative

The aircraft was on an instrument training flight at the time of the occurrence. The flight was cleared to an altitude of 6,000 feet on departure. The trainee reported that as the aircraft climbed through 4,500 feet, with the instructor flying the aircraft, "the airplane pitched up, and rolled to the left followed by a pitch down, and a roll back to wings level, then a pitch back up and to the left." The instructor stated that as the aircraft climbed through that altitude, "the aircraft suddenly nosedived for about 3-4 seconds and pitched up into a climb." Both pilots reported that they susbsequently felt the pitch control stuck in a pitch-up position, and that they had to hold forward pressure to hold the nose down (the instructor stated both pilots had to apply full forward pressure to prevent a stall.) The instructor further reported that the aircraft would not roll; the trainee reported that the controls were stuck in roll to the left. The pilots reported that the instructor subsequently attempted to trim the aircraft nose-down, without success. The pilots declared an emergency with ATC and subsequently elected to land in a field directly in front of the aircraft by utilizing rudder and power for control, which they accomplished successfully. The pilots reported in their initial interview with the FAA inspector that they did not have the autopilot on at the time of the occurrence, and that they made no attempts to disengage the autopilot during the incident. Post-incident examinations of the flight controls, trim, and autopilot operation by the operator, an FAA inspector, and the autopilot manufacturer did not disclose any evidence of malfunctions or abnormal flight control or autopilot operation.

Probable cause

A degradation of aircraft control for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA01IA113
Event ID
20010618X01192
Case number
SEA01IA113
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2001-05-31.
  • API snapshot SHA-256: 677004254a16ef405d9186c73f75530d4025a9223797fd3ba79dd9ec86611547; retrieved 2026-09-22T11:55:17.667Z.