Cessna 172H accident near Weyers Cave, Virginia, October 20, 2012
On October 20, 2012 at about 4:30 pm local time, a Cessna 172H, registered N1431F, was substantially damaged in an accident during landing (flare/touchdown) near Weyers Cave, Virginia (Shenandoah Valley 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 landing flare, which resulted in a hard landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 20, 2012 · about 4:30 pm local time
- Place
- Weyers Cave, Virginia · Shenandoah Valley · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172H · all 172Hs on the register
- Registration
- N1431F · registry record · serial 17254926
- 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 after completing her first solo cross-country flight she landed without incident. She then elected to practice takeoffs and landings in the airport traffic pattern. During the subsequent landing, the airplane touched down hard and bounced before coming to rest on the runway. The airplane sustained substantial damage to the firewall and skin deformation just forward of the pilot’s side door. The student pilot reported that she did not experience any mechanical malfunctions or failures that would have precluded normal operation.
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
- Hard landing during landing (flare/touchdown) defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Student pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
Dual student
- Certificate: student
- Flight time: 68 hours in all; 58 in this make and model; 20 in the last 90 days; 13 in the last 30 days; 9 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,979 hours
- Last inspection: 100-hour inspection, August 24, 2012; 76 hours since
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor O-300 SER (piston); 0 hours total
- Operator: Valley Aircraft Leasing
The flight
- Departed from: SHD Weyers Cave VA at 4:25 pm
- Destination: SHD Weyers Cave VA
- Flight plan: none
- Runway 23, 6,001 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 250° at 7 knots
- Visibility: 10 statute miles
- Sky: scat at 5,500 ft
- Temperature: 61°F (16°C), dew point 36°F (2°C)
- Altimeter: 29.82 inHg
- Observation at 4:35 pm from SHD
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
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.