# NTSB ERA24LA033: Cessna 172S, N91PF, Orlando, FL, November 10, 2023 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Class 3 · Limited · Final report - Date: November 10, 2023, 10:50 local (15:50 UTC) - Place: Orlando, FL - Coordinates: 28.782222, -81.218889 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=28.7822&lon=-81.2189&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) - Highest injury: Minor injuries - Injuries: 2 minor - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 193370 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA24LA033 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/193370/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=193370 - Page: https://openairdocs.org/ntsb/ERA24LA033 ## Probable cause A partial loss of engine power during initial climb after takeoff for undetermined reasons. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Aircraft](https://openairdocs.org/ntsb-findings/01050000): Aircraft › Aircraft power plant · Unknown/Not determined (probable cause); cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-findings/01050000/cases.md?model=2072439), [All aircraft, 151 cases](https://openairdocs.org/ntsb-findings/01050000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Unknown or undetermined](https://openairdocs.org/ntsb-events/000) (defining event); cases with it: [Cessna 172S, 12 cases](https://openairdocs.org/ntsb-events/000/sequence.md?model=2072439), [All aircraft, 1,703 cases](https://openairdocs.org/ntsb-events/000/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 172S, 15 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072439), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Cessna 172S, 102 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072439), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); 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 The flight instructor and pilot receiving instruction were conducting a touch-and-go landing. The pilot receiving instruction landed long on the runway, then, during initial climb after takeoff, the engine exhibited a partial loss of power when the airplane was about 150 ft above ground level (agl). The flight instructor called for and took positive control of the airplane, then conducted an emergency descent straight ahead to land on the remaining runway. The airplane bounced on the runway at high speed near the departure end, and the flight instructor maneuvered it to clear an obstacle before landing it hard in the grass. Postaccident examination of the engine, ignition system, and fuel system revealed no evidence of any preimpact mechanical malfunction or failure that would preclude normal operation. A review of the maintenance logbook excerpts revealed no open discrepancies. ## Factual narrative On November 10, 2023, at 1050 eastern standard time, a Cessna 172S, N91PF, was substantially damaged during a forced landing at Orlando Sanford International Airport (SFB), Orlando, Florida. The flight instructor and pilot receiving instruction sustained minor injuries. The airplane was operated as a 14 Code of Federal Regulations Part 91 instructional flight. According to the flight instructor, he and the pilot receiving instruction were conducting a touch-and-go landing on runway 9L at SFB. The pilot receiving instruction conducted the landing with 10° of flaps, which increased the landing roll distance. During the landing roll, the pilot receiving instruction raised the flaps to 0°, added power to take off again, and, as the airplane climbed through 150 ft agl, the engine exhibited a partial loss of power. The flight instructor stated that he called out “my flight controls” and verified the fuel selector was on “both” and the mixture was full rich. He stated that he “dived” the airplane and added flaps to try to land straight ahead on the remaining runway, based on his assessment that the airplane had insufficient altitude to complete a turn to land in the opposite direction. The flight instructor stated the airplane bounced on the runway at high speed and was about to collide with the runway end identifier lights, so he reduced the flaps to 0° and tried to add power, but the engine didn’t produce much power. The airplane cleared the obstacle but was unable to climb. The flight instructor then made a “very hard landing” in the grass off the right side of the departure end of the runway to avoid a swamp. Postaccident examination revealed that the fuselage and both wings were buckled and the engine was partially separated from the airframe. About 30 gallons of 100LL was defueled from both fuel tanks at the accident site. After the airplane was removed from the site, fuel was observed leaking from the fuel system. The cockpit fuel selector was found in the “both” position. During the engine examination, the crankshaft was turned by manually rotating the propeller. The crankshaft turned freely through 720° with no binding or unusual noise evident, and all cylinders showed compression and suction. A lighted borescope was inserted into the cylinders, and no anomalies were noted. The pistons moved up and down normally, and valve action was correct. There were no holes or damage to the pistons or valves. The engine-driven fuel pump was removed for examination. Fuel was found inside the lines from the fuel pumps to the fuel servo. The fuel strainer was opened; the strainer was full of fuel, and the screen was clean and unobstructed. No contamination or obstructions were found in the fuel system. The lever-action pumps functioned normally when operated by hand. The servo was impact damaged and broken away from the engine. Continuity for the engine controls was confirmed from the cockpit to the engine, but their preimpact positions could not be verifieddue to the engine being partially separated from the mounts. The oil filter was removed for examination. The unit contained oil. The screen was removed, and no particulates or contamination were observed. The spark plugs were removed for examination. The electrodes were normal in wear and dark in color when compared to a Champion Check-a-Plug chart. The magnetos were removed and tested by rotating the input drives with a power drill. Both magnetos produced spark when rotated. The two-blade aluminum propeller remained securely attached to the engine. The propeller spinner was crush damaged. The propeller blades exhibited impact damage; one blade was bent aft midspan. There was no chordwise scratching on the surfaces of the blades or leading-edge damage. A review of the maintenance logbook excerpts revealed no open discrepancies. ## Aircraft - Registration: [N91PF](https://openairdocs.org/aircraft/N91PF), registered now, S/N 172S10302, built 2006 (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: 172S10302 - Year built: 2006 - Airframe hours: 12095 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, October 6, 2023, 90 hours before - Destination: Same as departure - Airport: SFB, Orlando Sanford International, runway 9L, 11,002 × 150 ft, asphalt - Equipment: Electronic primary flight display, Electronic multifunction display, Auto-pilot, ADS-B, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Flight instructor; age 33; injuries: minor; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: sport pilot; last flight review October 6, 2023; seat: right; restraint: 3-point; flight hours: 1,447 total, 1,324 in this make and model, 1,310 as pilot in command, 194 in the last 90 days, 68 in the last 30 days, 3 in the last 24 hours - Pilot; age 28; injuries: minor; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review September 6, 2022; seat: left; restraint: 3-point; flight hours: 306 total, 195 in this make and model, 203 as pilot in command, 29 in the last 90 days, 11 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 180° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 82 °F, dew point 68 °F - Altimeter: 30.09 inHg - Observed at: SFB, 1 nm away - METAR: KSFB 101553Z 18008KT 10SM CLR 28/20 A3009 RMK AO2 SLP187 T02830200 ## 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 20231110022239A](https://openairdocs.org/incident/20231110022239A), Nov 10, 2023: Cessna 172S, Sanford, FL, Destroyed. While practicing a touch and go, the aircraft lost power during departure roll and crashed off the departure end of runway 9L. Pilot states that nothing… ## Docket (4 files) The files NTSB released with the investigation on September 3, 2025, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=193370. 379 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 11 pages, 3.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19147461&FileExtension=pdf&FileName=6120%20LA033_Redacted-Rel.pdf - Memorandum for record - FAA inspector engine examination summary (item 2, PDF, 2 pages, 69 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17304915&FileExtension=pdf&FileName=FAA%20MOR%20engine%20examination%20LA033-Rel.pdf - Maintenance records (excerpt) (item 3, PDF, 10 pages, 373 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17304691&FileExtension=pdf&FileName=MX%20logbook%20excerpts%20LA033_Redacted-Rel.pdf - Investigative photos (item 4, PDF, 3 pages, 2.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=17305003&FileExtension=pdf&FileName=Investigative%20Photos%20LA033-Rel.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.