WPR09LA203 · Extra EA-300
Otter Enterprises Extra EA-300 · Accident: collision with terrain/object (non-CFIT) while maneuvering
From Santa Barbara Municipal Airport (SBA) to Santa Barbara Municipal Airport (SBA)
Event
- NTSB case
- WPR09LA203
- 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
- 1 · 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 EA-300
- 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
- N101PK
- Operator
- Otter Enterprises
- Onboard fatalities
- Unknown
- Route
- From Santa Barbara Municipal Airport (SBA), Santa Barbara, CATo Santa Barbara Municipal Airport (SBA), Santa Barbara, CA
- 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
- Maneuvering · aerobatics
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A witness observed the airplane performing aerobatics over the ocean for about 10 minutes prior to the accident. The maneuver was the same; the airplane would fly straight up, roll 360 degrees as in a loop, descend, and then pull back up into the same maneuver. On the maneuver that culminated in the accident he saw the airplane fly straight up, flip over, and enter into a 45-degree descent toward the water. He expected the airplane to pull up into the same maneuver; however, the airplane continued its descent until it impacted the water. The witness reported that he was not able to see any detail as the airplane was off in the distance.
Probable cause
The pilot's failure to maintain clearance with terrain for undetermined reasons while performing aerobatics.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09LA203
- Event ID
- 20090420X30037
- Case number
- WPR09LA203
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2009-04-20.
- API snapshot SHA-256: 3265c0d6db96504f086c8e5df5d199060d74946c56c6285299619285d95d8fa3; retrieved 2026-09-13T20:04:34.403Z.