ERA12CA496 · Cessna 172S
Aviation Adventures Cessna 172S · Accident: abnormal runway contact during landing
From Warrenton Fauquier Airport (HWY) to Culpeper Regional Airport (CJR)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA12CA496
- 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
Cessna 172S
- Aircraft type
- Cessna 172
- 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
- N6276Z
- Operator
- Aviation Adventures
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Warrenton Fauquier Airport (HWY), Warrenton, VATo Culpeper Regional Airport (CJR), Culpepper, 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
- 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
- Abnormal runway contact
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the airplane touched down about halfway down the runway. The pilot’s intent was to perform a touch-and-go practice landing and takeoff. He applied takeoff power, retracted the flaps, and the airplane veered to the left. The pilot reported that he was unable to maintain directional control with aileron and rudder control inputs and elected to abort the takeoff. After he reduced power to idle, the airplane departed the left side of the runway and continued approximately 100 yards before impacting a row of trees. A witness report corroborates the pilot’s landing description. A postaccident examination revealed substantial damage to the fuselage and left wing. In a phone interview the accident the pilot reported that there were no mechanical malfunctions or anomalies that precluded normal operation of the airplane.
Probable cause
The pilot’s failure to maintain directional control during an attempted takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12CA496
- Event ID
- 20120806X51434
- Case number
- ERA12CA496
- 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: 17a61a44ef270ba4a1c428fa0cac4ed3d6ce03001d135bbdfbea31981db1eee5; retrieved 2026-09-15T19:15:14.716Z.