# NTSB ERA25LA306: Cessna 172, N6208C, Baltimore, MD, August 17, 2025 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 4 · Limited · Final report - Date: August 17, 2025, 03:00 local (07:00 UTC) - Place: Baltimore, MD · On Runway - Coordinates: 39.330038, -76.419427 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.3300&lon=-76.4194&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 30, 2026 - Report: Approved by Office Director - Investigation class: Class 4 - Basic report with no Prelim publish - NTSB office: Eastern Region Aviation - Parties: FAA / FSDO - NTSB case key (mKey): 200825 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25LA306 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200825/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=200825 - Page: https://openairdocs.org/ntsb/ERA25LA306 ## Probable cause The pilot’s inadequate landing flare at night, which resulted in a hard landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained; 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 · 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: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); 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: 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) ## Analysis The pilot was returning to his home airport at night following a personal cross-country flight. He reported that before departure, he completed the preflight and before takeoff checks with no anomalies noted. The takeoff, enroute, and approach phases of the flight were uneventful. He stated that after completing a practice instrument approach, and during the landing flare, the elevator control was restricted and not fully effective. The airplane subsequently touched down flat, and during taxi to parking, the pilot noted a “wobbly” nosewheel. After shutdown, he observed damage to the nosewheel, restricted elevator control movement, and abnormal trim wheel operation. Examination of the airplane by the operator and an FAA inspector revealed that the airplane sustained substantial damage to firewall and lower fuselage. The inspector noted that the elevator control pivot point near the lower fuselage impact damage was bent, which restricted the elevator control yoke movement. Postaccident examination of the airplane revealed no preaccident mechanical malfunctions or failures that would have precluded normal operation. Due to the pilot’s reported preflight flight control checks, which would have confirmed free and correct movement, and the postaccident examination that revealed no mechanical anomalies, it is likely that the elevator control binding resulted from damage sustained during the hard landing. ## Aircraft - Registration: [N6208C](https://openairdocs.org/aircraft/N6208C), registered now, S/N 172S10820, built 2008 (OpenAirDocs) - Reported make and model: CESSNA 172 (S) - 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: 172S10820 - Year built: 2008 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Mustang Sally Aviation LLC - Airworthiness certificate: Standard, Normal; Standard, Utility - Departed: RDU, Raleigh/Durham, NC - Destination: Same as departure - Flight plan: IFR - Airport: MTN, Martin State, runway 33, 6,997 × 180 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: none; commercial; airplane ratings: single-engine sea, single-engine land; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 599 total ## Weather - Conditions: Visual (VMC), Night - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 73 °F - Altimeter: 30.03 inHg - Observed at: MTN - METAR: KMTN 170510Z AUTO 00000KT 10SM CLR 26/23 A3003 RMK AO2 T02610225 ## 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 20250817012469A](https://openairdocs.org/incident/20250817012469A), Aug 17, 2025: Cessna 172S, Middle River, MD, Substantial damage. Pilot was returning from cross country flight on IFR flight plan from rdu to mtn. Whether it was VMC winds calm, visibility 10 miles, sky scattered at 5000… ## Docket (6 files) The files NTSB released with the investigation on April 30, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=200825. 4.0 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19859350&FileExtension=pdf&FileName=NTSB%206120%20Report_Redacted-Rel.pdf - Memorandum for record a�� FAA inspector statement (item 2, PDF, 1 page, 68 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19859632&FileExtension=pdf&FileName=MFR%20FAA%20Inspector%20Statement-Rel.pdf - Memorandum for record a�� pilot statement (item 3, PDF, 2 pages, 70 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19859130&FileExtension=pdf&FileName=MFR%20Pilot%20Statement-Rel.pdf - Weather report (item 4, PDF, 1 page, 252 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=20266001&FileExtension=pdf&FileName=METAR-Rel.pdf - Excerpt from FAA aircraft accident package - ATC timeline (item 5, PDF, 4 pages, 878 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19859084&FileExtension=pdf&FileName=N6208C%20ACCIDENT%20PACKAGE%2025-005-PCT%20Excerpt-Rel.pdf - Investigation photographs (item 6, PDF, 7 pages, 6 photos, 827 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19870717&FileExtension=pdf&FileName=Investigation%20Photographs-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.