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

Cessna R172K accident near Aurora, Oregon, May 21, 1999

On May 21, 1999 at about 4:00 pm local time, a Cessna R172K, registered N1909V, was substantially damaged in an accident near Aurora, Oregon (Aurora State airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

Aircraft control was not maintained. The pilot's misjudged flare and inadequate remedial action, along with the flight instructors delayed remedial action were factors.

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

What the record shows

Date
May 21, 1999 · about 4:00 pm local time
Place
Aurora, Oregon · Aurora State · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna R172K · all R172Ks on the register
Registration
N1909V · no longer on the register · serial R1722219
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The pilot reported that the approach for the full flap landing was normal. The pilot stated that the flare was a little high, about ten feet above the runway, and the stall horn sounded about five feet above the runway. The pilot stated that as the main landing gear touched down 'firmly' with the airplane in a nose high attitude, he added full power. The airplane veered to the left side of the runway, and the flight instructor took over the controls to continue the go-around, not realizing that when the wing dipped down during the veering maneuver, it contacted the runway surface. During the downwind leg, the pilot noticed that the wing tip fairing was vibrating. The flight instructor continued in the pattern and landed without further incident.

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

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 100 hours in all; 41 in this make and model; 45 in the last 90 days; 33 in the last 30 days; 72 as pilot in command
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 1,070 hours
  • Last inspection: annual inspection, May 4, 1999; 50 hours since
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-360-K (piston); 0 hours total

The flight

  • Departed from: UAO at 2:45 pm
  • Flight plan: none
  • Runway 0, 5,000 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 090° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 52°F (11°C), dew point 45°F (7°C)
  • Altimeter: 30.00 inHg
  • Observation at 3:53 pm from UAO

Injuries

FatalSeriousMinorNone
Crew2

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Other NTSB records under N1909V the same tail number, which may have belonged to a different aircraft at the time

2003-01-14SEA03FA026 · accident near Gig Harbor, WA · substantial damage · no injuries

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.