# Accident 20000608009169A: Piper PA28181, Minneapolis, MN, June 8, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 8, 2000, 16:00 local time
- Place: Minneapolis, MN
- Airport: Flying Cloud Airport
- Damage: No damage
- Operating rules: Pilot school (Part 141)
- Location: 44.8996° N, 93.3704° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=44.8996&lon=-93.3704&mi=10
- Aircraft: N8189T, a cancelled registration (https://openairdocs.org/deregistered/N8189T-2000-07-27) (OpenAirDocs)
- Registry model: Piper PA-28-161 (registry code 7102803, https://openairdocs.org/model/piper-pa-28-161) (OpenAirDocs)
- Reported make and model: PIPER PA28181
- Fatal injuries: 0
- NTSB investigation: [NTSB CHI00LA154](https://openairdocs.org/ntsb/CHI00LA154) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000608009169A

## Narrative

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

(-23) DURING CLIMB, ENGINE QUIT WHEN A/C WAS AT 200 FT AGL. A/C CRASHED INTO A SWAMP. A/C WAS DESTROYED, OCCUPANTS RECEIVED MINOR INJURIES. DURING POST CRASH INVESTIGATION, THE ENGINE CRANKSHAFT WAS FOUND TO BE BROKEN AT THE #3 ROD BEARING JOURNAL FORWARD THROW AT THE CENTER MAIN JOURNAL. ENGINE T.T. IS 5487 HOURS AND T.S.O. IS 128 HOURS. IT WAS NOTED IN THE ENGINE MAINTENANCE RECORDS THAT THIS ENGINE EXPERIENCED A PROP STRIKE AT APPROX, 1500 HOURS T.T. AT THAT TIME ONLY A FLANGE RUN OUT CHECK WAS ACCOMPLISHED.

## 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 CHI00LA154](https://openairdocs.org/ntsb/CHI00LA154), Jun 8, 2000: Piper PA-28-161 (N8189T), Minneapolis, MN, substantial damage. Probable cause: the failure of the engine and the unsuitable terrain for landing encountered by the pilot-in-command. Factors to the accident were the fracture of the crankshaft due to fatigue, excessive main…

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.