MIA88FA213 · Franklin DRIFTER XP-503 DRIFTER XP
Maxair Aircraft Franklin DRIFTER XP-503 DRIFTER XP · Accident: airframe, component or system failure while maneuvering
Event
- NTSB case
- MIA88FA213
- 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
- 2 · 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
Franklin DRIFTER XP-503 DRIFTER XP
- Aircraft type
- Franklin DRIFTER XP-503
- 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
- N65DF
- Operator
- Maxair Aircraft
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Flight control, aileron attachment › Failure, total
- Flight control, aileron › Flutter
- Pilot in command › Airspeed(vne), exceeded
- Pilot in command › Design stress limits of aircraft, exceeded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE OWNER RPRTD THE PLT FLEW THE ACFT AT A COMPANY PICNIC WITHOUT AUTHORIZATION. COMPANY PSNL SAW THE EXPERIMENTAL, AMATEUR BUILT ACFT TAKEOFF FROM THE COMPANY STRIP, THEN MANEUVER FOR A LOW PASS OVER THE AREA AT ABOUT 150 TO 200 FT AGL. SOME ESTIMATED THE PASS WAS MADE WITH A SPEED IN EXCESS OF 100 MPH. THE NEVER EXCEED (VNE) SPEED FOR THE ACFT WAS 95 MPH. AS THE ACFT APCHD THE AREA OF THE PICNIC, WITNESSES HEARD A BUZZING OR FLUTTERING SOUND. AS IT CONTINUED OVERHEAD, WITNESSES NOTED THE LEFT AILERON HAD BECOME DETACHED FROM THE OUTBOARD END & HAD FOLDED AFT. SUBSEQUENTLY, THE RGT AILERON FAILED IN A SIMILAR MANNER. THE ACFT ENTERED A CLIMB & SOME WITNESSES NOTED A POWER REDUCTION AS IF THE PLT WAS TRYING TO SLOW THE ACFT. HOWEVER, THE ACFT ROLLED & ENTERED A DSCNT WHICH WAS DESCRIBED AS A STALL/SPIN CONDITION. RPRTDLY, THE PLT WAS AWARE OF THE ACFT'S TENDENCY TO ENCTR AILERON BUZZ OR FLUTTER WHEN ACCELERATED ABOVE 100 MPH.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA88FA213
- Event ID
- 20001213X26294
- Case number
- MIA88FA213
- 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: 48f8c9ddfa40b459859126c4f09411795da111fa7e314dfa4a690cfa5a220437; retrieved 2026-09-21T03:39:31.282Z.