# NTSB ERA11CA347: Cessna 172N, N4954G, Belle Glades, FL, June 15, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 15, 2011, 18:30 local (22:30 UTC) - Place: Belle Glades, FL - Coordinates: 26.692222, -80.656387 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=26.6922&lon=-80.6564&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 December 19, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 80798 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA11CA347 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/80798/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=80798 - Page: https://openairdocs.org/ntsb/ERA11CA347 ## Probable cause The pilot’s failure to maintain airplane control during the landing approach. ## 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) - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Effect on operation (probable cause) - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause) ## Analysis The pilot reported that while conducting flight maneuvers he encountered inclement weather. After electing to divert to a nearby airport, he encountered gusting wind and rain showers in the landing pattern. He was unable to land on his first approach due to a gusting crosswind. After conducting a go-around and reattempting a landing approach, the pilot was unable to align the aircraft due to the wind and attempted a second go-around. However, the gusting wind caused him to lose control of the airplane, which subsequently impacted the ground. During the accident sequence, the airplane sustained substantial damage to the left wing and firewall. The wind in the vicinity was reported to be 15 knots with gusts of 28 knots. The pilot reported no preimpact mechanical malfunctions that would have precluded normal operation. ## Factual narrative The pilot reported that while conducting flight maneuvers he encountered inclement weather. After electing to divert to a nearby airport, he encountered high winds, gusting winds, and rain showers in the landing pattern. He was unable to land on his first approach due to a gusting cross wind. After conducting a go-around, reattempting a landing approach, the pilot was unable to align the aircraft due to the winds and attempted a second go-around. However, the gusting wind caused him to lose control of the airplane and subsequently impacted the ground. During the accident sequence, the airplane sustained substantial damage to the left wing and firewall. Winds in the vicinity were reported at 15 knots with gusts of 28 knots. The pilot reported no preimpact mechanical malfunctions that would have precluded normal operations. ## 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) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) ## Aircraft - Registration: [N4954G](https://openairdocs.org/aircraft/N4954G), registered now, S/N 17273501, built 1979 (OpenAirDocs) - Reported make and model: CESSNA 172N - 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: 17273501 - Airframe hours: 9545 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Ari Ben Aviator Inc - Registered owner: Ari Ben Aviator Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 22, 2011, 86 hours before - Departed: FPR, Fort Pierce, FL - Destination: FPR, Fort Pierce, FL - Airport: X10, Belle Glade State Municipal, runway 09, 3,700 × 50 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 44; injuries: none; military, private; airplane ratings: single-engine land; instrument ratings: helicopter; medical: class 1; last flight review June 13, 2011; seat: left; flight hours: 4,992 total, 42 in this make and model, 3,213 as pilot in command, 60 in the last 90 days, 20 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 110° at 15 knots, gusting 28 - Visibility: 1 statute miles - Lowest ceiling: 2,500 ft broken - Temperature: 73 °F, dew point 66 °F - Altimeter: 29.96 inHg - Observed at: OBE, 35 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 20110615013249A](https://openairdocs.org/incident/20110615013249A), Jun 15, 2011: Cessna 172N, Belle Glade, FL, Substantial damage. Pilot departed st lucie county airport (fpr) at 15:47 local on a time building flight VFR. Computer weather breifing showed activity above melbourne; a front… ## Docket (5 files) The files NTSB released with the investigation on October 17, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=80798. 1.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 608 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350522&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Pilot statement (item 2, .PDF, 195 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350523&FileExtension=.PDF&FileName=Pilot%20statement-Redacted.PDF - Reports from Federal Agencies-Record of Conversation FAA (item 3, .PDF, 20 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350524&FileExtension=.PDF&FileName=Reports%20from%20Federal%20Agencies-Record%20of%20Conversation%20FAA-Master.PDF - Photo 1- FAA photo- right side of airplane (item 4, .PDF, 636 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351469&FileExtension=.PDF&FileName=Photo%201-%20FAA%20photo-%20right%20side%20of%20airplane%20-Master.PDF - Photo 2-FAA photo- buckled fuselage (item 5, .PDF, 250 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351470&FileExtension=.PDF&FileName=Photo%202-FAA%20photo-%20buckled%20fuselage-Master.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.