FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13CA024 · Cessna 170A

27 Oct 2012 · Calexico, CA, United States

Cessna 170A · Accident: loss of control on ground during landing

From MMRG · Rancho Grande to Calexico International Airport (cxl)

Report a problem

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
WPR13CA024
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 170A

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
N1332D
Operator
Unknown
Onboard fatalities
Unknown
Route Narrative disagrees
From MMRG · Rancho GrandeTo Calexico International Airport (cxl)
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 · flare/touchdown
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 private pilot/co-owner of the tailwheel-equipped airplane overflew the non-towered, paved airport to determine the wind conditions, which he determined to be from the northwest about 6 to 8 knots. He then flew a traffic pattern for landing on runway 26. During the landing flare the airplane began to drift left of the runway centerline, and at touchdown the tail of the airplane swerved to the left. The pilot unsuccessfully attempted to correct the airplane's path then initiated a go-around. He reported that after adding full power for the go-around, the airplane was headed to the right, at an angle that he estimated to be about 45 degrees from the runway alignment. Before the airplane could become airborne, it exited the right side of the runway and struck a low earthen berm. The airplane came to rest upright, with the right main landing gear fractured and separated from the fuselage. Additional damage included a bent propeller, a crushed nose cowl, crush damage to the lower fuselage, and bending and crush damage to both wings. There were no recorded meteorological data for the accident airport, but review of meteorological data from an airport about 10 miles north indicated conditions similar to those reported by the pilot. The pilot reported approximately 2,000 hours of a total flight experience, including about 30 hours in the accident airplane make and model in the past 30 days. The pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation and that he was uncertain why he lost directional control.

Probable cause

The pilot's failure to maintain directional control during an attempted go-around, which resulted in a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13CA024
Event ID
20121027X00052
Case number
WPR13CA024
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: 7f18b1ba1c8f75075ebd77f13defd9809929727e1f24669da5645c4025e06325; retrieved 2026-09-15T20:17:33.563Z.