FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11CA052 · Costruzioni Aeronautiche Tecna P2004 BRAVO

29 Oct 2010 · Stockport, OH, United States

Costruzioni Aeronautiche Tecna P2004 BRAVO · Accident: abnormal runway contact during landing

From Fairfield County Airport (LHQ) to 80A7 · Stockport, OH

Report a problem

Event

NTSB case
CEN11CA052
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

Costruzioni Aeronautiche Tecna P2004 BRAVO

Aircraft type
Tecnam P2004
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
N619CS
Operator
Joseph F. Conte Jr · private individual
Onboard fatalities
Unknown
Route
From Fairfield County Airport (LHQ), Lancaster, OHTo 80A7 · Stockport, OH
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
Abnormal runway contact
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 power plant

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that he maintained a higher-than-normal approach speed due to the gusty wind conditions. Upon touchdown, the airplane bounced back airborne and the pilot's knee inadvertently moved the throttle control forward, increasing the engine power. Shortly after he realized that the airplane was accelerating between his applications of brakes. The airplane continued off the end of the airstrip and impacted a ditch, resulting in substantial damage to the right wing.

Probable cause

The pilot's inadvertent movement of the throttle control during landing, which resulted in an increase in power and excursion from the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11CA052
Event ID
20101103X70916
Case number
CEN11CA052
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: 5cdd65a3b416201f38112659fe45403b1d71cfa95fe44bed74fe0301dff1e050; retrieved 2026-09-15T15:32:21.322Z.