ERA10CA497 · Consolidated Aeronautics INC. LAKE LA-4-200
Consolidated Aeronautics INC. LAKE LA-4-200 · Accident: collision with terrain/object (non-CFIT) during takeoff
From New Castle International Airport (VA85) to Moneta, VA
Event
- NTSB case
- ERA10CA497
- 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
Consolidated Aeronautics INC. LAKE LA-4-200
- Aircraft type
- Consolidated Aeronautics LAKE LA-4-200
- 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
- N8001J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From New Castle International Airport (VA85), New Castle, VATo Moneta, 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
- Takeoff · rejected takeoff
- 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
- Collision with terrain/object (non-CFIT)
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the airplane was accelerating normally during the takeoff roll into a 6- to 8-knot headwind. About halfway down the turf runway, the airplane became airborne and then settled back onto the runway. The pilot decided to abort the takeoff and reduced power while applying the brakes. He realized that the airplane would not be able to stop prior to impacting a berm located at the end of the runway and added full power. The airplane cleared the berm, crossed a dirt road, and impacted a tree and several boulders before coming to rest in a pond. The pilot stated that it had rained earlier in the day and that the runway might have still been damp. The pilot reported no mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation.
Probable cause
The pilot's delayed decision to abort the takeoff, which resulted in a collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA497
- Event ID
- 20100923X71802
- Case number
- ERA10CA497
- 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: f5d06ee1bd386337771bf245eae8c3c91a49f02001dd3d312fad55cfadc32dfb; retrieved 2026-09-15T15:19:43.308Z.