WPR10CA049 · Piper PA-18-150
Piper PA-18-150 · Accident: collision with terrain/object (non-CFIT) on approach
From S80 · Grangeville, ID to Pinnacle Airport (0ID8)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR10CA049
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-18-150
- Aircraft type
- Piper PA-18
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N82213
- Operator
- James J. Babb · private individual
- Onboard fatalities
- Unknown
- Route
- From S80 · Grangeville, IDTo Pinnacle Airport (0ID8), Grangeville, ID
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR go-around
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Collision with terrain/object (non-CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot, who was making a visual-flight-rules approach to an 800-foot-long remote airstrip, overflew the runway to observe the windsock. Because he observed the windsock hanging limp, he assumed that the winds around the runway were calm, and therefore continued his approach. About the time he reached the approach end of the uphill-sloping runway, the airplane encountered a strong tailwind gust, which pushed it "…too far up the strip to land." The pilot therefore executed a go-around, but his decision was "too late" and he was therefore unable to outclimb the terrain on the departure end of the runway. During the go-around sequence, the airplane's landing gear came in contact with brush and it flipped over onto its back. Ground witnesses told the pilot that all morning the winds had been variable in direction and had been changing rapidly from nearly calm to gusting as high as 20 miles per hour.
Probable cause
The pilot's delayed decision to execute a go-around in gusting winds and with up-sloping terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA049
- Event ID
- 20091109X84233
- Case number
- WPR10CA049
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 519ac4963f68bae6648c560d69da695dc6a127868608d6430dc1a131985aaf70; retrieved 2026-09-15T13:28:53.288Z.