FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA00LA131 · McCan VELOX REV II VELOX REV

13 Apr 2000 · Mulberry, FL, United States

McCan VELOX REV II VELOX REV · Accident: airframe, component or system failure while maneuvering

From Lakeland Linder International Airport (LAL) to an unrecorded destination

Report a problem

Event

NTSB case
MIA00LA131
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
0
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

McCan VELOX REV II VELOX REV

Aircraft type
Mccan VELOX REV
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
N103MV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lakeland Linder International Airport (LAL), Lakeland, FLTo not recorded
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
First occurrenceThe 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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Flt control syst, elevator control cable/rod › Undetermined

Approximate · Estimated position: the centre of Mulberry, FL, the place the record names. Not the accident site.

NTSB narrative

The pilot was performing an aerobatic sequence in preparation for an airshow. After several maneuvers he experienced a loss of elevator control while inverted. He jettisoned the canopy and bailed out. Examination of the flight control system revealed a failure of the elevator pitch control rod. Further analysis of the pitch control rod revealed the rod had failed in bending overstress for undetermined reasons.

Probable cause

The bending overstress separation of the elevator pitch control rod for undetermined reasons. This resulted in an in-flight loss of control, bail out, and subsequent in-flight collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA00LA131
Event ID
20001212X20878
Case number
MIA00LA131
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 9d4f9cc64ebd9681d6016252f7fb7012b942502a9e011c5ba4243069cd9a75d7; retrieved 2026-09-21T20:15:40.586Z.