# Incident 19970116007719I: Piper PA28181, Waseca, MN, January 16, 1997

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 16, 1997, 18:00 local time
- Place: Waseca, MN
- Damage: Minor damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 44.0815° N, 93.5040° W: Placed by OpenAirDocs: center of Waseca, MN, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.0815&lon=-93.5040&mi=10
- Aircraft: N2767M, registered now (https://openairdocs.org/aircraft/N2767M) (OpenAirDocs)
- Registry model: Piper PA-28-181 (registry code 7102807, https://openairdocs.org/model/piper-pa-28-181) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- Reported make and model: PIPER PA28181
- Reported engine: LYC O360A4M
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 75 total, 3 in this make and model, 3 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19970116007719I

## Narrative

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

NARRATIVE: N2767M WAS ENROUTE VFR FROM NEW ULM, MN TO ROCHESTER, MN AND RETURNED TO NEW ULM. THE PILOT STATED HE RAN OUT OF FUEL IN ONE TANK AND CHANGED TANKS, BUT THE ENGINE FAILED TO RESTART. THE PILOT MADE AN EMERGENCY LANDING IN A FIELD THREE MILES WEST OF WASECA, MN. THERE WAS ONE PERSON ON BOARD, NO REPORTED INJURIES. WHEN THE PILOT CHANGED TANKS, HE FAILED TO TURN ON THE FUEL BOOST PUMP. IMPROPER USE OF FUEL MANAGEMENT TECHNIQUES.

## Other reports on N2767M (1)

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

- [Accident 19831220062169A](https://openairdocs.org/incident/19831220062169A), Dec 20, 1983: Piper PA28181 (N2767M), Waverly, KY, Substantial damage. Encountered freezing rain en route. Lost glasses in dark. Elected to land on a road. Struck a fence on the rollout.

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.