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

Cessna 172G accident near Steubenville, Ohio, October 14, 2000

On October 14, 2000 at about 8:12 pm local time, a Cessna 172G, registered N4352L, was substantially damaged in an accident near Steubenville, Ohio (Jefferson CO. Airpark airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured and 3 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain directional control while landing with a crosswind. Factors in the accident were the pilot's lack of familiarity in the make and model airplane, and the crosswind conditions.

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

What the record shows

Date
October 14, 2000 · about 8:12 pm local time
Place
Steubenville, Ohio · Jefferson CO. Airpark · map
Type
Accident
Injuries
1 person was seriously injured and 3 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cessna 172G · all 172Gs on the register
Registration
N4352L · no longer on the register · serial 17254425
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

While landing on runway 32, as the airplane entered ground effect, the left wing suddenly lifted skyward, and airplane touched down hard on the right main landing gear. The airplane was then 'pushed' off the runway by the crosswind, at a speed of 65 knots, and the propeller impacted a runway light. The pilot applied full power, with 40 degrees of flaps, and the airplane began to climb. The pilot raised the flaps to 30 degrees and the right wing impacted a tree. The right wing struck a second tree, and the airplane descended to the ground. Review of the pilot's logbook revealed that he had accumulated about 78 hours of total flight experience, of which 3.5 hours were in make and model. The winds recorded at a nearby airport about the time of the accident, were from 210 degrees at 7 knots.

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: 78 hours in all; 4 in this make and model; 28 as pilot in command
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 5,383 hours
  • Last inspection: annual inspection, October 10, 2000
  • Maximum gross weight: 2,300 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental O-300D (piston); 0 hours total

The flight

  • Departed from: 2G2 at 7:00 pm
  • Flight plan: none
  • Runway 32, 3,320 ft by 60 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 210° at 7 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 9,500 ft; not recorded
  • Temperature: 158°F (70°C), dew point 129°F (54°C)
  • Altimeter: 30.00 inHg
  • Observation at 7:53 pm from HLG, 12 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers3

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.

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.