WPR26LA187 · Cirrus Design Corp SR20
Cirrus Design Corp SR20 · Accident: loss of control on ground during landing
From Falcon Field (FFZ) to an unrecorded destination
Event
- NTSB case
- WPR26LA187
- 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
Cirrus Design Corp SR20
- Aircraft type
- Cirrus SR20
- 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
- N806DM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Falcon Field (FFZ), Mesa, AZTo not recorded
- Aircraft age
- About 13 years (built 2013)
- 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
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
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 while on the final leg of the traffic pattern at the destination airport, he applied left crosswind correction and noted that the right rudder pedal was stiff. When the main landing gear contacted the runway surface, the rudder pedal was stuck. The pilot attempted to maintain control of the airplane; however, the airplane yawed to the right and exited the runway surface. Subsequently, the left wing impacted an airport sign, which resulted in substantial damage. At the time of the accident, the pilot was landing the airplane on runway 21 with the wind from 150° at 12 knots, gusting to 23 knots. Post accident examination revealed that a plastic foreign object was stuck in the right rudder pedal. The pilot added that during the flight, he observed a plastic foreign object bouncing around the cockpit earlier in the flight but was not sure what it was.
Probable cause
The pilot’s inability to maintain directional control due to a plastic foreign object jammed in the rudder pedals, while landing with a gusting left crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR26LA187
- Event ID
- 20260515202998
- Case number
- WPR26LA187
- 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: 96520b6575026e1a201528ccce6ed59d1067baed1efb59b435850356a3e088a0; retrieved 2026-09-16T21:29:12.596Z.