ERA10CA355 · Piper J3C-65
Piper J3C-65 · Accident: hard landing
From Flying Circus Aerodrome (3VA3) to Flying Circus Aerodrome (3VA3)
Event
- NTSB case
- ERA10CA355
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper J3C-65
- Aircraft type
- Piper J3
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N33554
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Flying Circus Aerodrome (3VA3), Warrenton, VATo Flying Circus Aerodrome (3VA3), Warrenton, VA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The pilot's improper flare during a precautionary landing, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA355
- Event ID
- 20100712X54906
- Case number
- ERA10CA355
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: b838bf00ab019bbe01b6faf4cc87a6aaefc642051f59139506790ba6a5d1b478; retrieved 2026-09-15T14:40:48.969Z.