Piper J3C-65 accident near Warrenton, Virginia, July 5, 2010
On July 5, 2010 at about 3:00 pm local time, a Piper J3C-65, registered N33554, was substantially damaged in an accident during landing (flare/touchdown) near Warrenton, Virginia (Flying Circus Aerodrome airport). It was a personal 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
The pilot's improper flare during a precautionary landing, which resulted in a hard landing.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 5, 2010 · about 3:00 pm local time · cases in 2010
- Place
- Warrenton, Virginia · Flying Circus Aerodrome · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper J3C-65 · all J3C-65s on the register
- Registration
- N33554 · registry record · serial 14028
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot, he was taking off from runway 2, a 2,000-foot-long, 150-foot wide, turf runway. About halfway down the runway, at an altitude of 80 to 100 feet above ground level, the pilot realized that the airplane "was not climbing particularly well." The pilot elected to perform a precautionary landing because the airplane was not going to clear trees located near the end of the runway. He turned the airplane and attempted to land it in a field to the right of the grass strip. The pilot stated that he had a "rough landing," substantially damaging the left wing of the airplane. The pilot further stated the preflight and engine run-up were "good" before the accident flight. He commented that the decreased performance of the airplane was due to the hot and humid day, the airplane was full of fuel, and he had a passenger in the airplane. The pilot noted that his total flight experience was approximately 200 hours; of which, about 125 hours were in the same make and model as the accident airplane. The recorded weather at an airport located 2 miles north of the accident site, included winds from 300 degrees at 7 knots, clear skies, and a temperature of 33 degrees C.
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
- Abnormal runway contact during landing (flare/touchdown)
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 200 hours in all; 125 in this make and model; 100 in the last 90 days; 65 in the last 30 days; 150 as pilot in command
- Last flight review: January 19, 2010
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: rear
- Injury: no injuries
The aircraft
- Last inspection: annual inspection, March 31, 2010
- Maximum gross weight: 1,220 lb
- Seats: 2
- Landing gear: fixed
- Engine: Cont Motor A&C65 SERIES (piston); 0 hours total
The flight
- Departed from: 3VA3 Warrenton VA at 3:00 pm
- Destination: 3VA3 Warrenton VA
- Flight plan: none
- Runway 02, 2,000 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 300° at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 91°F (33°C), dew point 61°F (16°C)
- Altimeter: 30.05 inHg
- Observation at 3:00 pm from HWY, 2 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on September 19, 2010. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Federal Aviation Administration Inspector Statement | PDF, 1 page | View Download |
| 3 | Weather Report | PDF, 1 page | View Download |
| 4 | Photo 1 - Damage to Left Wing (Courtesy of FAA) | PDF, 1 page | View Download |
| 5 | Photo 2 - Structural Damage (Courtesy of FAA) | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N33554 on the register today · the tail number may have moved to another aircraft since
- Piper J-3 Cub 3,804 registered today · the model family and its accident history
- Piper 44,854 aircraft on the register
- Engine: Cont Motor A&C65 SERIES · as the NTSB recorded it
- Flying Circus Aerodrome · nearest airport
- Accidents and incidents in Virginia 1,361 since 1982 · 227 in the last ten years
- Virginia 5,982 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA10CA355.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.