WPR09CA295 · Piper PA-18-150
Piper PA-18-150 · Accident: nose over/nose down during landing
From Thomas Creek Airport (2U8) to Dixie, ID
Event
- NTSB case
- WPR09CA295
- 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
- N4155U
- Operator
- Peter J. Ryan · private individual
- Onboard fatalities
- Unknown
- Route
- From Thomas Creek Airport (2U8), Stanley, IDTo Dixie, 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 systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was making a landing on a dirt landing area that also doubled as the main road in the center of the remote mountain town. He intentionally landed a little long in order to miss the substantial puddle of water near the approach end of the landing area. He began applying brakes while the airplane was going about 20 miles per hour, but his brake application was of sufficient force to result in the airplane nosing over onto its back. The sequence of events resulted in substantial damage to the vertical stabilizer and one wing lift strut. The pilot said that there was nothing wrong with the braking system, and that he should have either delayed his braking or applied the brakes with "more finesse."
Probable cause
The pilot's excessive braking during the landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09CA295
- Event ID
- 20090618X45951
- Case number
- WPR09CA295
- 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: b5e974c000cc9cde9137687dc82e411e24c6d027aa885f46e255f583d7ce0ea6; retrieved 2026-09-15T11:29:38.899Z.