FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10CA445 · Columbia Aircraft MFG LC42-550FG

26 Aug 2010 · Tampa, FL, United States

Columbia Aircraft MFG LC42-550FG · Accident: ground collision while standing

From Tampa Executive Airport (VDF) to Tampa Executive Airport (VDF)

Report a problem

Event

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

Columbia Aircraft MFG LC42-550FG

Aircraft type
Columbia LC42
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
N1321C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tampa Executive Airport (VDF), Tampa, FLTo Tampa Executive Airport (VDF), Tampa, FL
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
Standing · engine(s) start-up
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
Ground collision
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 proceeded through the pre-engine start checklist and set the parking brake. After several failed attempts to start the engine, he increased the power lever setting before another start attempt. The engine subsequently started and the airplane abruptly lurched forward toward another airplane parked 150 feet directly ahead. The pilot immediately applied right rudder, which turned his airplane to the right; however, the right wing struck the parked airplane, resulting in substantial damage. The pilot exited the airplane uneventfully after it skidded to a stop. A witness reported hearing the airplane's engine start and described that it sounded as if the airplane was ready to take off. A photograph revealed tire skid marks leading to and beyond the parked airplane.

Probable cause

The pilot's failure to reduce engine power following a high-powered engine start.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10CA445
Event ID
20100826X75914
Case number
ERA10CA445
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: 911570b1b56d0c8938bc88278a105ebe6e702194739dc8a6ca2a38dba54df38f; retrieved 2026-09-15T14:58:20.950Z.