- Date
- October 27, 2012, 12:15 local (19:15 UTC)
- Place
- Calexico, CA
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N1332DCessna 170A
- Defining event
- Landing-flare/touchdown: Loss of control on ground
- Weather
- Visual (VMC) · Day
- Status
- Completed · report January 31, 2013
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- FAA FSDO
- FAA report
- 20121027024329A
- Case key
- 85447
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot's failure to maintain directional control during an attempted go-around, which resulted in a runway excursion.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
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.
Factual 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 at about 6 to 8 knots. He then flew a traffic pattern for landing on runway 26, which was 75 feet wide. 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, and 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 impact resulted in damage, and the end of the takeoff attempt. The airplane came to rest upright, with the right main landing gear fracture-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. Neither the pilot nor his passenger was injured, and both exited via the right-side cabin door. There was no fire. There was no recorded meteorological data for the accident airport, but review of meteorological data from an airport about 10 miles north of the accident airport indicated conditions similar to what the pilot reported. According to the pilot, he had a total flight experience of approximately 2,000 hours, including about 30 hours in the accident airplane make and model in the past 30 days. The pilot stated that there were no mechanical deficiencies or failures that contributed to the accident, but that he was uncertain as to exactly why he lost directional control.
Aircraft
- Registration
- N1332D
- Reported as
- Cessna 170A
- Category
- Airplane
- Serial number
- 19908
- Airframe hours
- 2,628
- Engine
- Cont Motor C145 SERIES, 145 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · June 12, 2012
- Departed
- MMRG · Rancho Grande
- Destination
- cxl · Calexico, CA
- Flight plan
- VFR
- Airport
- cxl · Calexico, runway 26, 4,683 × 75 ft, asphalt
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 64
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, With waivers/limitations
- Last flight review
- April 23, 2011
- Seat
- Left
- Flight hours
- 2,000 total · 30 in this make and model · 2,000 as pilot in command · 40 in the last 90 days · 30 in the last 30 days · 4 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 340° at 3 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 81 °F, dew point 18 °F
- Altimeter
- 29.93 inHg
- Observed at
- IPL, 10 nm away
Docket · 5
The files NTSB released with the investigation on December 5, 2012, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.5 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N1332D · 1
Matched to the same aircraft by N-number and date.