FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03LA107 · McBride Avid Flyer

12 Apr 2003 · Anderson, IN, United States

McBride Avid Flyer · Accident: overrun during landing

From Marion Municipal Airport (MZZ) to Anderson Municipal Darlington Field (AID)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

McBride Avid Flyer

Aircraft type
Mcbride AVID FLYER
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
N29MD
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Marion Municipal Airport (MZZ), Marion, INTo Anderson Municipal Darlington Field (AID), Anderson, IN
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
Landing · landing roll
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
Overrun
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The amateur-built airplane sustained substantial damage during landing rollout when the airplane nosed over in a ditch. The pilot reported he was conducting a series of high speed taxi tests. He reported, "On the third run, I continued to 'fast taxi' and I suddenly found myself off the ground and in an unstable position." He did not intend to takeoff. Once airborne, the pilot decided, "It would be prudent to familiarize myself with the aircraft as best as I could before I attempted to land." The pilot reported he no experience flying that model airplane before, so he practiced flying the airplane for about an hour before he attempted to land. He decided to land on the grass adjacent to the runway. He reported, "The rollout was smooth, but my speed was excessive and I knew I would not be able to stop the aircraft before I came to the threshold lights." The pilot steered the airplane away from the threshold lights, but the airplane went into a ditch and nosed over.

Probable cause

The pilot's misjudgment of speed which resulted in a landing overrun. The pilot's lack of experience in make and model airplane, and the ditch were contributing factors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03LA107
Event ID
20030415X00512
Case number
CHI03LA107
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, coordinates. 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: 0e7396028b317597fea374ee7554c56ec9a65d534921c6621b3392ecb17689d3; retrieved 2026-09-22T09:25:11.614Z.