FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11CA128 · Excalibur Aircraft Excalibur

30 Jan 2011 · Immokalee, FL, United States

Excalibur Aircraft Excalibur · Accident: loss of control in flight during takeoff

From Immokalee Regional Airport (IMM) to Immokalee Regional Airport (IMM)

Report a problem

Event

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

Excalibur Aircraft Excalibur

Aircraft type
Excalibur EXCALIBUR
Category
Ultralight
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
N818RJ
Onboard fatalities
Unknown
Route
From Immokalee Regional Airport (IMM), Immokalee, FLTo Immokalee Regional Airport (IMM), Immokalee, 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
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
Loss of control in flight
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

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

NTSB narrative

The pilot reported that he was completing high speed taxi tests when the airplane inadvertently became airborne. The airplane climbed to about 50 to 70 feet above ground level and the pilot attempted to touch back down to land. The airplane descended quickly and he applied right rudder and pushed the controls forward. The airplane impacted the ground, incurring substantial damage to the wings and fuselage. Documentation provided by the airplane manufacturer recommended against high speed taxi.

Probable cause

The pilot's failure to maintain control of the airplane during a high speed taxi test resulting in unintentional flight and ground collision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11CA128
Event ID
20110130X34242
Case number
ERA11CA128
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: a89f7c7f2144908eb9317efebe6dfccd4e2e9586761efbb0a2896dee249d67e4; retrieved 2026-09-15T15:43:24.282Z.