WPR10CA257 · Cessna 180A
Cada Cattle Cessna 180A · Accident: collision with terrain/object (non-CFIT) during landing
From Davenport Municipal Airport (68S) to Kettle Falls, WA (no airport)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR10CA257
- 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
Cessna 180A
- Aircraft type
- Cessna 180
- 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
- N9104R
- Operator
- Cada Cattle
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Davenport Municipal Airport (68S), Davenport, WATo Kettle Falls, WA (no airport)
- 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
- Collision with terrain/object (non-CFIT)
- 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
- Environmental issues › Physical environment
- 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 stated that while in flight he encountered frequent isolated rain storms. During the approach there was light rain with good visibility. The pilot reported a normal touchdown and a reduction in forward visibility as the light rain became heavy rain. At approximately 150 feet from the end of the airstrip the pilot saw an 18 inch elevated driveway and applied heavy braking and right rudder resulting in a low speed skid. The left main gear impacted the driveway and the aircraft continued to slide over the road bed. The impact resulted in substantial damage to the left wing, fuselage, and firewall.
Probable cause
The pilot's failure to maintain clearance from obstacles during the landing roll. Contributing to the accident was the reduced visibility due to precipitation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA257
- Event ID
- 20100524X35104
- Case number
- WPR10CA257
- 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: 6e455f9d718af5c5e27d44869720f64fca17f3372c72e65f4b1a38f2fc125b67; retrieved 2026-09-15T14:11:51.884Z.