# Incident 20070827017379I: Maule M4220C, Twin Falls, ID, August 27, 2007

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 27, 2007, 10:30 local time
- Place: Twin Falls, ID
- Airport: Joslin Field - Magic Valley Rg
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 42.5641° N, 114.4609° W: Placed by OpenAirDocs: center of Twin Falls, ID, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=42.5641&lon=-114.4609&mi=10
- Aircraft: N2039U, registered now (https://openairdocs.org/aircraft/N2039U) (OpenAirDocs)
- Registry model: Maule M-4-220C (registry code 5460114, https://openairdocs.org/model/maule-m-4-220c) (OpenAirDocs)
- Registry engine: Franklin 6V 350 series (registry code 27043, https://openairdocs.org/engine/franklin-6v-350-series) (OpenAirDocs)
- Reported make and model: MAULE M4220C
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 1,767 total, 5 in this make and model, 88 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20070827017379I

## Narrative

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

(-23) UPON LANDING AT TWF ON RUNWAY 25, THE AIRCRAFT BOUNCED AND VEERED TO THE RIGHT AND STRUCK A RUNWAY SIGN, DAMAGING THE RIGHT MAIN GEAR STRUT AND LEFT WING TIP.

## Other reports on N2039U (2)

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

- [Accident 20080305011529A](https://openairdocs.org/incident/20080305011529A), Mar 5, 2008: Maule M4220C (N2039U), Jerome, ID, Substantial damage. (-23) On take off, student pilot added power and aircraft started down the center line of the runway. The aircraft's nose turned a few degrees to the left and…
- [Incident 19891003053889I](https://openairdocs.org/incident/19891003053889I), Oct 3, 1989: Maule M4220C (N2039U), Visalia, CA, Minor damage. Pilot lost directional control on landing and ground looped.

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.