# Accident 19880404048919A: Cessna 207, Hardwick, MN, April 4, 1988

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 4, 1988, 18:20 local time
- Place: Hardwick, MN
- Damage: Destroyed
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: Air taxi and commuter (Part 135)
- Operator: AFEA
- Location: 43.7706° N, 96.1896° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=43.7706&lon=-96.1896&mi=10
- Aircraft: N207CA, a cancelled registration (https://openairdocs.org/deregistered/N207CA-1988-12-05) (OpenAirDocs)
- Registry model: Cessna 207 (registry code 2073602, https://openairdocs.org/model/cessna-207) (OpenAirDocs)
- Reported make and model: CESSNA 207
- Reported engine: CONT IO520F
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 8,000 total, 260 in this make and model, 42 in the last 90 days
- NTSB investigation: [NTSB CHI88FA092](https://openairdocs.org/ntsb/CHI88FA092) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19880404048919A

## Narrative

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

OBSERVED FLYING ERRATICALLY OVER A FARM. DIVED INTO TREES AND FARM BUILDINGS CAUSE UNKNOWN. POSSIBLE INCAPACITATION

## 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 CHI88FA092](https://openairdocs.org/ntsb/CHI88FA092), Apr 4, 1988: Cessna 207 (N207CA), Hardwick, MN, destroyed, 1 fatal

## Other reports on N207CA (1)

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

- [Incident 19831108070499I](https://openairdocs.org/incident/19831108070499I), Nov 8, 1983: Cessna 207 (N207CA), Buffalo, ND. Engine malfunction. Emergency landing on highway. Crankshaft broke. One connecting rod broke.

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.
