GAA15CA011 · Piper PA18 - 150
Soaring Society Of Boulder Piper PA18 - 150 · Accident: abnormal runway contact during landing
From Boulder Municipal Airport (KBDU) to Boulder Municipal Airport (KBDU)
Event
- NTSB case
- GAA15CA011
- 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 PA18 - 150
- Aircraft type
- Piper PA18
- 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
- N4785F
- Operator
- Soaring Society of Boulder
- Onboard fatalities
- Unknown
- Route
- From Boulder Municipal Airport (KBDU), Boulder, COTo Boulder Municipal Airport (KBDU), Boulder, CO
- Aircraft age
- About 52 years (built 1963)
- 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 · flare/touchdown
- 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
- Abnormal runway contact
- 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
- 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
While conducting a flight to practice landings in a tailwheel equipped airplane, the pilot made an approach to the runway. During the landing, the airplane touched down on the runway and bounced. The pilot attempted to regain control of the airplane as it touched down several times. The airplane exited the right side of the runway onto the grass and the left wing struck an embankment. A postaccident examination revealed the airplane sustained substantial damage to the left wing and aileron. The pilot reported no mechanical malfunctions or failures with the airplane prior to the accident that would have precluded normal operation of the airplane.
Probable cause
The pilot's loss of directional control during a bounced landing, which resulted in a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA011
- Event ID
- 20150321X24500
- Case number
- GAA15CA011
- 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: 82f1af6f0e86ccf08ffde10c2ba5074767772c34f897be7492508815040f656e; retrieved 2026-09-16T02:10:01.674Z.