WPR10LA242 · Grumman AA-5A
Salem Pilots Association Grumman AA-5A · Accident: loss of control on ground during landing
From Salem-Willamette Valley Airport/McNary Field (SLE) to Monument Municipal Airport (12S)
Event
- NTSB case
- WPR10LA242
- 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
Grumman AA-5A
- Aircraft type
- Grumman AA-5
- 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
- N26414
- Operator
- Salem Pilots Association
- Onboard fatalities
- Unknown
- Route
- From Salem-Willamette Valley Airport/McNary Field (SLE), Salem, ORTo Monument Municipal Airport (12S), Monument, OR
- 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 · 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
- Loss of control on ground
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the airplane touched down hard at an angle near the approach end of the runway. After touchdown, the airplane veered to the right, departed the runway, and collided with 10-foot juniper trees. The pilot stated that the runway was sloped with a hump in the middle and a slight dogleg. He had previously landed downhill, but the local pilots recommended uphill. He thought that the different sight picture resulted in the early flare and subsequent hard landing. The pilot reported no mechanical failures or malfunctions with the airplane at the time of the accident.
Probable cause
The pilot’s misjudged flare during landing resulting in a hard landing and loss of directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10LA242
- Event ID
- 20100515X63412
- Case number
- WPR10LA242
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2010-05-15.
- API snapshot SHA-256: 6b989ffd492dbf076d64ab79388366b2d14f918ff69b15d8fa229e25c66a45a1; retrieved 2026-09-15T14:05:51.043Z.