# Accident 20030819028779A: Beech 76, Hammond, MN, August 19, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 19, 2003, 00:01 local time
- Place: Hammond, MN
- Damage: Substantial damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 44.3611° N, 92.7208° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=44.3611&lon=-92.7208&mi=10
- Aircraft: N1812S (not matched to a registry record)
- Reported make and model: BEECH 76
- Reported engine: LYC O360*
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 1,000 total, 30 in the last 90 days
- NTSB investigation: [NTSB CHI03LA267](https://openairdocs.org/ntsb/CHI03LA267) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030819028779A

## Narrative

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

(-23) AT APPROX. 0001 CST ON 8/19/03 A BE-076 LOST CONTROL WHILE DEVIATING AROUND THUNDERSTORMS WITH TOPS REPORTED AT FL500. THE AIRCRAFT WAS IN CRUISE FLIGHT AT 7000 FEET WHEN THE PILOT STATED HE ENCOUNTERED IMC CONDITIONS, SOME TURBULENCE, AND THEN A LOSS OF CONTROL. THE PILOT RECOVERED AT APPROX. 3000 FEET MSL. THE PILOT STATED HE DOES NOT KNOW HOW HE RECOVERED, ONLY THAT AT ABOUT 3000' MSL HE REGAINED CONTROL. UPON ARRIVAL AT MLI HE NOTICED WRINKLING ON THE UPPER INBOARD WING SKINS.

## 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 CHI03LA267](https://openairdocs.org/ntsb/CHI03LA267), Aug 19, 2003: Beech BE-76 (N1812S), Hammond, MN, substantial damage. Probable cause: The pilot exceeded the design limits of the wings when he pulled out of an inadvertent spiral after he lost control of the airplane while operating in IMC conditions. Additional factors included the…

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.