FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13CA192 · Piper PA-22-150

9 Apr 2013 · Moose Creek Ranger Station, ID, United States

Piper PA-22-150 · Accident: nose over/nose down during landing

From Kooskia Municipal Airport (S82) to Moose Creek US Forest Service Airport (1U1)

Report a problem

Event

NTSB case
WPR13CA192
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-22-150

Aircraft type
Piper PA-22
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
N3505P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kooskia Municipal Airport (S82), Kooskia, IDTo Moose Creek US Forest Service Airport (1U1), Moose Creek Ranger Station, 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
Landing · landing roll
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
Nose over/nose down
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that he overflew the turf airstrip and observed the windsock, which indicated "little to no wind." While on short final, and beyond the point where he could accomplish a safe go-around, he realized that he was landing with a tailwind. He saw some deer that had emerged from the trees and were on the runway and had to add power to avoid them. He continued the landing, and after touchdown, he applied heavy braking in an attempt to prevent the airplane from overrunning the runway. The airplane subsequently nosed over and came to rest inverted. The vertical stabilizer, the rudder, and the top of both wings sustained substantial damage. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's use of excessive braking after landing with a tailwind and after an extended touchdown to avoid deer on the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13CA192
Event ID
20130415X04257
Case number
WPR13CA192
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, coordinates. 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: f079b5b64878c4a29f924be9bcbdecd5f444ba54512b88228e9822378ef0cfb2; retrieved 2026-09-15T21:18:10.083Z.