WPR24LA169 · Piper PA-22-150
Piper PA-22-150 · Accident: loss of control on ground during landing
From Scappoose Industrial Airpark (SPB) to an unrecorded destination
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
- WPR24LA169
- 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
- Event fatalities
- Unknown
- 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
- N3267Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Scappoose Industrial Airpark (SPB), Scappoose, ORTo not recorded
- 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
- Loss of control on ground
- 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
The pilot reported that during landing, the airplane was fast and subsequently began to deviate to the left. The pilot attempted to correct with opposite rudder, aileron, and brakes; however, the airplane ground looped to the left, and the right main landing gear collapsed. The right wing struck the ground during the ground loop, which resulted in substantial damage. The pilot reported no preimpact mechanical malfunctions or anomalies that would have precluded normal operation. At the time of the accident, the pilot was landing on runway 31L, and the wind was from 250° at 6 knots, gusting to 14 knots. Given the crosswind conditions at the time, the pilot likely did not maintain directional control during the landing roll.
Probable cause
The pilot’s failure to maintain direction control during the landing roll with a left crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24LA169
- Event ID
- 20240604194384
- Case number
- WPR24LA169
- 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, cause areas. 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: 618824bdcc7efc0027ce484deea403365139945ca6c2043dbd4122c1a9485861; retrieved 2026-09-16T18:50:49.576Z.