# NTSB MIA03CA158: Cessna 172S, N775SP, Orlando, FL, August 7, 2003 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 7, 2003, 11:25 local (15:25 UTC) - Place: Orlando, FL - Coordinates: 28.545278, -81.332778 - Nearby events: https://openairdocs.org/map.md?lat=28.5453&lon=-81.3328&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report November 25, 2003 - Report: Approved by Office Director - Parties: FAA FSDO - NTSB case key (mKey): 57661 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=MIA03CA158 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/57661/pdf - Page: https://openairdocs.org/ntsb/MIA03CA158 ## Probable cause The failure of the student pilot to maintain directional control of the airplane during takeoff roll resulting in the aircraft departing the runway and incurring substantial damage. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, takeoff - roll/run - directional control - not maintained, pilot in command (cause) ## Analysis The student pilot stated that he was on his second touch-and-go of his first solo flight, when he added power and was rolling down the runway. He noted the airplane was headed toward the left edge of the runway and applied right rudder to compensate; the airplane did not respond to the input. He reduced engine power, however, the airplane skidded off the runway on to the grass for about 45 feet before coming to a full stop.The student's flight instructor stated that he observed the student perform the first touch-and-go well and without incident. He mentioned on the second landing, shortly after the airplane touched down, the aircraft rolled on the runway for a few seconds then turned into the grass and then the nose gear of the airplane collapsed. A mechanic performed a visual inspection of the airplane and rudder system after the accident and stated he could not find any obstructions in the rudder system that would have attributed to the accident. ## Factual narrative On August 07, 2003, about 1125 eastern daylight time, a Cessna 172S, N775SP, registered to Scharf Aviation Inc., and operated by Air Orlando Flight School, ran off the side runway 25 during takeoff roll at Orlando Executive Airport, Orlando, Florida. Visual meteorological conditions prevailed at the time, and no flight plan was filed. The instructional flight was conducted under 14 CFR Part 91. The airplane incurred substantial damage and the student pilot was not injured. The flight originated from Orlando, Florida, the same day, about 1100.. The student pilot stated that he was on his second touch-and-go of his first solo flight, when he added power and was rolling down the runway. He noted the airplane was headed toward the left edge of the runway and applied right rudder to compensate; the airplane did not respond to the input. He reduced engine power, however, the airplane skidded off the runway on to the grass for about 45 feet before coming to a full stop. The student's flight instructor stated that he observed the student perform the first touch-and-go well and without incident. He mentioned on the second landing, shortly after the airplane touched down, the aircraft rolled on the runway for a few seconds then turned into the grass and then the nose gear of the airplane collapsed. A mechanic performed a visual inspection of the airplane and rudder system after the accident and stated he could not find any obstructions in the rudder system that would have attributed to the accident. ## Aircraft - Registration: [N775SP](https://openairdocs.org/aircraft/N775SP), registered now, S/N 172S8705, built 2001 (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: 172S875 - Airframe hours: 1151 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Air Orlando Flight School - Registered owner: Scharf Aviation Inc. - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, June 3, 2003, 88.1 hours before - Departed: KORL, Orlando, FL - Airport: ORL, Orlando Executive, runway 25, 6,003 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 34; injuries: none; student; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 35 total, 35 in this make and model, 35 in the last 90 days, 26 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 86 °F, dew point 73 °F - Altimeter: 29.95 inHg - Observed at: KORL, 1 nm away ## 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 20030807018219A](https://openairdocs.org/incident/20030807018219A), Aug 7, 2003: Cessna 172S, Orlando, FL, Substantial damage. (-23) Student pilot was on his first solo flight. After successfully completing two touch and go's the student pilot was on his third takeoff roll when he lost… ## Other investigations on N775SP (1) 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 ERA14CA317](https://openairdocs.org/ntsb/ERA14CA317), Jun 29, 2014: Cessna 172S (N775SP), Orlando, FL, substantial damage. Probable cause: The flight instructor's failure to maintain control while taxiing in a strong gusty wind. 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.