FTW90DRD06 · Stolt ACRODUSTER II ACRODUSTER
Stolt ACRODUSTER II ACRODUSTER · Accident: hard landing
From Esler Army Airfield / Esler Regional Airport (ESF) to an unrecorded destination
Event
- NTSB case
- FTW90DRD06
- 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
Stolt ACRODUSTER II ACRODUSTER
- Aircraft type
- Stolt ACRODUSTER
- 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
- N63BD
- Operator
- Unk
- Onboard fatalities
- Unknown
- Route
- From Esler Army Airfield / Esler Regional Airport (ESF)To 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
- 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
- Hard landing
- 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
- Pilot in command › Flare, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS DISSIPATING AIRSPEED OVER THE RUNWAY, IN THE OPEN COCKPIT BIPLANE. HE SAID HIS HELMET SLIPPED BACK ON HIS HEAD AND DURING HIS ATTEMPT TO READJUST IT, THE LEFT WING CAME UP AND DURING HIS CORRECTION, THE PROPELLER STARTED HITTING THE RUNWAY. HE SHUT OFF THE ENGINE, FLEW FURTHER DOWN THE RUNWAY AND LANDED. HE SAID HIS NEXT TOUCHDOWN WAS SMOOTH BUT THE MAIN GEAR COLLAPSED, AND THE BOTTOM OF THE FUSELAGE STARTED SLIDDING ON THE RUNWAY. A FIRE STARTED AND AS THE PILOT EVACUATED THE AIRPLANE, HE WAS BURNED ON THE FACE AND HANDS. AFTER HE MOVED AWAY FROM THE AIRPLANE, MORE FIRE ERUPTED IN THE AIRPLANE. LATER INVESTIGATION REVEALED THAT THE MAIN LANDING GEAR SPREAD OUT AND THE FUSELAGE BOTTOM HIT THE RUNWAY ON THE FIRST IMPACT. FIRE STARTED WITH FUEL FROM A BROKEN FUEL STRAINER VALVE.
Probable cause
THE PILOT MISJUDGED THE LANDING FLARE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW90DRD06
- Event ID
- 20001212X22917
- Case number
- FTW90DRD06
- 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: 4f82059af165ad6fafab4a694912855d4e3cbf0ffd5438b8e3cc8cdd103fb690; retrieved 2026-09-21T15:43:24.102Z.