# NTSB ERA26LA033: Cessna 172, N34LC, Oxford, CT, November 6, 2025 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 4 · Limited · Final report - Date: November 6, 2025, 15:49 local (20:49 UTC) - Place: Oxford, CT · Embankment adjacent to runway 36 at OXC - Coordinates: 41.473032, -73.13317 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.4730&lon=-73.1332&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report January 9, 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): 201969 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA26LA033 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/201969/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=201969 - Page: https://openairdocs.org/ntsb/ERA26LA033 ## Probable cause The pilot’s failure to compensate for gusty crosswind conditions, which resulted in a loss of control of the airplane and subsequent collision with terrain. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172N, 150 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072434), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Response/compensation (probable cause); cases with it: [Cessna 172N, 19 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=2072434), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md) - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Response/compensation (probable cause); cases with it: [Cessna 172N, 28 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=2072434), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 172N, 45 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072434), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172N, 134 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072434), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that the purpose of the flight was to practice traffic pattern operations with a simulated power off, 180-degree turning approach to land. While turning toward final approach, the pilot stated that the left wing began to rise as the result of a crosswind gust. The pilot was unable to stop the right turn, which continued until airplane impacted the ground. The airplane then became airborne again before it came to a rest in tall grass and bushes east of the runway. The airplane’s wings and fuselage sustained substantial damage. The pilot stated that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation. ## Aircraft - Registration: [N34LC](https://openairdocs.org/aircraft/N34LC), registered now, S/N 17272203, built 1979 (OpenAirDocs) - Reported make and model: CESSNA 172 (N) - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17272203 - Year built: 1979 - Airframe hours: 5294 - Engines: LYCOMING O-320-A4M 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: Annual, October 23, 2025, 23 hours before - Departed: DXR, Danbury, CT - Destination: DXR, Danbury, CT - Airport: OXC, Waterbury-Oxford, runway 36, 5,801 × 100 ft, asphalt - Equipment: Electronic flight bag or handheld device, Stall warning system, ADS-B, Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 47; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review November 27, 2024; seat: left; restraint: 3-point; flight hours: 272 total, 161 in this make and model, 205 as pilot in command, 26.5 in the last 90 days, 11.8 in the last 30 days, 3.1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 6 knots, gusting 15 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 45 °F, dew point 27 °F - Altimeter: 30.05 inHg - Observed at: OXC - METAR: METAR KOXC 062056Z VRB06G15KT 10SM SCT060 07/M03 A3005 RMK AO2 SLP191 T00721028 53019 $= ## 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 20251106019969A](https://openairdocs.org/incident/20251106019969A), Nov 6, 2025: Cessna 172N, Oxford, CT, Substantial damage. A Cessna 172, 4 place single engine aircraft was practicing take offs and landings at Oxford oxc airport in Connecticut. While attempting a landing on runway… ## Docket (2 files) The files NTSB released with the investigation on January 9, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=201969. 44.3 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 42.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19583989&FileExtension=pdf&FileName=ERA26LA033%206120.1%20Redacted-Rel.pdf - Investigation photographs (item 2, PDF, 5 pages, 4 photos, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19635472&FileExtension=pdf&FileName=ERA26LA033%20Investigation%20Photo%20Array-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.