# Accident 19970314003289A: Piper PA28161, Sanford, ME, March 14, 1997

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 14, 1997, 11:45 local time
- Place: Sanford, ME
- Airport: Sanford Municipal
- Damage: Substantial damage
- Phase of flight: Touch And Go Landing
- Operating rules: General operating rules (Part 91)
- Location: 43.3938° N, 70.7080° W: Placed by OpenAirDocs at , within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=43.3938&lon=-70.7080&mi=10
- Aircraft: N2914A, registered now (https://openairdocs.org/aircraft/N2914A) (OpenAirDocs)
- Registry model: Piper PA-28-161 (registry code 7102803, https://openairdocs.org/model/piper-pa-28-161) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA28161
- Reported engine: LYC O320A2B
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 16 total, 16 in this make and model, 16 in the last 90 days
- NTSB investigation: [NTSB NYC97LA060](https://openairdocs.org/ntsb/NYC97LA060) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19970314003289A

## Narrative

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

ON GO FROM TOUCH NOTED FLAPS DOWN. DUMPED SAME. SETTLED. ABORTED. LOST CONTROL INTO SNOWBANK. FULL STOP BETTER.

## 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 NYC97LA060](https://openairdocs.org/ntsb/NYC97LA060), Mar 14, 1997: Piper PA-28-161 (N2914A), Sanford, ME, substantial damage. Probable cause: the pilot's premature raising of the flaps during the initial climb after takeoff, which resulted in a stall/mush. A factor relating to the accident was: the pilot's failure to maintain proper runway…

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.