# NTSB MIA08CA092: Cessna 172S, N375LP, Daytona Beach, FL, April 20, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 20, 2008, 14:27 local (18:27 UTC) - Place: Daytona Beach, FL - Coordinates: 29.179721, -81.058052 - Nearby events: https://openairdocs.org/map.md?lat=29.1797&lon=-81.0581&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 May 28, 2008 - Report: Approved by Office Director - Parties: FAA Flight Standards District Office - NTSB case key (mKey): 67863 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=MIA08CA092 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/67863/pdf - Page: https://openairdocs.org/ntsb/MIA08CA092 ## Probable cause The student pilot's improper recovery from a bounced landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Object/animal/substance: runway/taxi/approach light](https://openairdocs.org/ntsb-findings/03022012): Environmental issues › Physical environment · Not specified; cases with it: [Cessna 172S, 3 cases](https://openairdocs.org/ntsb-findings/03022012/cases.md?model=2072439), [All aircraft, 106 cases](https://openairdocs.org/ntsb-findings/03022012/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) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/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 While inbound to land, the student pilot was advised by Daytona Beach Air Traffic Control tower that the wind was from 050 degrees at 7 knots. The flight was cleared to land on runway 25L, and while on final approach to runway 25L the controller advised the pilot runway 7R was available. He elected to continue the approach to runway 25L and stated that the while landing the airplane bounced "repeatedly." While attempting to turn onto a taxiway, the airplane was too fast and skidded off the runway, onto grass, where the airplane collided with runway lights, then a ditch. ## Factual narrative While inbound to land, the student pilot was advised by Daytona Beach Air Traffic Control tower that the wind was from 050 degrees at 7 knots. The flight was cleared to land on runway 25L, and while on final approach to runway 25L the controller advised the pilot runway 7R was available. He elected to continue the approach to runway 25L and stated that the while landing the airplane bounced "repeatedly." While attempting to turn onto a taxiway, the airplane was too fast and skidded off the runway, onto grass, where the airplane collided with runway lights, then a ditch. ## Aircraft - Registration: [N375LP](https://openairdocs.org/deregistered/N375LP-2013-05-17), registration cancelled 2013-05-17, S/N 172S9375, built 2003 (OpenAirDocs) - Reported make and model: Cessna 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S9375 - Airframe hours: 2361 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: Air America Flight Center LLC - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, March 1, 2008 - Departed: EVB, New Smyrna Bch, FL - Destination: KDAB, Daytona Beach, FL - Airport: KDAB, Daytona Beach International, runway 25L, 3,195 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 34; injuries: none; student; medical: class 2; seat: left; flight hours: 72 total, 9 in this make and model, 16 as pilot in command, 9 in the last 90 days, 6 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 40° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 81 °F, dew point 55 °F - Altimeter: 29.96 inHg - Observed at: KDAB ## 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 20080420834739A](https://openairdocs.org/incident/20080420834739A), Apr 20, 2008: Cessna 172S, Daytona Beach, FL, Substantial damage. (-23) Pilot departed to practice at nearby new smyrna Beach airport (evb). Upon returning to Daytona, the ATIS "z" reported runway 25 in use. On final approach… ## Other investigations on N375LP (2) 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. - [NTSB ERA12LA274](https://openairdocs.org/ntsb/ERA12LA274), Apr 9, 2012: Cessna 172S (N375LP), Daytona Beach, FL, substantial damage. Probable cause: A total loss of engine power due to a catastrophic engine failure, the origin of which could not be determined during postaccident examination. - [NTSB MIA05LA043](https://openairdocs.org/ntsb/MIA05LA043), Dec 17, 2004: Cessna 172S (N375LP), Lakeland, FL, substantial damage. Probable cause: The faulure of the pilot to maintain directional control of the aircraft during the landing roll resulting in the on-ground collision with a taxiway sign and subsequent collapse of the nose landing… 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.