# Accident 20120908019359A: Great Lakes 2T-1A-2, Monroe, WA, September 8, 2012

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 8, 2012, 15:15 local time
- Place: Monroe, WA
- Damage: Substantial damage
- Phase of flight: Maneuver
- Operating rules: General operating rules (Part 91)
- Location: 47.8400° N, 121.9703° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=47.8400&lon=-121.9703&mi=10
- Aircraft: N3702F, registered now (https://openairdocs.org/aircraft/N3702F) (OpenAirDocs)
- Registry model: Great Lakes 2T-1A-2 (registry code 3910101, https://openairdocs.org/model/great-lakes-2t-1a-2) (OpenAirDocs)
- Registry engine: Lycoming AEIO-360 series (registry code 41522, https://openairdocs.org/engine/lycoming-aeio-360-series) (OpenAirDocs)
- Reported make and model: GREAT LAKES 2T-1A-2
- Reported engine: LYCOMING AEIO-360-B1G6
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 479 total, 174 in this make and model, 1 in the last 90 days
- NTSB investigation: [NTSB WPR12LA409](https://openairdocs.org/ntsb/WPR12LA409) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20120908019359A

## Narrative

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

AFTER ENGINE FAILURE FORCE LANDED IN SOFT FIELD AIRCRAFT ROLLED ONTO BACK AS IT SLOWED.

## 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 WPR12LA409](https://openairdocs.org/ntsb/WPR12LA409), Sep 8, 2012: Great Lakes 2T-1A-2 (N3702F), Monroe, WA, substantial damage. Probable cause: A loss of engine power during cruise flight for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.

## Other reports on N3702F (2)

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

- [Incident 20140809015539I](https://openairdocs.org/incident/20140809015539I), Aug 9, 2014: Great Lakes 2T-1A-2 (N3702F), Pacoima, CA, Minor damage. The pilot of N3702 made a 3 point landing on runway 12, during roll out the tower asked the pilot of N3702 if he could make the next exit (cheerly). The…
- [Accident 19771008030979A](https://openairdocs.org/incident/19771008030979A), Oct 8, 1977: Grtlks 2T1A2 (N3702F), Oakland, CA, Substantial damage

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.