FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09CA073 · Extra Flugzeugbau Gmbh EA 300/L

28 Nov 2008 · Tampa, FL, United States

Tampa Aircraft Holding Extra Flugzeugbau Gmbh EA 300/L · Accident: collision during takeoff/landing on approach

From Peter O Knight Airport (TPF) to Peter O Knight Airport (TPF)

Report a problem

Event

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

Extra Flugzeugbau Gmbh EA 300/L

Aircraft type
Extra EA-300
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
N505EX
Onboard fatalities
Unknown
Route
From Peter O Knight Airport (TPF), Tampa, FLTo Peter O Knight Airport (TPF), 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
Approach · VFR pattern final
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 during takeoff/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

  • Personnel issues › Psychological

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

NTSB narrative

The pilot stated that while on approach to final, and as he prepared to touchdown, he saw a sailboat that did not have its sail raised. Consequently, he did not see the sail mast. The right wing tip struck the mast and shattered. The pilot added power in an attempt to level out the airplane, but it collided with the ground. The pilot said that he did not observe any abnormalities with the airplane or the engine during his approach. Examination by a Federal Aviation Administration inspector revealed that the airplane's right wing struck the sailboat approximately 8 feet below the top of the sail mast. Witnesses to the accident reported that the sailboat was operating approximately 50 yards from the seawall when the accident occurred. They said that the airplane attempted to curve around the sailboat but as the right wing dipped it hit the mast.

Probable cause

The pilot's inadequate visual lookout, which resulted in a collision with an object.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09CA073
Event ID
20081128X83452
Case number
ERA09CA073
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: ad7c930181c88312bb04392185fc395f44831242268f5ad3860819bb47962e11; retrieved 2026-09-15T10:34:53.644Z.