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

Cessna 172 accident near Orange, Virginia, February 8, 2021

On February 8, 2021 at about 4:15 pm local time, a 2001 Cessna 172, registered N841SP, was substantially damaged in an accident during landing near Orange, Virginia (Orange County 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 recovery from a bounced landing.

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

What the record shows

Date
February 8, 2021 · about 4:15 pm local time
Place
Orange, Virginia · Orange County · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 S, built 2001 · all 172s on the register
Registration
N841SP · registry record · serial 172S8746
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The solo student pilot reported that during landing while on a cross country flight, the airplane was high and fast on final approach. The approach was continued and after the first touchdown the airplane “ballooned back up only to porpoise.” After the multiple touchdowns, the student pilot was able to stop the airplane near the midpoint of the runway, where the airplane was shut down and towed to the ramp. Examination of the airplane revealed that the bounced landing resulted in substantial damage to the fuselage.

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. Hard landing during landing defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Student/instructed pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained

Dual student

  • Certificate: student
  • Flight time: 68 hours in all; 61 in this make and model; 34 in the last 90 days; 19 in the last 30 days; 7 as pilot in command
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,962 hours
  • Last inspection: annual inspection, December 8, 2020
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 4,962 hours total

The flight

  • Departed from: FVX Farmville VA at 3:45 pm
  • Flight plan: VFR
  • Runway 08/2, 3,200 ft by 75 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 32°F (0°C), dew point 12°F (-11°C)
  • Altimeter: 30.45 inHg
  • Observation at 11:15 am from KOMH

Weather report (METAR): METAR KOMH 081615Z AUTO 00000KT 10SM CLR 00/M11 A3045 RMK AO2=

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 July 15, 2021. 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.