# NTSB WPR13CA328: Cessna 172S, N625SP, Redlands, CA, July 15, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 15, 2013, 13:05 local (20:05 UTC) - Place: Redlands, CA - Coordinates: 34.08472, -117.156112 - Nearby events: https://openairdocs.org/map.md?lat=34.0847&lon=-117.1561&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report November 19, 2013 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 87483 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR13CA328 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/87483/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=87483 - Page: https://openairdocs.org/ntsb/WPR13CA328 ## Probable cause The student pilot's improper flare and unsuccessful attempt to correct a bounced landing, which resulted in the overrun landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Effect on equipment; cases with it: [Cessna 172S, 21 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=2072439), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Student/instructed pilot (probable cause); cases with it: [Cessna 172S, 41 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072439), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 99 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072439), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Terrain: rough terrain](https://openairdocs.org/ntsb-findings/03021015): Environmental issues › Physical environment · Not specified; cases with it: [Cessna 172S, 4 cases](https://openairdocs.org/ntsb-findings/03021015/cases.md?model=2072439), [All aircraft, 442 cases](https://openairdocs.org/ntsb-findings/03021015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Cessna 172S, 5 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=2072439), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cessna 172S, 76 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072439), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis During a solo cross-country flight the student pilot had attempted to land twice but due to the gusty wind conditions he had aborted the attempts. On the third attempt to land, the gusty wind conditions had not changed. The student pilot reported that his approach speed was never low enough to extend the flaps beyond 10 degrees. On touchdown the airplane bounced twice, and on the third touchdown point he reported he was "far down the runway and still had a lot of speed." The student pilot determined that the airplane was traveling too fast to stop prior to the runway ending, so he attempted to turn left at the runway end taxiway. The airplane did not negotiate the turn and the airplane departed the taxiway and into a drainage ditch. The airplane sustained substantial damage to the landing gear and to the right wing. The student pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Factual narrative During a solo cross-country flight the student pilot had attempted to land two times but due to the gusty wind conditions he had aborted the attempts. On the third attempted landing the gusty wind conditions had not changed. The student pilot reported that his approach speed was never low enough to extend the flaps beyond 10 degrees. On touchdown the airplane bounced two times, and on the third touchdown point he reported he was "far down the runway and still had a lot of speed." The student pilot determined that the airplane was traveling too fast to stop prior to the runway ending, so he attempted to turn left at the runway end taxiway. The airplane did not negotiate the turn and the airplane departed the taxiway and into a drainage ditch. The airplane sustained substantial damage to the landing gear and to the right wing. The student pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N625SP](https://openairdocs.org/aircraft/N625SP), registered now, S/N 172S8616, built 2000 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S8616 - Airframe hours: 4419 - Engines: LYCOMING IO360 L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Mustang Sally Aviation LLC, doing business as Accessible Aviation International, Inc. FliteServe - Registered owner: Mustang Sally Aviation LLC - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: 100 hour, May 31, 2013, 88 hours before - Departed: LGB, Long Beach, CA - Destination: REI, Redlands, CA - Airport: REI, Redlands Municipal Airport, runway 26, 4,504 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 36; injuries: none; student; medical: class 2, without waivers/limitations; seat: left; flight hours: 68 total, 68 in this make and model, 7 as pilot in command, 56 in the last 90 days, 8 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 200° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 90 °F, dew point 54 °F - Altimeter: 29.87 inHg - Observed at: KREI ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20130715014269A](https://openairdocs.org/incident/20130715014269A), Jul 15, 2013: Cessna 172S, Redlands, CA, Substantial damage. The aircraft touched down half way down the runway. When brakes were applied the aircraft left the runway, and came to rest in a ditch that paralleled the… ## Docket (1 files) The files NTSB released with the investigation on October 22, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=87483. 3.1 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40401498&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.