# Accident 19980726046599A: Amtr DRAGONFLY, Caro, MI, July 26, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 26, 1998, 11:45 local time
- Place: Caro, MI
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 43.4807° N, 83.3993° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=43.4807&lon=-83.3993&mi=10
- Aircraft: N14U, registered now (https://openairdocs.org/aircraft/N14U) (OpenAirDocs)
- Registry model: Luckey Alan W DRAGONFLY (registry code 05620PJ, https://openairdocs.org/model/luckey-alan-w-dragonfly) (OpenAirDocs)
- Registry engine: Volkswagen CONVERSION (registry code 63501, https://openairdocs.org/engine/volkswagen-conversion) (OpenAirDocs)
- Reported make and model: AMTR DRAGONFLY
- NTSB investigation: [NTSB CHI98LA281](https://openairdocs.org/ntsb/CHI98LA281) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980726046599A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) AIRCRAFT WAS ON DESCENT AT MEDIUM POWER WHEN THE PILOT EXPERIENCED AN ENGINE VIBRATION. PILOT ATTEMPTED AN EMERGENCY LANDING ON A STREET. HE APPLIED POWER TO CLEAR ELECTRICAL WIRES DURING APPROACH AND EXPERIENCED A SEVERE VIBRATION WHICH CAUSED CRANKSHAFT TO FAIL AT PROPELLER ATTACH BOLT.PROPELLER DEPARTED AIRCRAFT.  DAMAGE WAS ISOLATED TO ENGINE AND LEFT CANARD.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CHI98LA281](https://openairdocs.org/ntsb/CHI98LA281), Jul 26, 1998: Luckey Dragonfly II (N14U), Caro, MI, substantial damage. Probable cause: an improper inflight decision when he mistook the road for the runway of the nearby airport to land on. A factor in this accident was the total failure of the engine's crankshaft.

## Other reports on N14U (1)

Matched to the same aircraft by N-number and date.

- [Incident 19940623028659I](https://openairdocs.org/incident/19940623028659I), Jun 23, 1994: Amtr DRAGONFLY (N14U), Indiana, PA. Right brake failed landing. Veered off left side. Stayed on grass to stop without using one brake only.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.