WPR12CA196 · Cessna 195 UNDESIGNAT
Cessna 195 UNDESIGNAT · Accident: loss of control on ground during takeoff
From Mogollon Airpark (AZ82) to Scottsdale Airport (SDL)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved and damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR12CA196
- 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 195 UNDESIGNAT Narrative disagrees
- Aircraft type
- Cessna 195
- 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
- N3442V
- Operator
- Richard J Adams · private individual
- Onboard fatalities
- Unknown
- Route
- From Mogollon Airpark (AZ82), Heber-Overgaard, AZTo Scottsdale Airport (SDL), Scottsdale, 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
- Takeoff
- 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 Possible conflict
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot reported that, on takeoff roll, just after the tail came up, the airplane encountered a right quartering tailwind gust, which forced the airplane off the left side of the runway. The pilot subsequently corrected back to the right, and the airplane crossed the runway, a gully, and a taxiway. He then intentionally applied right brake and ground looped the airplane to avoid colliding with a hangar, which resulted in the collapse of both main landing gears. A postcrash fire erupted shortly thereafter, which consumed the airplane.
Probable cause
The pilot's loss of directional control during takeoff roll upon encountering a wind gust.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12CA196
- Event ID
- 20120506X42842
- Case number
- WPR12CA196
- 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: b9c9fc2c53eb6361a245a050ff891e5d147f16c33156581063ce2686981d82b7; retrieved 2026-09-15T18:00:32.471Z.