# Accident 20091101021459A: Piper PA18150, Grangeville, ID, November 1, 2009

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 1, 2009, 07:15 local time
- Place: Grangeville, ID
- Airport: Pinnacle
- Damage: Substantial damage
- Phase of flight: Landing
- Operating rules: General operating rules (Part 91)
- Location: 46.3773° N, 117.0112° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=46.3773&lon=-117.0112&mi=10
- Aircraft: N82213, registered now (https://openairdocs.org/aircraft/N82213) (OpenAirDocs)
- Registry model: Piper PA-18-150 (registry code 7101828, https://openairdocs.org/model/piper-pa-18-150) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA18150
- Reported engine: LYC O320*
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot flight hours: 2,101 total, 567 in this make and model, 14 in the last 90 days
- NTSB investigation: [NTSB WPR10CA049](https://openairdocs.org/ntsb/WPR10CA049) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20091101021459A

## Narrative

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

^PRIVACY DATA OMITTED^ WAS LANDING AT A PRIVATE AIRSTRIP NAMED PINNACLE AIRSTRIP (01D8) ABOUT 10 MILES SOUTH OF THE GRANGEVILLE AIRPORT.  HE ELECTED TO GO AROUND BECAUSE OF A TAILWIND.  HE STRUCK BRUSH AND VEGETATION ON THE SIDE OF THE RUNWAY THAT CAUSED THE AIRCRAFT TO CRASH.  THE AIRCRAFT ENDED UP ON ITS BACK OFF OF THE RUNWAY.  WHEN ASKED WHY THE DELAY IN NOTIFYING THE FAA ABOUT THE ACCIDENT HE SAID HE HAD BEEN BUSY REMOVING THE AIRCRAFT FROM THE ACCIDENT SITE.

## 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 WPR10CA049](https://openairdocs.org/ntsb/WPR10CA049), Nov 1, 2009: Piper PA-18-150 (N82213), Lewiston, ID, substantial damage. Probable cause: The pilot's delayed decision to execute a go-around in gusting winds and with up-sloping terrain.

## Other reports on N82213 (3)

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

- [Accident 20111030026129A](https://openairdocs.org/incident/20111030026129A), Oct 30, 2011: Piper PA-18-150 (N82213), Grangeville, ID, Substantial damage. At the time of the accident [privacy data omitted] performed a 3 point landing on runway 7 at gic. He then raised the tail wheel and lowered the tail wheel to…
- [Incident 19890408023149I](https://openairdocs.org/incident/19890408023149I), Apr 8, 1989: Piper PA18150 (N82213), Dallas, TX, Minor damage. Student lost control on landing. Instructor told him to release controls. Veered off runway.
- [Accident 19840618074769A](https://openairdocs.org/incident/19840618074769A), Jun 18, 1984: Piper PA18150 (N82213), Blue Ridge, TX, Substantial damage. Glided low over prospective landing area. Engine failed to respond. Nosed over braking to miss cattle on landing.

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.