WPR10CA177 · Cessna 170
Cessna 170 · Accident: loss of control on ground during landing
From Indian Hills Airpark (2AZ1) to Kingman Airport (IGM)
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
- WPR10CA177
- 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 170
- Aircraft type
- Cessna 170
- 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
- N4200V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Indian Hills Airpark (2AZ1), Solome, AZTo Kingman Airport (IGM), Kingman, AZ
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was landing the tailwheel-equipped airplane when he lost control and veered off the runway. He stated that the three-point landing was “textbook” and on the runway centerline; however, during the rollout the airplane veered to the left. The pilot attempted to regain control of the airplane by applying rudder inputs but was not successful. The airplane exited the runway; the right main landing gear separated and the right wing then impacted the ground. The pilot reported that after the accident the passenger told him that he applied rudder during the landing to help the pilot. The pilot stated that in the future he would be more assertive whenever there was someone with access to controls as to who is the actual manipulator of the controls.
Probable cause
The pilot’s failure to maintain directional control during landing rollout. Contributing to the accident was flight control interference by the passenger.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA177
- Event ID
- 20100325X03756
- Case number
- WPR10CA177
- 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. 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: b3718e02bce96d4b102ce157780ad79b5f1db650b62add846a49afa3e77a5cab; retrieved 2026-09-15T13:47:28.411Z.