FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MKC84FU003 · American Aerolights EAGLE XL

5 May 1984 · MILLARD, NE, United States

American Aerolights EAGLE XL · Accident: dragged wing, rotor, pod, float or tail/skid during landing

From Millard Airport (MLE) to an unrecorded destination

Report a problem

Event

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

American Aerolights EAGLE XL

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
UNREG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Millard Airport (MLE), MILLARD, NETo 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 103: Ultralight
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 · flare/touchdown
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
Dragged wing, rotor, pod, float or tail/skid
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

  • Pilot in command › Compensation for wind conditions, improper
  • Pilot in command › Directional control, not maintained
  • Pilot in command › Ground loop/swerve, inadvertent

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

NTSB narrative

THE PLT OF THE ULTRALIGHT VEHICLE WAS FLYING AS #2 IN A FLT OF 2. THE PLT OF THE LEAD ACFT STATED THAT THEY OBSERVED RAIN SHOWERS SOUTH OF MILLARD & ELECTED TO RETURN TO THE ARPT AHEAD OF THE PRECIPITATION. AFTER ARRIVING, THEY LANDED ON A 40 FT WIDE TAXIWAY BESIDE RWY 12. THERE WERE HANGAR STRUCTURES APRX 100 FT TO THE RIGHT OF THE TAXIWAY. THE LEAD PLT SAID THAT HE ENCOUNTERED TURBULENCE ON SHORT FINAL APCH & DURING THE FLARE. THE # 2 PLT LANDED IN TRAIL. DURING #2'S LANDING, THE RIGHT WING CONTACTED THE TAXIWAY, THEN THE VEHICLE TURNED RIGHT TO APRX 200 DEG. THE #2 PLT INITIATED A GO-AROUND, BUT THE VEHICLE COLLIDED WITH A HANGAR AT AN ELEVATION OF ABOUT 10 FT AGL.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MKC84FU003
Event ID
20001214X39685
Case number
MKC84FU003
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: e91c2188ce0e22c5655edd002f68cf8349ac13dbfe699dc96bf9cad33ffdf282; retrieved 2026-09-21T17:37:29.207Z.